|
From: | jemarch |
Subject: | Re: [pdf-devel] Undefined symbols libiconv libiconv_close libiconv_open |
Date: | Sun, 15 Jun 2008 18:10:24 +0200 |
User-agent: | Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
> Do you mean that you didn't even need to remove the --no-undefined in the > Makefile.am? No, you need to remove the -no-undefined either by commenting the line or setting the value to empty. I also tested with your recent patch (if COMPILE_W32_SYSTEM) and it also works :-) I have been investigating a bit about the -no-undefined + macos10 problem. The macos10 static linker (ld) is not able to see symbols provided in loadable bundles or custom frameworks/dynamic libraries. It seems that libiconv is provided in that way. So the fix installed by aleksander does The Right Thing(TM). The use of -no-undefined in the linking stage is only needed when compiling for the mingw32 platform.
[Prev in Thread] | Current Thread | [Next in Thread] |