[vbox-dev] Build issues with 4.0.12 and 4.1.2 on OSX Lion
martin at lispworks.com
Tue Sep 13 10:41:56 PDT 2011
>>>>> On Tue, 13 Sep 2011 09:17:53 -0700, Arend Dittmer said:
> Thanks again. It looks like you are right ... there are no function
> prototypes for the symbols libiconv, libiconv_open and libiconv_close
> in /Developer/SDKs/MacOSX10.6.sdk/usr/include/iconv.h which corresponds to
> Question is ... which flag do I set to have the build pick up
> the MacOSX10.6.sdk version?
> Just not sure what VirtualBox build flag makes it pick up the right header.
Do you really need --with-openssl-dir=/opt/local in the configuration? I
suspect that option adds /opt/local/include to the include path, so the
compiler finds /opt/local/include/iconv.h by accident.
> On Tue, Sep 13, 2011 at 7:10 AM, François Revol <revol at free.fr> wrote:
> > Le 13/09/2011 16:05, Arend Dittmer a écrit :
> > > Thank you Darshan and Francois for getting back to me. For the build that
> > > fails the linker tries to link with libiconv in
> > > /Developer/SDKs/MacOSX10.6.sdk:
> > [...]
> > > If I manually run the command in the same directory and force linking
> > with
> > > the macports libiconv it actually builds. The macports library is
> > universal:
> > It's possible that it always finds the iconv headers from MacPorts
> > first regardless, then it fails linking with the SDK one due to
> > mismatched headers and lib.
> > > The issue is that libiconv in /Developer/SDKs/MacOSX10.6.sdk* *does not
> > have
> > > the _libiconv symbol (and the other symbols that are missing which are
> > > _libiconv_open and _libiconv_close) for 64-bit:
> > By experience, there are several "versions" of the iconv symbol names.
> > This is meant to make it possible to link with an external libiconv or
> > the one included with the libc on some platforms.
> > For ex. when defining LIBICONV_PLUG.
> > If it picked up the wrong headers then it will try to use wrong symbols.
> > François.
> Arend Dittmer
> Phone: 415 497 7797
> e-mail: arend at mypocketxp.com
More information about the vbox-dev