Neel Smith wrote:
[]
configure:2415: checking for C compiler default output file name
configure:2418: gcc -I/sw/lib/fontconfig2/include/  -I/sw/include -L/sw/lib conf
test.c -liconv -lintl -lexpat >&5
ld: warning prebinding not disabled because (__PAGEZERO segment (address = 0x0 s
ize = 0x1000) of a.out overlaps with __TEXT segment (address = 0x0 size = 0x1d00
0) of /sw/lib/libexpat.0.dylib
ld: warning prebinding not disabled because (__TEXT segment (address = 0x1000 si
ze = 0x2000) of a.out overlaps with __TEXT segment (address = 0x0 size = 0x1d000
) of /sw/lib/libexpat.0.dylib
ld: warning prebinding not disabled because (__DATA segment (address = 0x3000 si
ze = 0x1000) of a.out overlaps with __TEXT segment (address = 0x0 size = 0x1d000
) of /sw/lib/libexpat.0.dylib
ld: warning prebinding not disabled because (__LINKEDIT segment (address = 0x400
0 size = 0x1000) of a.out overlaps with __TEXT segment (address = 0x0 size = 0x1
d000) of /sw/lib/libexpat.0.dylib
configure:2421: $? = 0
configure:2467: result: a.out
configure:2472: checking whether the C compiler works
configure:2478: ./a.out
dyld: ./a.out version mismatch for library: /sw/lib/libexpat.0.dylib (compatibil
ity version of user: 6.0.0 greater than library's version: 5.0.0)
[]
For what it's worth, I have a current expat package installed via fink (1.95.7-1). /sw/lib/libexpat.dylib is a symbolic link to /sw/lib/libexpat.0.5.0.dylib So why is a.out expecting version 6 of libexpat? What have I messed up?

Actually, libexpat.0.5.0.dylib most likely has a compatibility version of 6.0.0. You can check this with "otool -L /sw/lib/libexpat.0.5.0.dylib".


I see only two possible scenarios that give the output you are seeing:

Either your /sw/lib/libexpat.0.dylib is a symlink to something else than /sw/lib/libexpat.0.5.0.dylib that it should be.

Or, more likely, you have a /usr/local/lib/libexpat.dylib that points to an older version of libexpat. The funny thing in this case is that this older thing, wherever it is actually installed, must have an install_name of /sw/lib/libexpat.0.dylib (test it again with "otool -L /usr/local/lib/libexpat.dylib"). Either you have played with these symlinks yourself, or you have some evil third-party stuff that not only pollutes /usr/local/lib, but does so by hijacking Fink libraries.

--
Martin



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to