When I try to emerge amarok, I get an error related to libstdc++.la. Reproducible: Always Steps to Reproduce: 1.emerge amarok Actual Results: grep: /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.la' is not a valid libtool archive make[4]: *** [libamarok.la] Error 1 Expected Results: amarok emerged successfully. I've searched google and the gentoo forums and found many proposed solutions, many involving fix_libtool_files.sh. They didn't work. What is the next step in figuring out what could be causing this problem?
Please, search... *** This bug has been marked as a duplicate of bug 73435 ***
I *have* searched, extensively. If I could find a solution by searching or using my own debugging skills I wouldn't have opened this bug in the first place! *NONE* of the solutions proposed in the bug you linked fixed my error AND the reporter isn't even having the same bug as I! Lets just start with the basics: 1) What package is supposed to provide libstdc++.la? 2) If none, why is libtool looking for it? Does it have some kind of library index table I can look at to get an idea of what is breaking? Thank you for your time, James Steven Supancic III
Read the other bug, thanks. *** This bug has been marked as a duplicate of bug 73435 ***
Are you some kind of bot that greps for the string 'libstdc++.la' in reports and then marks bugs as a duplicate of Bug 73435? I am NOT having the same problem as the reporter of Bug 73435. The solutions given in that thread do NOT work for me! I have tried them ALL twice. I have read Bug Report #73435 three times! I AM NOT ENCOUNTERING THE SAME ISSUE AS THE REPORTER OF BUG #73435! THIS IS **NOT** A DUPLICATE OF BUG #73435! THIS IS **NOT** A DUPLICATE OF BUG #73435! PLEASE DO NOT MARK THIS AS A DUPLICATE OF #73435 AGAIN. Thank you for your time, James Steven Supancic III
(In reply to comment #4) - Yes, you have exactly the same issue. - No, you didn't bother yourself with reading the bug (esp. Bug 73435, Comment #208) - Fix your Caps Lock and stop screaming. - No, absolutely no point in reopening this bug over and over again. DUPLICATE, do *not* reopen this. *** This bug has been marked as a duplicate of bug 73435 ***
Closed.
Let us ignore the fact that I always run fix_libtool_files.sh after upgrading gcc and the fact that I have never used gcc 4.1.0 (I upgraded from 3.6 to 4.1.1) (so this shouldn't have happened in the first place and I don't see what thas has to do with my system). From the post you cite "The solution is simple: "fix_libtool_files.sh 4.1.0". This is what I did: delta ~ # fix_libtool_files.sh 4.1.0 delta ~ # env-update && source /etc/profile delta ~ # revdep-rebuild -X delta ~ # env-update && source /etc/profile delta ~ # env-update && source /etc/profile delta ~ # emerge amarok. Same error. Now, What is going on? If what you say is true, Why am I getting the same error? Why didn't the solution proposed in http://bugs.gentoo.org/show_bug.cgi?id=73435#c208 work? Thank you for your time, James Steven Supancic III
err, I upgraded from 3.4.6. And sorry about the caps, I am just a bit frustrated after spending a whole day re-emering things...
Stop reopening this bug! *** This bug has been marked as a duplicate of bug 73435 ***
(In reply to comment #7) > delta ~ # fix_libtool_files.sh 4.1.0 Of course this won't work; you need fix_libtool_files.sh 4.1.1 obviously. But why not repeat what's been said about zillion times on the other bug. *Please* stop this pointless noise already.
I tried that already. I did that yesterday when I was searching the gentoo forums (http://forums.gentoo.org/viewtopic-t-318790.html). It was suggested there. I double checked my .bash_history. Yesterday I did: delta ~ # fix_libtool_files.sh 4.1.1 delta ~ # env-update && source /etc/profile delta ~ # env-update && source /etc/profile delta ~ # emerge amarok same issue, But I did it again, just to be 100% sure that it does not work. Guess what? The SAME error. I am beginning to take offense your repetitive RTFMish replies. I am asking here because I have searched google, I have searched the gentoo forums, and I have searched this bugzilla. Did it even occur to you that, while the bugs my be superficially similar, they might not have the same causes? Thank you for your time, James Steven Supancic III
*** This bug has been marked as a duplicate of bug 73435 ***
