|
From: | Vincent Torri |
Subject: | Re: problem with mingw-w64 and libraries like libole32.a |
Date: | Sun, 26 Sep 2010 08:00:42 +0200 (CEST) |
Hey
Any news about the problem ?
so, i have provided the libtool debug output [1] and provided the informations that Charles Wilson asked me to give [2].
Any idea of the problem ? Vincent Torri [1] http://lists.gnu.org/archive/html/libtool/2010-08/msg00040.html [2] http://lists.gnu.org/archive/html/libtool-patches/2010-09/msg00310.html
Vincent Torri On Wed, 25 Aug 2010, Vincent Torri wrote:On Wed, 25 Aug 2010, Ralf Wildenhues wrote:* Vincent Torri wrote on Wed, Aug 25, 2010 at 06:46:31AM CEST:I checked out libtool git 2 days ago and try to compile a library that uses libole32 or libws2_32 with mingw-w64 (cross compilation on linux). I get the usual message: *** Warning: linker path does not have real file for library -lole32. etc... No problem with mingw. A guy from mingw-w64 told me that it worked before. Could this be a regression ?Please rerun the 'libtool --mode=link' command with --debug added as first argument after libtool, and post both the complete command as well as all output. Thanks.Command:/bin/bash ../../../libtool --tag=CC --mode=link x86_64-w64-mingw32-gcc -Wall -Wextra -Wshadow -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -g -O2 -no-undefined -Wl,--enable-auto-import -version-info 0:1:0 -L/home/torri/local/mingw64/lib -o libdl.la -rpath /home/torri/local/mingw/lib libdl_la-dlfcn.lo ../../../src/lib/libevil.laoutput: in the attached file. Vincent Torri
[Prev in Thread] | Current Thread | [Next in Thread] |