MacPorts 1.4 rc2
pguyot at kallisys.net
Thu Mar 15 07:48:18 PDT 2007
Basically, you are confusing the behavior of the configure script
with C_INCLUDE_PATH and LIBRARY_PATH environment variables. There is
not much we can do except unset those variables in the configuration
script to prevent this.
For your information, the bug I was mentioning is quite different. It
happens when there is an installation of readline in /usr/local with
headers and no library or with headers and a static library. The
reason is that gcc looks into /usr/local/include as part of the
system includes (and before /usr/include), while ld does not look
into /usr/local/lib and even when told to do so, the -L arguments do
not form a simple priority chain as static libraries and dynamic
libraries are handled differently. In other words, gcc will take the
headers of the newer version of readline in /usr/local while ld will
take the library from the system installation of readline.
Le 15 mars 07 à 22:37, Vincent Lefevre a écrit :
> On 2007-03-15 19:03:37 +0900, Paul Guyot wrote:
>>> prunille:~> locate libreadline.dylib
>>> But only /opt/local/lib/libreadline.dylib and /usr/lib/
>>> should be available.
>> configure (normally?) doesn't look into /opt/local.
> It completely depends on the environment variables. To benefit from
> MacPorts, I have:
More information about the macports-dev