From: Jean-François B. <jea...@be...> - 2011-01-25 22:40:20
|
Am 25/01/2011 23:09, schrieb Charles Wilson: >>> Unless you take explicit steps to force the MSYS environment into "msys" >>> mode, by default it will enforce*mingw* behavior. What does 'uname -s' >>> say,*within the same shell instance that you run configure*? >> uname -s = MINGW32_NT-5.1 > > Good, that means MSYS is acting in its normal "pretend I am 'mingw'" > mode. So...odds are that Howard is not correct; your build is targeting > mingw, NOT msys. The real proof of this would be the third or fourth > line of your configure output, which should say something like: > > checking build system type... i686-pc-mingw32 > checking host system type... i686-pc-mingw32 configure:2150: checking build system type configure:2168: result: i386-pc-mingw32 configure:2190: checking host system type configure:2205: result: i386-pc-mingw32 configure:2227: checking target system type configure:2242: result: i386-pc-mingw32 So i386 instead of i686. I don´t know the consequences of this. > [...] > No, the name "mingw32-gcc" is really only used if you are doing a > deliberate "cross-compile" style build, with --host=mingw32. MSYS > arranges things so that you can use the "native" name of the compiler > ('gcc') and still get mingw32 output (that is, you don't need to specify > --host nor --build when configuring). MSYS "lies" and pretends to BE > mingw32 as far as all that goes...but gives you some semblance of unix > support to make life a little easier. Thank you for your explanations, that nicely supplement the FAQ sections on 'mingw32-make vs MSYS make' and 'mingw32-gcc vs. gcc' > verify it by building some little hello world app: > > #include <stdio.h> > int main(int argc, char* argv[]) > { > printf("Hello, World!\n"); > return 0; > } OK I'll work on that until bedtime (I'm in Germany). Yet I believe Howard Chu has a point when I watch objdump: $ objdump -p slapd.exe|grep 'DLL Name' DLL Name: msys-crypto-1.0.0.dll DLL Name: msys-ssl-1.0.0.dll DLL Name: libgnurx-0.dll DLL Name: ADVAPI32.DLL DLL Name: KERNEL32.dll DLL Name: msvcrt.dll DLL Name: msvcrt.dll DLL Name: RPCRT4.dll DLL Name: WS2_32.dll Then 'info sharedlibrary' in gdb (gdb) info sharedlibrary From To Syms Read Shared Object Library 0x7c911000 0x7c9c8eb8 Yes (*) C:\WINDOWS\system32\ntdll.dll 0x7c801000 0x7c907c84 Yes (*) C:\WINDOWS\system32\kernel32.dll 0x64d01000 0x64d300d4 Yes (*) C:\Programme\Alwil Software\Avast5\snxhk.dll 0x62a01000 0x62b49fb4 Yes (*) C:\MinGW\msys\1.0\bin\msys-crypto-1.0.0.dll 0x60801000 0x60902878 Yes (*) C:\MinGW\msys\1.0\bin\msys-1.0.dll 0x6b8c1000 0x6b90e050 Yes (*) C:\MinGW\msys\1.0\bin\msys-ssl-1.0.0.dll 0x71041000 0x71079b80 Yes C:\MinGW\msys\1.0\local\bin\libgnurx-0.dll 0x77be1000 0x77c37d74 Yes (*) C:\WINDOWS\system32\msvcrt.dll 0x77da1000 0x77e49af8 Yes (*) C:\WINDOWS\system32\advapi32.dll 0x77e51000 0x77ee2558 Yes (*) C:\WINDOWS\system32\rpcrt4.dll 0x77fc1000 0x77fd0888 Yes (*) C:\WINDOWS\system32\secur32.dll 0x71a11000 0x71a26dc8 Yes (*) C:\WINDOWS\system32\ws2_32.dll 0x71a01000 0x71a07320 Yes (*) C:\WINDOWS\system32\ws2help.dll 0x76f71000 0x76f77230 Yes (*) C:\WINDOWS\System32\winrnr.dll 0x76ee1000 0x76f062f4 Yes (*) C:\WINDOWS\system32\dnsapi.dll 0x76f21000 0x76f4c290 Yes (*) C:\WINDOWS\system32\wldap32.dll 0x719b1000 0x719efc48 Yes (*) C:\WINDOWS\System32\mswsock.dll 0x10001000 0x100085ee Yes (*) C:\Programme\FRITZ!DSL\SARAH.DLL 0x78521000 0x785c27ac Yes (*) C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e\msvcr90.dll 0x00b71000 0x00b88e12 Yes (*) C:\Programme\FRITZ!DSL\BLOCK.DLL 0x76f81000 0x76f850a0 Yes (*) C:\WINDOWS\system32\rasadhlp.dll 0x66711000 0x667686ba Yes (*) C:\WINDOWS\system32\hnetcfg.dll 0x77ef1000 0x77f38870 Yes (*) C:\WINDOWS\system32\gdi32.dll 0x7e361000 0x7e3f0de4 Yes (*) C:\WINDOWS\system32\user32.dll 0x76331000 0x7634cc6c Yes (*) C:\WINDOWS\system32\imm32.dll 0x719f1000 0x719f7114 Yes (*) C:\WINDOWS\System32\wshtcpip.dll (*): Shared library is missing debugging information. (gdb) Is is possible that using msys-ssl DLL causes the linker to link the msys DLL ? That was my last question for tonight, with my thanks again. JF |