Greetings, I have some users suddenly complaining that on recent Debian Distributions (Squeeze and Sid in particular), my par-packed binary is dying, seemingly because it's picking up a library outside of the PAR cache tree. I can't work out why it's doing this - seems fine on earlier linux distributions. If the users delete/rename the system library, the PAR cache version is found and it's all ok which makes it look as if the library search path is wrong somehow, looking outside of the PAR cache first?
PK -- Dr Philip Kime
