Bug 167736 – media-libs/sdl-sound will not build with libtool-1.5.23b

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Max 2007-02-20 11:50:56 UTC]

I'm trying to emerge sdl-sound for dosbox, but during compile of sdl-sound the emerge process errors out. For complete error, see the emerge.log attachment. Build output has vast amounts of this line in it:

../../libtool: line 1100: -e: command not found
../../libtool: line 1048: -e: command not found

The emerge_info.txt has my emerge --info output.


Reproducible: Always

Steps to Reproduce:
1. try and emerge sdl-sound with libtool-1.5.23b on your system
2.
3.

Actual Results:  
Error in compile

Expected Results:  
Nice and clean compile

I tried emerging =libtool-1.5.22 and build sdl-sound with that. No problems there: using =libtool-1.5.22, sdl-sound builds nicely.

[Comment 1 Max 2007-02-20 11:52:00 UTC]

Created attachment 110723 [details]
Log containing build output for sdl-sound

[Comment 2 Max 2007-02-20 11:52:25 UTC]

Created attachment 110724 [details]
Output of emerge --info

[Comment 3 SpanKY 2007-02-20 21:12:51 UTC]

SED isnt being set in libtool ...

[Comment 4 SpanKY 2007-02-20 22:17:15 UTC]

... and that's because someone upstream thought it'd be a swell idea to package an old libtool.m4 in acinclude.m4

[Comment 5 Max 2007-02-21 08:05:47 UTC]

Well, I dumped the 1.5.23b version of libtool in package.mask here and frankly I suggest the maintainers for the libtool package do the same until the upstream package is sane again. 

[Comment 6 SpanKY 2007-02-27 14:48:33 UTC]

wtf are you talking about ?  did you even read my comments ?  this has nothing to do with libtool ... the sdl-sound package is broken

[Comment 7 Max 2007-02-27 15:04:04 UTC]

Right. The way I read your comments (libtool not really being my thing), you are saying sed isn't being set in libtool, because someone packaged some incorrect m4 files. I can't distil which package (sdl-sound or libtool) contains the wrong files. Thus when I read your comments in a bugreport about libtool, I can only assume the files are packages incorrectly in the libtool package.

Fact remains that with the older version of libtool, sdl-sound DOES build. I suppose that could be because of either problems with sdl-sound and libtool. I don't know.

Apart from that, I'm trying to help out here, no need to become angry.

[Comment 8 Pompei2 2007-03-03 00:42:23 UTC]

Hello, It seems that exporting the environment variable
# export SED=sed
before emerging fixes that. At least, doing this, I can compile it withoute any problem. Can't say if the binary is broke or not, but I don't think so :)

Thank to SpanKy for pointing into the right direction !

[Comment 9 Jakub Moc (RETIRED) 2007-03-06 20:14:56 UTC]

*** Bug 169663 has been marked as a duplicate of this bug. ***

[Comment 10 Richard Benjamin Voigt 2007-03-12 04:47:51 UTC]

I can confirm that sdl-sound builds if and only if SED=sed is prefixed to the emerge line, on my amd64 (core2duo) system

[Comment 11 Kyle Hunter 2007-03-21 14:20:21 UTC]

Both on my friend's box (~x86) and my box (~amd64) it fails in this way unless you export SED=sed.

Thanks!

[Comment 12 Martin Wegner 2007-03-21 14:50:32 UTC]

The workaround (setting the env var SED to sed) solved this for me as well here (~amd64 box).

[Comment 13 SpanKY 2007-03-25 21:35:34 UTC]

sorry, i was referring to the notion of masking libtool/forcing a downgrade as being completely the wrong answer

the ebuild now deletes the excess m4 macros from the local .m4 file in src_unpack