[MBDyn-users] Error in compiling MBdyn 1.5.2 on minGW32+MSYS

徐志華(Gmail) zionman.hsu at gmail.com
Mon Oct 22 14:49:26 CEST 2012


>zionman.hsu at gmail.com
>>
>>
>> I had try to build MBDyn 1.5.2 on minGW32+MSYS, there is a tricky error
>>
>>
>>
>> make[2]: Entering directory `/home/ /mbdyn-1.5.2/libraries/libmbc'
>>
>> /bin/sh ../../libtool --tag=CC   --mode=compile /mingw/bin/gcc.exe
>> -DHAVE_CONFIG_H -I. -I../../include -I../../include -I./../../include
>> -I./../../libraries/libmbc -I./../../mbdyn   -fexceptions -I/mingw/include
>> -I/local/include  -DWINVER=0x0501 -D_WIN32_IE=0x0501 -fno-builtin -pipe
>> -O2 -mms-bitfields -Wno-pedantic-ms-format -march=i686 -mtune=i686 -MT
>> mbc.lo -MD -MP -MF .deps/mbc.Tpo -c -o mbc.lo mbc.c
>>
>> mv -f .deps/mbc.Tpo .deps/mbc.Plo
>>
>> mv: cannot stat `.deps/mbc.Tpo': No such file or directory
>>
>> make[2]: *** [mbc.lo] Error 1
>>
>>
>>
>> I download version 1.5.1 source, the same problem exists.
>>
>> I download version 1.2.6 source, the similar lines in make log shows that
>> “  --mode=compile if /mingw/bin/gcc.exe   then;  .; exit fi ..”,
>> the error doesnot exists.
>>
>>
>>
>> it seems like MBDyn taylored libtool of 1.5.1 and 1.5.2 had ate the next
>> line in make file together, so that it would not get the correct result.
>>
>> I had try to paste the line “/bin/sh ../../libtool   mbc.c” to the
>> MSYS console, it not work (no mbc.Tpo generated)
>>
>> Then I try to paste the partial line “/mingw/bin/gcc.exe   mbc.c” to
>> MSYS console, it work. (mbc.Tpo generated)
>>
>> I try the previous line with original mingw libtool, it works. (mbc.Tpo
>> generated)
>>
>>
>>
>> It seems that MBDyn taylored libtool not workable on minGW32+MSYS
>>
>> Is there any mingw workable MBDyn taylored libtool to be release?
>
>MBDyn's libtool is generated by standard autotools (currently: autoconf
>2.67, automake 1.11.1, libtoolize 2.2.6b) run on Linux, where make
>distcheck is executed to produce the tar.gz that is subsequently
>distributed.  Although neither cygwin nor MSYS/MinGW are officially
>supported, I personally routinely check the build on both systems and I
>did not see any error.
>
>If you can provide a general solution that does not break builds on
>Unix-like systems we will gladly incorporate in the next release;
>otherwise, I would consider this in the gray area between "cannot
>reproduce" and "not ours".
>
>Cheers, p.
>

I had change the definition of  variable LIBTOOL aclocal.m4 to use the minGW32 native libtool  instead of our own libtool, then it seems OK to build MBDyn 1.5.2.




More information about the MBDyn-users mailing list