After merging apache2, when trying to merge mod_php (4.3.2-r3) with USE="apache2", I get (after some time): grep: /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/libstdc++.la' is not a valid libtool archive make: *** [libphp4.la] Error 1 make: *** Waiting for unfinished jobs.... !!! ERROR: dev-php/mod_php-4.3.2-r3 failed. !!! Function php_src_compile, Line 384, Exitcode 2 !!! compile problem The problem is that my host type is i686 and not i586, and the correct one also pops up many times during this and many other package merges. The path on my system would then be /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/, and not /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/ as is tried here. I don't know where the wrong path comes from. Reproducible: Always Steps to Reproduce: 1. I merge apache2. I already have apache1 with mod_php (same version) merged. 2. I try to merge mod_php. This produces the bug. Actual Results: The bug as demonstrated by the screen dump above. Expected Results: It should have worked! ;-).
make sure you have latest gcc and gcc-config ... then run `env-update && source /etc/profile` try again and see if it works ...
*** Bug 24921 has been marked as a duplicate of this bug. ***
One package you have still refers to the i586 version you had installed at some point. Search thru all of your libraries to find what is linked against /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/libstdc++.la, and then recompile that package. This is not a PHP or Apache bug, it's due to not compiling everything linked against a library which was removed.
Well I never had my CHOST set to i586 at any point, so I don't know how that could have happened. Also, the _same_ version of mod_php merged just fine before; All this only started after merging Apache2. Oh and, how do you "search through all libraries and find what is linked against ..." ? I have no idea how that is done.
I did fgrep 'libstdc++.la' * from within /usr/lib. That showed that the problem was with aspell and gtkspell. I re-emerged them and now everything is working. I have no idea how any i586 stuff got into the system in the first place as at least one of the machines is a stage1 build and has always been i686.
Same here, but only aspell for me. Aspell is not in my world file, so I don't know who installed it (I have USE="spell" as per default). All I know is that all this started after merging apache2 a few days ago. No problems before that, so I still think there is some kinda bug somewhere ;-). After merging apache 2 I couldn't even re-merge mod_php or php for apache1.
i had the same problem, and my libaspell.la and libpspell.la files included references to 586. i recompiled them and now all of the references in them are to 686. but i'm still encountering the same problem at compile time. does anyone know why this might be? do i need to refresh some other key data? the bug's been discussed at http://forums.gentoo.org/viewtopic.php?t=65846 and i've been thinking of trying their fix but it looks way more dangerous to me. i executed their command line code without the last sed command and there are piles of *.la files that would be modified under /usr/kde/3.1/ilb/ and one under /usr/lib/xchat/plugins/. does anyone have any words of advice?
I suggest grepping your entire system for i586 and seeing about re-compiling those binaries that have 'i586' in them.
their .la solution works, just do it and forget about it ;)
*** Bug 25424 has been marked as a duplicate of this bug. ***
*** Bug 25433 has been marked as a duplicate of this bug. ***
