Hi, I have finally was able to solve this problem using a workaround. The problem was that on my RH4 machines the .so files were link to .so.0 files... So, when the par was opened and ran it looked for .so files while the files in the /tmp/par tmp dir had .so.0 extenssion.
The solution for that was creating my own lib directory and copy there all the library (.so file) I needed (with .so extenssion) Then, I ran pp (not wxpar...) with -l <path to lib> switch for all the library files I stored in my own lib directory. That workaround solve the problem for me. Thanks. Erez On Thu, Nov 12, 2009 at 11:21 AM, Steffen Mueller <nj88ud...@sneakemail.com>wrote: > Hi David, > > > Erez David wrote: > >> I am trying to create an executable using wxpar which will work on both >> Linux RH4 and Linux RH5.. For this purpese I am using Linux RH4 32bit. >> > > Unfortunately, there's long been an issue with running PAR::Packer > generated binaries from RH4 on RH5. It's a recurring one that's regularly > raised on par@perl.org (including a recent post by yourself). It's also an > issue that *seems* to be isolated to RedHat Linuxes. I've never used RedHat > and do not plan to do so. Therefore, I can't debug it. Nobody else has > managed to do so. Your specific issue may or may not be the same as the > historic one since it's using tons of "external" Wx shared libraries. > > I'm sorry to be of so little help. I hope somebody else can fill the gap. > Maybe Mark Dootson, the author of wxpar, has something to contribute to > this? > > Best regards, > Steffen >
