libtool issues

[jim@…]

Ryan and I are looking into issue caused by the flackiness of libtool. This tool also has impacted cross platform builds RPATH as well. This problem is a minor issue, but needs to be correct if possible.

Example: # Libraries that this one depends upon. dependency_libs=' -L/sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src -L/ sources/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src/.libs -lm -lm -lm -L/ sources/gcc-build/gcc -lgcc_s -lc -lgcc_s -lm -lgcc_s -lc -lgcc_s'

[n-roeser@…]

A symptom of the problem is shown in bug 883.

[Matthew Burgess]

Any ideas whether the latest versions of libtool fix this up, or is it more of a design problem with libtool? Either way, is libtool upstream aware of this?

[jim@…]

Still happening. This issue is being worked, but not a priority.

[ryan.oliver@…]

Will attempt to take a look at this over the next couple of weeks. Not to sure how to handle it as we shouldn't really adjust the .la files until *after* the build completes...

would probably be easier to regenerate them (pointing at install locations) than to come up with a sed...

libtool... bleh...

[giftbound@…]

If im not wrong I think the CVS version corrects this issue

[jim@…]

Issue still exists with libtool 1.5.14. If you change your /usr/lib/libstdc++.la file you will notice that the temp directories are still in the dependency path.

[archaic@…]

Jim or Ryan, what is the status of this bug? The last comment was made in late February.

[jim@…]

Suppose to be fixed with libtool 2.0, when it's released.

[Matthew Burgess]

Can we mark this as WONTFIX and we'll pick the fix up when upstream do so? It's been so long now and it doesn't appear to be having any ill effects on our build method.

[Jeremy Huntwork]

Marking as WONTFIX as per Matt's suggestion. If you find that this is still an issue, and have a means to fix it, please reopen this ticket.