GNU bug report logs - #53479
clang identified as MSVC because of cl* match

Previous Next

Package: libtool;

Reported by: Brecht Sanders <brecht <at> sanders.org>

Date: Sun, 23 Jan 2022 16:55:02 UTC

Severity: normal

To reply to this bug, email your comments to 53479 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#53479; Package libtool. (Sun, 23 Jan 2022 16:55:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Brecht Sanders <brecht <at> sanders.org>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Sun, 23 Jan 2022 16:55:02 GMT) Full text and rfc822 format available.

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

From: Brecht Sanders <brecht <at> sanders.org>
To: Bug-libtool <at> gnu.org
Subject: clang identified as MSVC because of cl* match
Date: Sun, 23 Jan 2022 14:03:33 +0100
[Message part 1 (text/plain, inline)]
When building MinGW-w64 with clang I ran into issues compiling 
|winpthreads|.

Somehow |libtool| would always build as if the compiler was MSVC (|.lib| 
instead of |.a|, MSVC-style linker flags).

After digging into what caused this I found that 
|mingw-w64-libraries/winpthreads/configure| matches the compiler with 
|cl*| to detect MSVC (|cl.exe|) but as I'm using |clang.exe| this also 
matches.

But there are more similar issues in m4/libtool.m4.

How do I get around this, or is this something that can be fixed in libtool?
||||
[Message part 2 (text/html, inline)]

Information forwarded to bug-libtool <at> gnu.org:
bug#53479; Package libtool. (Sun, 23 Jan 2022 17:11:02 GMT) Full text and rfc822 format available.

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

From: Ozkan Sezer <sezeroz <at> gmail.com>
To: Bug-libtool <at> gnu.org
Subject: Re: bug#53479: clang identified as MSVC because of cl* match
Date: Sun, 23 Jan 2022 20:10:00 +0300
On 1/23/22, Brecht Sanders <brecht <at> sanders.org> wrote:
> When building MinGW-w64 with clang I ran into issues compiling
> |winpthreads|.
>
> Somehow |libtool| would always build as if the compiler was MSVC (|.lib|
> instead of |.a|, MSVC-style linker flags).
>
> After digging into what caused this I found that
> |mingw-w64-libraries/winpthreads/configure| matches the compiler with
> |cl*| to detect MSVC (|cl.exe|) but as I'm using |clang.exe| this also
> matches.
>
> But there are more similar issues in m4/libtool.m4.
>
> How do I get around this, or is this something that can be fixed in
> libtool?

I guess the problem is at these two lines at least:
http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=blob;f=m4/libtool.m4;h=20e645b8a554561d68dbe8ed5d9a7df80595e5fa;hb=HEAD#l4950
http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=blob;f=m4/libtool.m4;h=20e645b8a554561d68dbe8ed5d9a7df80595e5fa;hb=HEAD#l5584




Information forwarded to bug-libtool <at> gnu.org:
bug#53479; Package libtool. (Sun, 23 Jan 2022 17:33:01 GMT) Full text and rfc822 format available.

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

From: Brecht Sanders <brecht <at> sanders.org>
To: 53479 <at> debbugs.gnu.org
Date: Sun, 23 Jan 2022 18:32:03 +0100
Just changing the cl* case matches wasn't enough, it was till building 
.lib instead of .a and the static library was not built.

Possible also the code that sets GXX=yes should detect clang as if it 
was gcc.





This bug report was last modified 2 years and 286 days ago.

Previous Next


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