Bugzilla Bug 167736

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.

Created an attachment (id=110723) [details]
Log containing build output for sdl-sound

Created an attachment (id=110724) [details]
Output of emerge --info

SED isnt being set in libtool ...

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

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. 

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

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.

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 !

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

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

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

Thanks!

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

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