Thanks Roderich for all your help.  I was able to use the readelf command to 
find all the shared libraries I needed to copy over to the target machine.  I 
now have a working application on my target box.  Cool stuff!

However, I have a new problem.  The build box was SCO 5.0.7 and the 1st target 
box was SCO 5.0.7.  I par-packed my application and grabbed all the needed 
shared libraries and put them on the SCO 5.0.7 target box and everything worked 
great.  Next I put together a SCO 5.0.6 target box.  I copied over my 
par-packed application along with the shared libraries.  But when I execute the 
par-packed "bridge" application (./bridge) I'm getting the following error:

Floating exception - core dumped

So my deployment package to the 1st target box works but the 2nd target (SCO 
5.0.6) does not.  I'll keep playing around with it to try to get it working but 
I'm pretty bummed it didn't work out of the gate.

Thanks again for your help.


-Mike



-----Original Message-----
From: Roderich Schupp [mailto:[email protected]] 
Sent: Tuesday, February 15, 2011 1:57 AM
To: Michael Miller
Cc: [email protected]
Subject: Re: Trouble putting together a stand alone

On Mon, Feb 14, 2011 at 10:24 PM, Roderich Schupp 
<[email protected]> wrote:
> Sorry, there's nothing I can do on the PAR::Packer side. If you know 
> the right incantation to stop gcc hardwiring library references, patch 
> the above line in myldr/Makefile and let me know.

Another idea: if you also have the static library .../libperl.a corresponding 
to your shared /usr/lib/perl5/5.8/i586-pc-sco3.2v5.0/CORE/libperl.so then you 
could tweak the statement to link with the static library. Replacing 
"-L/usr/lib/perl5/5.8/i586-pc-sco3.2v5.0/CORE -lperl" with 
"/usr/lib/perl5/5.8/i586-pc-sco3.2v5.0/CORE/libperl.a" should probably do the 
trick.

Cheers, Roderich

#####################################################################################
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
#####################################################################################

Reply via email to