On 2013-09-10 09:47, Ozkan Sezer wrote: > On 9/10/13, Peter Rosin <p...@lysator.liu.se> wrote: >> On 2013-09-10 09:08, Ozkan Sezer wrote: >>> Tell me if you need anything else. >> >> Let's focus on the libtool 2.4.2.393-5d4a if that's ok with >> you. >> >> Can you provide the output from "libtool --config" and >> config.log? I'm not set up to easily duplicate your >> environment... >> >> Cheers, >> Peter >> >> > > Attached ./libtool --config output after configuration. Attached > config.log.
Your error messages indicate that libtool cannot find any files matching the various things associated with -lole32 (and other w32 libraries). I.e. it's not that the any files found are not considered good enough, it's that libtool doesn't find them at all. So, the dlltool --identify code path is in all likelihood perfectly fine, it's just that nothing is being fed to dlltool in the first place. So, something seems to be fishy with your library search path. I notice this in your libtool --config: # Compile-time system search path for libraries. sys_lib_search_path_spec="/opt/W64_180676/lib/gcc /opt/W64_180676/x86_64-w64-mingw32/lib64 /opt/cross_win64/mingw/lib64 " Do you have any libole32.a (or something such) in any of those places? If not, where are they? (and why didn't libtool pick that up when it did $host-gcc --print-search-dirs?) Cheers, Peter _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
