|
From: Jonathan B. <jon...@gm...> - 2015-02-19 19:02:05
|
Am 19.02.2015 um 19:51 schrieb Ray Donnelly: > On Thu, Feb 19, 2015 at 6:46 PM, Jonathan Baecker <jon...@gm...> wrote: >> Am 19.02.2015 um 19:30 schrieb NAKAI Yuta: >>> ---------------------------------------- >>>> Date: Thu, 19 Feb 2015 19:24:33 +0100 >>>> From: jon...@gm... >>>> To: msy...@li... >>>> Subject: [Msys2-users] libtool version mismatch >>>> >>>> Hello everybody, >>>> after the last update I am not able to compile libgnurx by my self >>>> anymore. I get a version mismatch in libtool: >>>> >>>> libtool: Version mismatch error. This is libtool 2.4.6, but the >>>> libtool: definition of this LT_INIT comes from libtool 2.4.5. >>>> libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 >>>> libtool: and run autoconf again. >>> This explains everything. >>> Run autoreconf -fiv, then configure and make. >>> >> Ok now I find out that msys2 use libtool 2.4.5 and mingw-w64 use 2.4.6. >> Maybe this is the reason. >> I there a way to force the compiling process to only use one version? > It doesn't matter what one uses versus the other. If you run > mingw32_shell.bat or mingw64_shell.bat instead of msys2_shell.bat then > it will not run MSYS2's version of libtool. Yes but this is the problem, I don't use the msys2_shell.bat or mingw*_shell.bat. I start msys with a shortcut, that have this call: mintty.exe -i /msys2.ico /usr/bin/bash --login I need this because I start msys2 from a other batch file. And when mintty is running it load its own profile, what I had build. But you are right, I was try it now with the mingw32_shell.bat and there it works. I need a deeper look in the profiles to find out why this is happen and what I did wrong in my custom way. Regards Jonathan |