Page 1 of 1
compiled c differences across puppy and fedora
Posted: Tue 20 Dec 2005, 14:50
by guest
Hi
I've got a miniterm type c program which I'm trying to run on puppy which I developed on fedora install. The code compiles using gcc on both platforms fine but runs differently. can I simply copy the libs over from fedora or something ..
please help.
Regards
Mulgy
Posted: Tue 20 Dec 2005, 16:09
by MU
I don't know if thecurrent fedora is binary-compatible.
If the program compileson puppy, butdoes not work - what forerrors do you get?
Some shell-commands might be incompatible, as Puppy uses busybox, that replaces some commands with other versions.
You could try to copy libs from fedora- or use them from Debian.
Tips for Debian-binaries:
http://www.murga.org/~puppy/viewtopic.p ... ight=undeb
http://www.murga.org/~puppy/viewtopic.p ... ight=undeb
Mark
Re: compiled c differences across puppy and fedora
Posted: Tue 20 Dec 2005, 17:23
by rarsa
guest wrote:The code compiles using gcc on both platforms fine but runs differently
What do you mean 'differently'? How do both binary differ?
Posted: Thu 22 Dec 2005, 15:55
by Mulgy
The miniterm I've written/amended monitors input from a serial device which accepts hex based commands. For some reason now I run on puppy the commands I was getting in, which were ascii numbers but are actually being sent as hex numbers are being displayed as -1073743086 is this a conversions problem which I can code around or am I seeing the memory address of the value hex3 or something else.. I'm lost.
cheers