As I just got a patch for GNU libtool accepted, I suppose I can call myself a grey beard.
(and because it's actually macOS-specific, Apple should send few grand my way...)
As I just got a patch for GNU libtool accepted, I suppose I can call myself a grey beard.
(and because it's actually macOS-specific, Apple should send few grand my way...)
Today's bug is a `libtool` bug: https://savannah.gnu.org/support/index.php?111193
There `libtool` fails to supply enough compiler runtime libraries for `clang`+`compiler-rt` build toolchain.
When building alsa-utils with a custom toolchain + sysroot, I get this error:
libtool: error: cannot find the library '/usr/lib/libasound.la' or unhandled argument '/usr/lib/libasound.la'
However, the file does exist inside of the sysroot, and configure claims to use the sysroot that the compiler specifies.
How do I solve this?
Trying to wrap my head around the #libtool and #pkgconf vs pkg-config situation. What is going on?
Why is libtool bad, what is wrong with .la files, what does libtool do that pkgconf doesn't, and what does pkg-config do that neither of them do??
If anyone seeing this has dealt/is dealing with this linking/tooling situation I'd love to hear your thoughts :) Very curious.
Not all surprises are bad: #libtool maintainers have finally applied my patch first submitted in June 2011 today (https://savannah.gnu.org/patch/?8843).
This is my personal record (and by far) for the longest time between patch submission and its acceptance, which is especially impressive considering the patch consisted of just one (1) word.
As incredible as it may sound, a new #GNU #Libtool release is out!
https://savannah.gnu.org/forum/forum.php?forum_id=10139
👍