Probably it is not a good practice, but for some reason time ago I had to define a CFLAGS containing an include path like this: CFLAGS=<normal flags> -I/some/strange/path This breaks the sed commands in src_unpack in the generated environment script of some ebuilds (example: media-libs/ladspa-sdk). I am not sure if this a single ebuild issue of this package, but I suspect a more general problem. As far as my specific issue is concerned: I removed the -I, in the hope that it is not needed any more. Reproducible: Always Steps to Reproduce: 1. add -I/some/path to your CFLAGS 2. emerge ladspa-sdk 3. Actual Results: emerge dies with sed error during src_unpack. Expected Results: build the package
As we use this during bootstrapping for Gentoo Prefix, it's likely to be a problem with ladspa-sdk.
Which version of media-libs/ladspa-sdk did you try? 1.12-r2 and 1.13 use sed to hack the CLFAGS into the build system. This is gone in the 1.13-r1 ebuild. 1.13-r1 is getting stabilized in bug 304033. Please try this one and report back.
(In reply to comment #2) Yes. it was 1.13, last marked stable in the tree. As soon as the world update finishes, I will try the 1-13-r1 with the -I flag.
(In reply to comment #3) Tested 1.13-r1, and it works. I'll close this bug as fixed then, though the fix regards a single package, non portage itself.
