Re: [Fink-users] Problem with qt4-x11 from mac newcomer

[Martin C. <cos...@wa...>]

alexor wrote:
> thank you for the reply. I am using Leopard on a MacBook.
> 
> On closer inspection of the log there is 
> 
> c++ -c -pipe -Os -Wall -W -D__USE_WS_X11__ -I../../../mkspecs/darwin-g++ -I.
> -I. -o iconv.o iconv.cpp
> c++ -headerpad_max_install_names
> -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
> -prebind -o iconv iconv.o     
> Undefined symbols:
>   "_iconv", referenced from:
>       _main in iconv.o
>   "_iconv_close", referenced from:
>       _main in iconv.o
>   "_iconv_open", referenced from:
>       _main in iconv.o

I am seeing this, too, but it does not prevent qt4-x11 from building 
correctly. In fact, you have to put it into its context. In my build 
log, I see that paragraph preceded by

POSIX iconv auto-detection... ()

and ended by

ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [iconv] Error 1
POSIX iconv disabled.
GNU libiconv auto-detection... ()

So the error is in fact not an error, but simply a test of the flavor of 
iconv that is installed. The GNU libiconv auto-detection then succeeds.

The tests are somewhat unrealistic, because they use neither 
-I/sw/include nor -L/sw/lib, so they are not even looking at Fink's 
iconv, which is the one that is used afterwards (at least the dylib, I 
am not so sure about the header). Indeed, if one looks at the 
gnu-libiconv binary that is created in this test, one sees that it is 
linked with /usr/lib/libiconv.2.dylib.

> There seems to be a lot of activity on the fink lists regarding this problem
> (not only in relation to qt4-x11) and I am not sure how to resolve it. I
> tried various suggestions that had been posted and I even tried moving the
> /usr/local directory out of the way but to no avail - stumped. I reinstalled
> libiconv-dev, libiconv-bin and libiconv.

The annoying thing is that many people, including me, and IIRC also the 
qt4-x11 maintainer, do *not* get the build crash you are seeing, and 
therefore cannot really investigate the cause.

Oh, and BTW you still haven't said which version of OSX and what 
architecture you are running. Xcode and gcc versions might be of 
interest, too.

-- 
Martin