|
From: | jemarch |
Subject: | Re: [pdf-devel] Undefined symbols libiconv libiconv_close libiconv_open |
Date: | Sun, 15 Jun 2008 01:36:23 +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) |
>> If disabled, it will compile correctly in Darwin. Should we put it as a >> condition only for compiling in Windows environment? > > Seems to be a good solution. > Just prepared a patch for this, which will prevent using --no-undefined except for mingw32 compilation (so Mac OS X compilation should not use it). Not sure if this is the best way to handle this, anyway. I think that it is a good solution for now. Later we can investigate the reason for Macos10 to crash when using --no-undefined. Please commit it and ack.
[Prev in Thread] | Current Thread | [Next in Thread] |