Yes, unfortunately I have come to the conclusion that I will have to static link the new library to prove the case, so that I can get the new library brought in to my companies software tree.
I've been doing my hardest to upgrade all our code to eradicate static linked libraries but it seems to be a case of the old adage of one step forwards and 2 steps backwards, lol. Thank you to those of you that offered helpful advice :) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dirk Manske Sent: 07 February 2011 19:25 To: libcurl development Subject: Re: Problems migrating from curl-7.10.6-9 to curl-7.15.5-2 > Unfortunately, changing to a newer version of libcurl is not so simple in my environment. At least for testing you could install a newer version into your home directory with s.t like that. ./configure --prefix=$HOME/curl && make install And than link you program to that version. If it works and you could not update curl on the production server you could link your program with libcurl statically. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
