| Summary: | media-gfx/imagemagick-6.4.2.9 fails to emerge with "compile problem" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Willard Dawson <willard.dawson> |
| Component: | Current packages | Assignee: | Gentoo Graphics Project <graphics+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Willard Dawson
2008-08-21 02:46:13 UTC
Full build log, if you don't mind. I did some more reading. Don't bother with the build log, cause, well,... What I'm about to say will be very rude but I really can't help it. This simply must be done. First of all, the reporter: you were the one who broke your system, you are in ~x86, so you should already have libtool 2 installed. To the author of the recent ebuild revision: you broke the ebuild; no, I'm not talking about the fact, that ImageMagick uses libtool 2 specific macros, so eautoreconf breaks it on the systems that have only 1.5 installed, I'm talking about the fact that you first sed the configure script and then run eautoreconf, which regenerates that script. So both the bug AND the ebuild are invalid (though the ebuild problem is quite minor). (In reply to comment #2) > I did some more reading. Don't bother with the build log, cause, well,... > > What I'm about to say will be very rude but I really can't help it. I don't take your comments as rude. Quite the contrary - they're tame in comparison to some I've seen elsewhere in Gentoo-land. > you are in ~x86, so you should already have libtool 2 installed. I forget why... lost long ago in the dim recesses of history... that I had libtool-2.2.4 masked. Unmasking it resolved the issue, of course. Thanks for the pointer. > So both the bug AND the ebuild are invalid (though the ebuild problem > is quite minor). If libtool 2 is required, shouldn't the ebuild puke on that rather than moving on with libtool <2 ? *** This bug has been marked as a duplicate of bug 235131 *** |