Summary: | Several ebuilds fail to emerge with similar or equivalent libstdc++.la problem | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Niels Muller Larsen <nml> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Niels Muller Larsen
2007-02-24 12:54:10 UTC
*** This bug has been marked as a duplicate of bug 73435 *** *** Bug 168239 has been marked as a duplicate of this bug. *** With all due respect I cannot see more than superficial similarity to the bug, that you claim this is a duplicate of. The error messages that I get do NOT point to some library of a previous incarnation of gcc. That would be the case if some developer used a literal ref to a specific version in stead of a variable ref. Instead the errors request a libstdc++-la of exactly the gcc-version that I am running. My conclusion therefore, is that this 'la'-file was not created during the emerge of the gcc version 4.4.1 that I run. I hold it that exactly this is the error that must be dealt with! I assume that if this is solved my 3 packages would emerge with no errors. On top of that I am critically dependent of Lyx of which I cannot find a binary package to install in stead. I hope you understand my point. So I humbly submit that you reconsider. (In reply to comment #3) > libstdc++-la of exactly the gcc-version that I am running. > > My conclusion therefore, is that this 'la'-file was not created during the > emerge of the gcc version 4.4.1 that I run. I hold it that exactly this is the > error that must be dealt with! It's not supposed to get created at all. Please re-read the bug more carefully. esp. bug 73435, Comment #208 *** This bug has been marked as a duplicate of bug 73435 *** |