From: <bu...@gm...> - 2006-03-03 20:12:19
|
Dnia 03-03-2006, pią o godzinie 14:49 -0500, Norm Dressler napisał(a): > More info -- > > It looks like the problem might be linked to the version of libsoup > being found. I had similar issues compiling other programs with some non-packaged libraries involved (although configured with proper prefixes). Look for all instances of libsoup (like all .pc files, all links to libraries) - maybe there is something left from older versions? That is why - if I am not sure - I always compile external/patched libraries to some local (meaning /home) prefixes and use PKG_CONFIG_PATH or other variables. When I want to try a new version, I just delete the whole folder. I hope this helps, otherwise I have no ideas (just to make sure I compiled today's svn libsyncml and had no problems). Just an example: $ pkg-config --modversion libsoup-2.2 $ 2.2.6.1 $ PKG_CONFIG_PATH=/home/burlap/sync/alternative/lib/pkgconfig pkg-config --modversion libsoup-2.2 $ 2.2.90 Cheers, Rafał |