Re: Handling dynamic libraries with Libtool and Ruby on Mac OS X
Peter O'Gorman <[EMAIL PROTECTED]> writes: > On Thu, 2006-07-13 at 17:11 +0200, Roland Levillain wrote: >> What do you people from Libtool and Ruby think about the behaviors of >> Libtool and Ruby? Should libtool create `.bundle' files on >> Mac OS X/Darwin? Or should ruby accept to load `.so' files as valid >> dynamic modules on this OS? >> >> Thanks in advance for your answers and advice! > Use the -shrext flag when linking the library on Mac OS X and specify > ".bundle" as its argument. Thanks! That's what I was looking for. ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: questions about DLLs built with libtool - multiple output files...
Brian Dessent <[EMAIL PROTECTED]> writes: >> Also, I seem to recall reading that it was possible to generate dlls >> which either did or did not depend on the cygwin dll being present on >> the machine. True? > > It is possible, but it's not quite that simple. There are essentially > two separate toolchains: cygwin and mingw. Cygwin implements its own C > library and POSIX emulation layer (cygwin1.dll), whereas mingw targets > the existing Microsoft-provided C library (MSVCRT.DLL) and provides > essentially zero compatibility/emulation layering. > > > Cygwin's gcc provides the necessary framework for using both toolchains > at once, via the -mno-cygwin switch, which is what you are probably > referring to. So it is true that under Cygwin you can create a DLL that > does not depend on cygwin1.dll by simply using -mno-cygwin. However, it > does not just magically remove this dependancy, it switches the compiler > to a very different toolchain, with an associated set of issues as > explained above. This means it's not a magic bullet that can just > surgically remove Cygwin without any other changes. Brian, Is there something special I need to do to make it use the ming compilers, in addition to the cross-compile stuff? I am trying it like this: ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin CC="gcc -no-cygwin" But when searching for a compiler, it tells me this: checking for i686-pc-mingw32-xlc... gcc -no-cygwin What is this i686-pc-mingw32-xlc business? Thanks, Ed -- Ed Hartnett -- [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: questions about DLLs built with libtool - multiple output files...
Howdy all! I am still trying to get my library to build on cygwin with mingw tools. I am getting two errors. One is the gcc.exe is not recognizing the -no-cygwin option. Should it? Another is that convenience library libnetcdf2.a is not found, yet there it is... THanks for any help... Ed libtool: compile: gcc -no-cygwin -DHAVE_CONFIG_H -I. -I. -I.. -I../fortran -g -O2 -MT v2i.lo -MD -MP -MF .deps/v2i.Tpo -c v2i.c gcc.exe: unrecognized option `-no-cygwin' libtool: compile: mv -f "v2i.o" ".libs/v2i.o" libtool: compile: gcc -no-cygwin -DHAVE_CONFIG_H -I. -I. -I.. -I../fortran -g -O2 -MT v2i.lo -MD -MP -MF .deps/v2i.Tpo -c v2i.c >/dev/null 2>&1 /bin/sh ../libtool --tag=CC --mode=link gcc -no-cygwin -g -O2 -o libnetcdf2.la v2i.lo libtool: link: rm -fr .libs/libnetcdf2.a .libs/libnetcdf2.la libtool: link: ar cru .libs/libnetcdf2.a .libs/v2i.o libtool: link: ranlib .libs/libnetcdf2.a libtool: link: creating libnetcdf2.la libtool: link: ( cd ".libs" && rm -f "libnetcdf2.la" && ln -s "../libnetcdf2.la" "libnetcdf2.la" ) /bin/sh ../libtool --tag=CC --mode=link gcc -no-cygwin -g -O2 -o libnetcdf.la -rpath /usr/local/lib -version-info 3:6:2 -no-undefined attr.lo ncx.lo putget.lo dim.lo error.lo libvers.lo nc.lo string.lo v1hpg.lo var.lo posixio.lo libnetcdf2.la libtool: link: rm -fr .libs/libnetcdf.dll.a .libs/libnetcdf.lax libtool: link: gcc -no-cygwin -shared .libs/attr.o .libs/ncx.o .libs/putget.o .libs/dim.o .libs/error.o .libs/libvers.o .libs/nc.o .libs/string.o .libs/v1hpg.o .libs/var.o .libs/posixio.o -Wl,--whole-archive ./.libs/libnetcdf2.a -Wl,--no-whole-archive -o .libs/libnetcdf-1.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/libnetcdf.dll.a Creating library file: .libs/libnetcdf.dll.a gcc.exe: unrecognized option `-no-cygwin' libtool: link: (cd .libs/libnetcdf.lax/libnetcdf2.a && ar x /home/ed/netcdf-3/libsrc/./.libs/libnetcdf2.a) /home/ed/netcdf-3/libsrc/./.libs/libnetcdf2.a: No such file or directory c:\MinGW\bin\ar.exe: make[2]: *** [libnetcdf.la] Error 9 make[2]: Leaving directory `/home/ed/netcdf-3/libsrc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ed/netcdf-3' make: *** [all] Error 2 bash-3.1$ ls -l /home/ed/netcdf-3/libsrc/./.libs/libnetcdf2.a -rwxrwxrwx 1 ed None 37172 Jul 19 14:22 /home/ed/netcdf-3/libsrc/./.libs/libnetcdf2.a bash-3.1$ which gcc /cygdrive/c/MinGW/bin/gcc bash-3.1$ echo $PATH /usr/local/bin:/usr/X11R6/bin:/cygdrive/c/MinGW/bin:/usr/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/ATI Technologies/ATI Control Panel:/cygdrive/c/Program Files/Common Files/GTK/2.0/bin:/cygdrive/c/PROGRA~1/SecureFX bash-3.1$ -- Ed Hartnett -- [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: questions about DLLs built with libtool - multiple outputfiles...
Ed Hartnett wrote: > ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin CC="gcc > -no-cygwin" This is a typo, you want "-mno-cygwin" not "-no-cygwin". > But when searching for a compiler, it tells me this: > > checking for i686-pc-mingw32-xlc... gcc -no-cygwin > > What is this i686-pc-mingw32-xlc business? That would appear to be libtool or autoconf searching for a working C compiler, since "gcc -no-cygwin" probably gave an error about incorrect parameters. But that's just a wild guess. Brian ___ http://lists.gnu.org/mailman/listinfo/libtool
Recheck Bug??
Hi together! seems i found a little ... äähmm ... bug(??) ;o) when i do: $ CC=wgcc CXX=wgcc LD=wgcc ../libtool-1.5.22/configure --prefix=/wamas/libtool/test/binary and after that bootstrap libtool, and do "$ gmake" libtool trys to recheck with: $ gmake/bin/sh ./config.status --recheckrunning /bin/sh ../libtool-1.5.22/configure --prefix=/wamas/libtool/test/binary CC=wgcc CXX=wgcc --enable-ltdl-install --no-create --no-recursion which isn't too good, since LD is not set, and /opt/gcc3.3/blahblah.../ld is used instead of wgcc, which breaks everything For now i just configure manually which works perfectly, but you know ;o) Regards, Markus ___ http://lists.gnu.org/mailman/listinfo/libtool
Recheck Bug...
Hi! Seems i was wrong with the recheck bug. Whenever i reconfigure in a directory where i allready configured libtool i get this: rm -f ltmain.shTdate=`/bin/sh ../libtool-1.5.22/mkstamp < ../libtool-1.5.22/ChangeLog` && sed -e 's/@''PACKAGE@/libtool/' -e 's/@''VERSION@/1.5.22/' -e "s%@""[EMAIL PROTECTED]%" ../libtool-1.5.22/ltmain.in > ltmain.shTmv -f ltmain.shT ../libtool-1.5.22/ltmain.sh || (rm -f ../libtool-1.5.22/ltmain.sh && cp ltmain.shT ../libtool-1.5.22/ltmain.sh && rm -f ltmain.shT)cp ../libtool-1.5.22/ltmain.sh ../libtool-1.5.22/libltdl/configure: error: tag name "CXX" already exists h Regards, Markus ___ http://lists.gnu.org/mailman/listinfo/libtool
