Compiling with MinGW

This is not exactly a bug in a strict since but it is a complication of building software with MinGW. Just a little back ground I was looking to build the latest version of wvware so that I end up with a windows stand alone binary. The environment that I was working on was: Windows 2003

Re: Cannot build 1.5.22 on HP-UX 11.00

Hello Johannes, First off, the mailing list in question is named bug-libtool, not libtool-bug. I wonder how it still arrived here, maybe the latter is an alias of the former? * Johannes Abt wrote on Fri, Aug 04, 2006 at 05:22:21PM CEST: > > during the build of libtool-1.5.22, cc is invoked with

Re: Compiling with MinGW

Hello Matthew, * [EMAIL PROTECTED] wrote on Fri, Aug 04, 2006 at 08:12:20PM CEST: > > This is not exactly a bug in a strict since but it is a complication > of building software with MinGW. > gcc -g -O2 -Wl,--disable-auto-import -o .libs/test-names.exe test- > names.o -Lc:/progra~1/wv libuni

Re: Compiling with MinGW

Exactly. Did you compile GCC yourself but installed it in MSYS /bin? I think that was the thing not to do, as it inhibits the automatic path translation. See http://www.mingw.org/mingwfaq.shtml#faq-usingwithmsys for more info. The gcc used comes from mingw. I installed MinGW by Downloading th

Re: Compiling with MinGW

Matthew McGillis wrote: > found that by simply > editing the libtool used in both of the above cases and adding: > > case $deplib in >/home*) deplib="c:/cygwin"$deplib;; > esac > > ... > I was able to complete the compiles and generate a version of > wvware-1.2.1

Re: Compiling with MinGW

On Fri, 4 Aug 2006, Bruno Haible wrote: ... I was able to complete the compiles and generate a version of wvware-1.2.1 that worked standalone on windows. You appear to be using mingw as a development environment. I don't know whether libtool supports that. MinGW is not a development environme

Re: How to use --whole-archive ld arg with libtool?

Dear libtoolers, I'm a little stumped by libtools handling of the -Wl,--whole-archive option. According to the documentation, such an option (-Wl,...) should be placed on the linker's command line right where it is located on libtool's command line. However, that does not appear to be the case. It

[sr #105489] --whole-archive doesn't work on OSX

Follow-up Comment #1, sr #105489 (project libtool): Mac OS/X does have a way to turn off the all_load option. The (undocumented) option is -noall_load. I have this from Apple compiler developers. ___ Reply to this item at:

Re: How to use --whole-archive ld arg with libtool?

Hi Reid, * Reid Spencer wrote on Fri, Aug 04, 2006 at 09:32:27PM CEST: > > libtool --tag=CXX --tag=disable-shared --mode=link g++ \ > -o myprog -Wl,--whole-archive -llib1 -llib2 -Wl,--no-whole-archive \ > -llib3 -llib4 > > This seems to generate a link command like: > > g++ -o myprog -Wl,--

Re: How to use --whole-archive ld arg with libtool?

I forgot the main part of the answer, sorry. You wrote: >> The reason I need this capability is to ensure that all the symbols from >> lib1 and lib2 are available to any dlopen'd modules that get loaded by >> "myprog". The _portable_ way to ensure this is to link each of the modules against the l

Re: fatal "make check" with libtool-1.5.18 on HP-UX 11.00

Hello Johannes, * Johannes Abt wrote on Fri, Aug 04, 2006 at 05:32:08PM CEST: > > as I had some problem with libtool-1.5.22, I built libtool-1.5.18 on a > hppa2.0w-hp-hpux11.00 with CC=cc, I tried "make check". > "make" told me to send the results, so here we go: > 33 of 63 tests failed > (49 te

Re: Building libgpg-error on OS X 10.4

Hello, * Marcus Brinkmann wrote on Wed, Aug 02, 2006 at 08:46:59PM CEST: > > it seems that the libtool+gettext+automake machinery does not work > perfectly for libraries using gettext. If you use > --with-included-gettext, then a static version of libintl will be > built, and LTLIBINTL is set to

Re: How to use --whole-archive ld arg with libtool?

Hi Ralph, Thanks for the quick response. Some follow-up questions: On Sat, 2006-08-05 at 02:25 +0200, Ralf Wildenhues wrote: > Hi Reid, > > Yes. Generic position-dependent linker flags are not implemented at > this point. Okay :) > If you control lib1 and lib2 though (i.e., they are built

Re: How to use --whole-archive ld arg with libtool?

Hi Ralph, Sorry to be a pain, but again, more questions .. :) On Sat, 2006-08-05 at 02:30 +0200, Ralf Wildenhues wrote: > I forgot the main part of the answer, sorry. You wrote: > >> The reason I need this capability is to ensure that all the symbols from > >> lib1 and lib2 are available to any