binary incompatibility problem?

[patrick <patrick at mail dot boxsoft dot com>]

Hi all,

I'm confused here.  I just finished building and installing egcs-1.1.2
and binutils 2.9.1.0.19a on my home machine:

   mybox> uname -a
   Linux 3eye 2.0.35 #1 Sun Aug 23 18:46:06 PDT 1998 i686 unknown

   mybox> gcc -v
   Reading specs from /usr/lib/gcc-lib/i486-linux/2.7.2.2/specs
   gcc version 2.7.2.2

   mybox> ld -v
   GNU ld version 2.9.1 (with BFD 2.9.1.0.19)


I compiled the following source:

// -- cut here --

#include <iostream>


int main( int, char** )
{
   std::cout << "TESTING\n";
   return 0;
}

// -- cut here --

Simple, no brainer code.  I compile it on my machine, ftp the executable
over to my isp's box:

   isp> uname -a
   Linux ktb2 2.0.36 #44 Mon Dec 7 11:02:15 PST 1998 i586 unknown

   isp> gcc -v
   Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
   gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release)

   isp> ld -v
   GNU ld version 2.9.1 (with BFD 2.9.1.0.22)

and when i run the executable it produces a "Segmentation fault"!
No core since they dis-allow changing the ulimit -c on my shell,
and they don't have gdb installed or at least don't have it chmod
for execute.


What might be the problem here?  I notice that their binutils are
slightly newer but I hardly think that might be the problem.
If you say it might be it, I don't mind getting that version if
someone could point me to the source.  The latest I could find
on sunsite was 2.9.1.0.19a.


I am open to suggestions.  The main reason I upgraded to egcs-1.1.2
is my isp didn't have libg++ installed on their box and i need to
run my C++-cgi scripts ... and I rather not put my source on their
box (among other reasons are disk-space limitations).

Thanks in advance,


patrick@boxsoft.com