GNU bug report logs - #78745
Installed libtool script produces invalid .la files

Previous Next

Package: libtool;

Reported by: Kirill Makurin <maiddaisuki <at> outlook.com>

Date: Tue, 10 Jun 2025 14:17:02 UTC

Severity: normal

To reply to this bug, email your comments to 78745 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-libtool <at> gnu.org:
bug#78745; Package libtool. (Tue, 10 Jun 2025 14:17:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Kirill Makurin <maiddaisuki <at> outlook.com>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Tue, 10 Jun 2025 14:17:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kirill Makurin <maiddaisuki <at> outlook.com>
To: "bug-libtool <at> gnu.org" <bug-libtool <at> gnu.org>
Subject: Installed libtool script produces invalid .la files
Date: Tue, 10 Jun 2025 14:15:59 +0000

[Message part 1 (text/plain, inline)]
Hi,

I have noticed that installed libtool (configured for MSVC tools) was producing invalid .la files. I have discovered it when I tried to build ncurses with MSVC.

However, we have recently have discovered configuration issue related to configure trying to find a Fortran compiler. This caused building libltdl to fail.

I believe this configuration issue is also responsible for this behavior (invalid .la files). After I started passing FC=no and F77=no to libtool's configure script, I noticed that installed libtool script started behaving as expected.

- Kirill Makurin

[Message part 2 (text/html, inline)]
This bug report was last modified 4 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.