Summary: | dev-dotnet/libgdiplus-1.2.6 fails to build with libtool-2.2.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gilles Dartiguelongue (RETIRED) <eva> |
Component: | New packages | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alessandrochirico |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 212763 | ||
Attachments: |
build.log
libtool 2.2 patch |
Description
Gilles Dartiguelongue (RETIRED)
2008-04-29 09:23:08 UTC
Created attachment 151308 [details]
build.log
Though it doesn't seem this way, it's an upstream bug. The way they included cairo sources doesn't let eautoreconf discover them. And anyway, somebody should ask upstream, why libgdiplus prefers included cairo over system and is it still this way for cairo 1.6. eautoreconf only rebuilds for the directory it was run in but you're right in that cairo should not be bundled or built into the package. it should be using the system version. (In reply to comment #3) > eautoreconf only rebuilds for the directory it was run in > > but you're right in that cairo should not be bundled or built into the package. > it should be using the system version. > I added --with-cairo=system for econf and it built fine. I'm not asking `does it build with --with-cairo=system`, I'm asking `why does upstream prefer included cairo`. Created attachment 154189 [details, diff]
libtool 2.2 patch
here is patch. but i tested it only on live ebuild, not on latest release
try it :-)
Try upgrading to 1.9, do you still experience same problems? Well, as 1.9 uses system cairo, this bug simply can't affect it. (In reply to comment #8) > Well, as 1.9 uses system cairo, this bug simply can't affect it. > It affects version 1.9 too. When eautoreconf is run, it goes into the cairo subdirectory and triggers the bug. The patch must be applied anyway, or simply rm -rf cairo (the subdir) since the local version is not used (In reply to comment #9) > (In reply to comment #8) > > Well, as 1.9 uses system cairo, this bug simply can't affect it. > > > > It affects version 1.9 too. When eautoreconf is run, it goes into the > cairo subdirectory and triggers the bug. The patch must be applied anyway, > or simply rm -rf cairo (the subdir) since the local version is not used No it does not. Just built this with libtool-2.2.4, no error. @CAIRO_DIR@ is the cairo dir in Makefile.am and CAIRO_DIR is only set in configure.in if cairo_v=internal. This bug is fixed in libgdiplus-1.9. |