1.7.0 beta & rc1: libcurl errors

[Ryan Schmidt]

On Dec 9, 2008, at 07:20, Jay Levitt wrote:

> Joshua Root wrote:
>
>> Could the wrong libcurl be picked up if there is something like
>> LDFLAGS=-L/opt/local/lib in the environment? If that's what  
>> happened to
>> Jay, it shouldn't be a problem with selfupdate because the  
>> environment
>> is sanitised.
>
> I do, in fact, have that:
>
> CPATH=/opt/local/include
> CPPFLAGS=-I/opt/local/include
> LDFLAGS=-L/opt/local/lib
> LIBTOOLIZE=/opt/local/bin/glibtoolize
> PATH=/usr/local/bin:/usr/local/sbin:/Users/jay/bin:/opt/local/bin:/ 
> opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/ 
> Applications/Utilities/diglloyd/disktester:/usr/local/git/bin:/opt/ 
> local/lib/postgresql83/bin


Stuff in /usr/local can and does conflict with MacPorts-installed  
software. Perhaps you have a different version of curl in there. See  
what happens if you rename /usr/local to e.g. /usr/local-off.