bug#79468: libtool-2.6.0 released [alpha]
Kirill Makurin <[email protected]> Fri, 2 Jan 2026 15:43:21 +0000
| Newsgroups | gmane.comp.gnu.libtool.bugs |
|---|---|
| Message-ID | <LV5PR05MB998298833342185F38E3A9A507B1BBA@LV5PR05MB998298.namprd05.prod.outlook.com> |
--_000_LV5PR05MB998298833342185F38E3A9A507B1BBALV5PR05MB998298_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Let's see how it goes in configure's output. The build machine is detected = correctly... ``` checking build system type... x86_64-w64-mingw32 checking host system type... x86_64-w64-mingw32 ``` And a little later... ``` checking how to convert x86_64-w64-mingw32 file names to x86_64-w64-mingw32= format... func_convert_file_msys_to_w32 checking how to convert x86_64-w64-mingw32 file names to toolchain format..= . func_convert_file_msys_to_w32 checking whether cygpath is installed... yes ``` I feel like check for cygpath must happen first, isn't it? Any idea what co= uld be wrong? - Kirill Makurin ________________________________ From: Ileana Dumitrescu Sent: Saturday, January 3, 2026 12:36 AM To: Kirill Makurin Cc: [email protected] Subject: Re: bug#79468: libtool-2.6.0 released [alpha] On 02/01/2026 17:27, Kirill Makurin wrote: > Hi Ileana, Hi Kirill, > I was thinking maybe the issue is that it does not detect build machine > to be msys2? I'm using Msys2's ucrt64 shell for which plain uname produce= s: > > ``` > MINGW64_NT-10.0-26200 > ``` > > compared to plain uname from Msys2's msys2 shell: > > ``` > MSYS_NT-10.0-26200 > ``` > > Could it be potential source of this issue? A check for the host and build is done before the values for file conversion are checked for caching, so that may be your issue.. AS_CASE([$host], [*-*-mingw* | *-*-windows* | *-*-cygwin*], [AS_CASE([$build], [*-*-mingw* | *-*-windows* | *-*-cygwin*], [AC_MSG_CHECKING([whether cygpath is installed]) Do you have lt_cv_cygpath_installed or lt_cv_cmd_slashes cached? -- Ileana Dumitrescu GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354 --_000_LV5PR05MB998298833342185F38E3A9A507B1BBALV5PR05MB998298_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> Let's see how it goes in configure's output. The build machine is detected = correctly...</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> ```</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> checking build system type... x86_64-w64-mingw32<br> checking host system type... x86_64-w64-mingw32</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> ```</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> And a little later...</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> ```</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> checking how to convert x86_64-w64-mingw32 file names to x86_64-w64-mingw32= format... func_convert_file_msys_to_w32<br> checking how to convert x86_64-w64-mingw32 file names to toolchain format..= . func_convert_file_msys_to_w32</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> checking whether cygpath is installed... yes</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> ```</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> I feel like check for cygpath must happen first, isn't it? Any idea what co= uld be wrong?</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> <br> </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" clas= s=3D"elementToProof"> - Kirill Makurin</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <br> </div> <hr style=3D"display: inline-block; width: 98%;"> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <b>From:</b> Ileana Dumitrescu<br> <b>Sent:</b> Saturday, January 3, 2026 12:36 AM<br> <b>To:</b> Kirill Makurin<br> <b>Cc:</b> [email protected]<br> <b>Subject:</b> Re: bug#79468: libtool-2.6.0 released [alpha] </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"font-size: 11pt;">On 02/01/2026 17:27, Kirill Makurin wrote:<= br> > Hi Ileana,<br> <br> Hi Kirill,<br> <br> > I was thinking maybe the issue is that it does not detect build machin= e<br> > to be msys2? I'm using Msys2's ucrt64 shell for which plain uname prod= uces:<br> ><br> > ```<br> > MINGW64_NT-10.0-26200<br> > ```<br> ><br> > compared to plain uname from Msys2's msys2 shell:<br> ><br> > ```<br> > MSYS_NT-10.0-26200<br> > ```<br> ><br> > Could it be potential source of this issue?<br> <br> A check for the host and build is done before the values for file<br> conversion are checked for caching, so that may be your issue..<br> <br> AS_CASE([$host],<br> [*-*-mingw* | *-*-windows* | *-*-cygwin*],<br> [AS_CASE([$build],<br> [*-*-mingw* | *-*-windows* | *-*-cygwin*],<br> [AC_MSG_CHECKING([whether cygpath is installed])<b= r> <br> Do you have lt_cv_cygpath_installed or lt_cv_cmd_slashes cached?<br> <br> --<br> Ileana Dumitrescu<br> <br> GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354<br> <br> </div> </body> </html> --_000_LV5PR05MB998298833342185F38E3A9A507B1BBALV5PR05MB998298_--