Mark Knecht wrote:
Thanks Stan,
I'll investigate doing that. I've not modified files like this
before on Gentoo and I'm sort of reluctant to go down that path.
I'm very surprised at this sort of unfixed bug. It's coming up on 3 years!
Am I correct that if I remove the gcj flag and re-emerge the
problem will go away?
Thanks,
Mark
As far as I know, yes. This would be supported by the fact that you
never saw it until you enabled the gcj flag. The only two *.la files
that are broken on my system are also related to the gcj use flag being
turned on. I was kind of surprised to find the age of this bug and see
it still remain unfixed. My guess is that not too many people have this
use flag enabled so it hasn't gotten a lot of attention and thus has
mostly been forgotten. Just by way of additional help, here is the line
for /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/libgij.la on my system that I
have edited:
# Libraries that this one depends upon.
dependency_libs='/usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/libgcj.la
-lpthread -lrt -ldl -lz'
Note that the path to the correct .la file and the location of the
file(s) you need to fix will depend on the version of gcc you are using.
In my case it's version 4.3.2, but this will show the pattern you need
to follow. The additional -l* libraries shown above are entries that
existed before I updated the path to the libgcj.la file, so I left them
alone. There are two files on my system, and I can't remember the name
of the second one right now. It's not too difficult to pick out of the
revdep-rebuild output, though.
--
Stan & Tashi
