My output (from musl-cross-make) is a relocatable/sysrooted static-linked toolchain, and having -L's in dependency_libs= is bad.
.@flameeyes Do you have any recipes for fixing the disaster of gcc installing .la files with hard-coded -L to build dirs in them?
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks for trying. I think I'm just going to have to move to using a staging-area before install.
-
On the positive side, then you can test the toolchain before installing it, which is convenient. And can also rm *.info, etc.
End of conversation
New conversation -
-
delete all la files? Gentoo had a tool to fix that but I forgot what the name was. fix_libtool_files or something
-
The only safe way to do that is to add an extra level of staging before install and find -exec rm in the staging dir...
-
find -exec rm in the actual install dir would not be reasonable/safe (e.g. if user already has third-party libs installed there).
End of conversation
New conversation -
-
-
Uninstall libtool.
-
It's not installed, it's part of the gcc build system. That's the problem.
-
I've had "NOP libtool wrapper" on my todo list since 2007.
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.