Opened 13 years ago

Closed 8 years ago

#3111 closed defect (invalid)

GDAL Curl Linking issue

Reported by: cbranch Owned by: warmerdam
Priority: normal Milestone:
Component: ConfigBuild Version: 1.6.1
Severity: normal Keywords: Curl Linking
Cc:

Description

System: Linux Red Hat Enterprise 5 Compiler: gcc 4.1.2

Situation: System has Curl 3 installed in usr/lib. I want to build GDAL with Curl 4 libraries. Attempt: Run configure with --with-curl pointing at a local build of Curl 4. Configure successfully finds and indicates it is using the local Curl.

Problem the resulting link line looks like this: -L/usr/lib .... -L/local/libcurl/lib -lcurl Because there is a libcurl.so.3 in usr lib gdal is linked with that version rather than the curl I specified. I believe this is because of the order of the LIB library in GDALmake.opt file. It looks like CURL (and possibly the other dependency libraries) should be placed before the expanded LIBS location to allow for external locations.

My work around was to move KAK DWG and CURL before the /usr/lib argument in the opt file.

Desired solution would be that gdal would use the specified third party library location over the any installed version.

Change History (3)

comment:1 by warmerdam, 13 years ago

Component: defaultConfigBuild

As far as I can tell this is a generic problem the construction of library paths on unix. It is very hard for configure to know how to construct the libpath in a way that gives the libraries we want. Generally, I advise people to manually rearrange things based on fuller knowledge - as you have done.

I'm not sure what we could change that isn't going to just move the breakage to another library which now has lower precidence.

comment:2 by Jukka Rahkonen, 8 years ago

Is this a GDAL bug at all?

comment:3 by Jukka Rahkonen, 8 years ago

Resolution: invalid
Status: newclosed

People must be building GDAL with curl on many different platforms with success. Closing.

Note: See TracTickets for help on using tickets.