I was able to run from the command line, but the executable I ran from the command line had those different versions. The older versions.
How do I check the webserver environment libraries? Testing.cgi, which is what gets run from the browser, had different libraries from the working example executable as well as duplicates. On Aug 17, 11:25 am, Jean-Philippe Barette-LaPierre <[email protected]> wrote: > On Mon, Aug 17, 2009 at 11:18 AM, tatebn <[email protected]> wrote: > > > I want to say that we recompiled curlpp to use libssl.so.4 and > > libcurl.so.4 to get rid of those warnings from before. Would > > recompiling libcurlpp to use libcurl.so.3 and libssl.so.0.9.7 do some > > good. Also, the guy who was handling those things quit on me... so > > how would I go about recompiling libcurlpp to use those libraries? > > No, stick to the current libraries. If you managed to run this correctly on > the command line, it alright. So, here's the steps: > > 1. Ensure everything uses the latest libraries (libcurl.so.4 seems > to be alright) > > 2. check the webserver environment, libraries and all. That's most > certainly the problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "curlpp" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/curlpp?hl=en -~----------~----~----~----~------~----~------~--~---
