Armin K. wrote:
On 28.10.2017 10:24, Pierre Labastie wrote:
Hi,
When building network-manager-applet, I got:
---------
[...]
CCLD src/libnm-gtk/libnm-gtk.la
/bin/grep: /usr/lib/libatk-1.0.la: No such file or directory
/bin/sed: can't read /usr/lib/libatk-1.0.la: No such file or directory
libtool: error: '/usr/lib/libatk-1.0.la' is not a valid libtool archive
---------
The reason id that libatk-1.0.la has not been installed when building
the atk package, because the build system is meson, but
network-manager-applet still uses autotools!
Of course, I can copy an old .la file coming from previous builds with
autotools, but what this error shows is that mixing meson and autotools
will be troublesome. OTOH, a lot of packages are not meson-able yet, so
autotools has still to be used. Conclusion: refrain using meson for the
time being.
[interoperability dream]
Maybe meson could generate .la files... Or libtool could use pkgconfig
files...
[interoperability reality]
I do not see any option for that
Doesn't LFS advise removal of .la files nowadays? I seem to recall
something was documented.
Unfortunately I do not think that works well. Every autotools package
installs .la files and libtool insists on using them. It would be nice if
libtool would just use pkgconfig.
Anyways, it seems you had installed autotools version of atk, which
provided its .la file, updated to meson one, which did not provide .la
file, and something that linked against libatk.la now fails. Find out what
by grepping "libatk.la" in /usr/lib/*.la. Libtool does not add deps to .la
files when there was never a .la file in the first place
That seems to be a good workaround. The next time I run into a problem,
I'll try it.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
