Source: http://compgroups.net/comp.os.linux.misc/compiling-on-32-bit-vs-64-bit-gcc-fails-on/360247
Timestamp: 2019-04-23 10:31:53+00:00

Document:
Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
Is there an Assembler issue re 64-bit v. 32-bit?
> Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
> Is there an Assembler issue re 64-bit v. 32-bit?
heller has logged on pts/2 from :0.0 at 24-Mar-2010 11:08.
So....  why does my g++ have a Target/host *not* as x86_64?
And is that the problem?
And if so, how to proceed?
> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
> > Is there an Assembler issue re 64-bit v. 32-bit?
> So....  why does my g++ have a Target/host *not* as x86_64?
> And is that the problem?
> And if so, how to proceed?
uninstall the 32-bit compiler(s) and install the 64-bit ones.
> > > Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
> > > Is there an Assembler issue re 64-bit v. 32-bit?
> > development files installed.
"uname -a"  and "cat /etc/issue" give you?
>> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
>> > Is there an Assembler issue re 64-bit v. 32-bit?
>> and development files installed.
I had initially installed 32-bit Scientific Linux 5.4 on this machine.
(partitions, file systems, etc. remain).
and suspect I'll be fine.
> > So.... =A0why does my g++ have a Target/host *not* as x86_64?
> > And is that the problem?
> > And if so, how to proceed?
> "uname -a" =A0and "cat /etc/issue" give you?
> >> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
> >> > Is there an Assembler issue re 64-bit v. 32-bit?
> >> and development files installed.
> I think I know what the problem is.
> I had initially installed 32-bit Scientific Linux 5.4 on this machine.
> (partitions, file systems, etc. remain).
> by the 64-bit version.
> and suspect I'll be fine.
> Thanks for all the assistance.
>> > So....  why does my g++ have a Target/host *not* as x86_64?
>> > And is that the problem?
>> > And if so, how to proceed?
>> do "uname -a"  and "cat /etc/issue" give you?
>> >> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4.
>> >> > Is there an Assembler issue re 64-bit v. 32-bit?
>> >> and development files installed.
> > I think I know what the problem is.
> > I had initially installed 32-bit Scientific Linux 5.4 on this machine.
> > (partitions, file systems, etc. remain).
> > by the 64-bit version.
> > and suspect I'll be fine.

References: v. 
 v. 
 v. 
 v. 
 v. 
 v. 
 v.