On 2007-04-05 16:49:38 -0400, Daniel J. Luke wrote:
The problem IIRC has to do with mismatched headers and library.
Yes, probably because the Makefile is incorrect.
So you'll want to do
locate readline.h
and see if there's a stray one (in /usr/local/include, probably) that's causing the build to choke.
No: prunille:~> locate include/readline/readline.h /Developer/SDKs/MacOSX10.4u.sdk/usr/include/readline/readline.h /opt/local/include/readline/readline.h /opt/local/var/db/dports/build/_Users_vinc17_software_darwinports_dports_devel_readline/work/destroot/opt/local/include/readline/readline.h /opt/local/var/db/dports/software/readline/5.1.004_0/opt/local/include/readline/readline.h /opt/local/var/db/dports/software/readline/5.2.001_0/opt/local/include/readline/readline.h /usr/include/readline/readline.h The problem is a mismatch between Apple's linker and gcc. A -I/usr/include is ignored by gcc (because it is in the system path), while with -L/usr/lib, this directory has the precedence. In short, using -L/usr/lib is incorrect. -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)