| Re: libcurl error with Mac OS X upgrade [message #81002] |
Mon, 06 August 2012 14:19 |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
On Monday, August 6, 2012 2:51:31 PM UTC-4, smuzz wrote:
> Hi Craig,
>
>
>
> Thanks for the quick reply. What additional information can I provide so we know 'who/what' the culprit is...?
>
>
>
> I am in a remote field site and really need to get this issue solved.
Well, start with my points 1, 2 and 3. Next, find out which software you installed is putting libcurl and libnetcdf into /usr/local/lib.
Craig
|
|
|
|
| Re: libcurl error with Mac OS X upgrade [message #81005 is a reply to message #81002] |
Mon, 06 August 2012 11:51  |
smuzz
Messages: 7
Registered: January 2011
|
Junior Member |
|
|
Hi Craig,
Thanks for the quick reply. What additional information can I provide so we know 'who/what' the culprit is...?
I am in a remote field site and really need to get this issue solved.
Thanks!
|
|
|
|
| Re: libcurl error with Mac OS X upgrade [message #81006 is a reply to message #81005] |
Mon, 06 August 2012 11:29 |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
On Monday, August 6, 2012 12:47:28 PM UTC-4, smuzz wrote:
> Hi, I am trying to run a program in IDL after recently upgrading to
>
> Mac OS X 10.7.4 but am met with the following error....
>
>
>
> Any and all suggestions would be greatly appreciated!
>
>
>
> Library not loaded: /usr/local/lib/libcurl.4.dylib
>
> Referenced from: /usr/local/lib/libnetcdf.7.dylib
>
> Reason: Incompatible library version: libnetcdf.7.dylib requires
>
> version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
The versions of the libraries you are showing are in your personally modified area, /usr/local/lib. This directory is shipped from Apple as empty. You must have installed some other software that put these libraries into place.
IDL is shipped with versions of netcdf and libcurl, but the IDL startup script takes great pains to set up dynamic linking so that those versions appear first in the search path.
I can only speculate that you:
1) are using a DLM which references these libraries explicitly (if so, then you need a new version of the DLM)
2) you tweaked the IDL startup script (if so, then you need to retweak it)
3) you are calling some external program which uses those libraries (if so, then you may need a new version of the program)
You are in library mis-match hell. It sucks. Whatever put those libraries into place needs to be updated. You don't provide enough information to know who the offender is.
Craig M
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
