compiling on 32-bit vs. 64-bit (gcc fails on 64-bit)
in [General Linux]
|
Prev: 20 Most Powerful Open Source Voices of 2010. So where is RoySchestowitz? Hahahahhaha
Next: NYC LOCAL: Thursday 25 March 2010 ISOC-NY: Jinyang Li on Censorship Circumvention via Kaleidoscope
From: Darrell Stec on 24 Mar 2010 12:56 Richard Vaughn wrote: > On Robert Heller's 64-bit centOS machine (above): > "g++ -v" provides: > Target: x86_64-redhat-linux > host=x86_64-redhat-linux > > On my 64-bit ScientificLinux machine: > "g++ -v" provides: > Target: i386-redhat-linux > host=i386-redhat-linux > > gcc versions are identical (gcc version 4.1.2 20080704 (Red Hat > 4.1.2-46) ). > > Outputs of "rpm -q binutils", "ld -v" and "as -v" commands are also > identical. > > So.... why does my g++ have a Target/host *not* as x86_64? > And is that the problem? > And if so, how to proceed? > > Thanks, > -Richard > Are you sure you have the 64-bit version of the software installed? What do "uname -a" and "cat /etc/issue" give you? > On Mar 24, 11:45 am, Darrell Stec <dars...(a)neo.rr.com> wrote: >> Richard Vaughn wrote: >> > On a 64-bit Scientific Linux 5.4 machine, I get the following >> > when I try to compile the basic "Hello world" program: >> >> > [root]# g++ -Wall hello.cc -o hello >> > /tmp/ccglIDXK.s: Assembler messages: >> > /tmp/ccglIDXK.s:10: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:38: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:55: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:79: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:81: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:85: Error: suffix or operands invalid for `push' >> > /tmp/ccglIDXK.s:94: Error: suffix or operands invalid for `pop' >> > /tmp/ccglIDXK.s:95: Error: suffix or operands invalid for `pop' >> >> > Contents of hello.cc: >> > #include <iostream> >> >> > int >> > main () >> > { >> > std::cout << "Hello, world!\n"; >> > return 0; >> > } >> >> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4. >> >> > Is there an Assembler issue re 64-bit v. 32-bit? >> >> > Thanks, >> > -Richard Vaughn >> >> The difference could be whether or not you have all the header, source >> and development files installed. >> >> -- >> Later, >> Darrell -- Later, Darrell
From: Richard Vaughn on 24 Mar 2010 15:58 I think I know what the problem is. I had initially installed 32-bit Scientific Linux 5.4 on this machine. Then I installed the 64-bit version; upgrade, not full re-install (partitions, file systems, etc. remain). Apparently in so doing, not all 32-bit software is over-written by the 64-bit version. So now I'll install the 64-bit version from the ground up and suspect I'll be fine. Thanks for all the assistance. -Richard Vaughn On Mar 24, 12:56 pm, Darrell Stec <dars...(a)neo.rr.com> wrote: > Richard Vaughn wrote: > > On Robert Heller's 64-bit centOS machine (above): > > "g++ -v" provides: > > Target: x86_64-redhat-linux > > host=x86_64-redhat-linux > > > On my 64-bit ScientificLinux machine: > > "g++ -v" provides: > > Target: i386-redhat-linux > > host=i386-redhat-linux > > > gcc versions are identical (gcc version 4.1.2 20080704 (Red Hat > > 4.1.2-46) ). > > > Outputs of "rpm -q binutils", "ld -v" and "as -v" commands are also > > identical. > > > So.... why does my g++ have a Target/host *not* as x86_64? > > And is that the problem? > > And if so, how to proceed? > > > Thanks, > > -Richard > > Are you sure you have the 64-bit version of the software installed? What do > "uname -a" and "cat /etc/issue" give you? > > > > > On Mar 24, 11:45 am, Darrell Stec <dars...(a)neo.rr.com> wrote: > >> Richard Vaughn wrote: > >> > On a 64-bit Scientific Linux 5.4 machine, I get the following > >> > when I try to compile the basic "Hello world" program: > > >> > [root]# g++ -Wall hello.cc -o hello > >> > /tmp/ccglIDXK.s: Assembler messages: > >> > /tmp/ccglIDXK.s:10: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:38: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:55: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:79: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:81: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:85: Error: suffix or operands invalid for `push' > >> > /tmp/ccglIDXK.s:94: Error: suffix or operands invalid for `pop' > >> > /tmp/ccglIDXK.s:95: Error: suffix or operands invalid for `pop' > > >> > Contents of hello.cc: > >> > #include <iostream> > > >> > int > >> > main () > >> > { > >> > std::cout << "Hello, world!\n"; > >> > return 0; > >> > } > > >> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4. > > >> > Is there an Assembler issue re 64-bit v. 32-bit? > > >> > Thanks, > >> > -Richard Vaughn > > >> The difference could be whether or not you have all the header, source > >> and development files installed. > > >> -- > >> Later, > >> Darrell > > -- > Later, > Darrell
From: Robert Heller on 24 Mar 2010 18:17 At Wed, 24 Mar 2010 12:58:46 -0700 (PDT) Richard Vaughn <rvaughn9(a)gmail.com> wrote: > > I think I know what the problem is. > > I had initially installed 32-bit Scientific Linux 5.4 on this machine. > Then I installed the 64-bit version; upgrade, not full re-install > (partitions, file systems, etc. remain). > > Apparently in so doing, not all 32-bit software is over-written > by the 64-bit version. > > So now I'll install the 64-bit version from the ground up > and suspect I'll be fine. Yep. 'Upgrading' from 32-bit to 64-bit is NOT a recomended procedure... -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
From: Darrell Stec on 24 Mar 2010 18:18 Richard Vaughn wrote: > I think I know what the problem is. > > I had initially installed 32-bit Scientific Linux 5.4 on this machine. > Then I installed the 64-bit version; upgrade, not full re-install > (partitions, file systems, etc. remain). > > Apparently in so doing, not all 32-bit software is over-written > by the 64-bit version. > > So now I'll install the 64-bit version from the ground up > and suspect I'll be fine. > > Thanks for all the assistance. > > -Richard Vaughn > Good luck. > On Mar 24, 12:56 pm, Darrell Stec <dars...(a)neo.rr.com> wrote: >> Richard Vaughn wrote: >> > On Robert Heller's 64-bit centOS machine (above): >> > "g++ -v" provides: >> > Target: x86_64-redhat-linux >> > host=x86_64-redhat-linux >> >> > On my 64-bit ScientificLinux machine: >> > "g++ -v" provides: >> > Target: i386-redhat-linux >> > host=i386-redhat-linux >> >> > gcc versions are identical (gcc version 4.1.2 20080704 (Red Hat >> > 4.1.2-46) ). >> >> > Outputs of "rpm -q binutils", "ld -v" and "as -v" commands are also >> > identical. >> >> > So.... why does my g++ have a Target/host *not* as x86_64? >> > And is that the problem? >> > And if so, how to proceed? >> >> > Thanks, >> > -Richard >> >> Are you sure you have the 64-bit version of the software installed? What >> do "uname -a" and "cat /etc/issue" give you? >> >> >> >> > On Mar 24, 11:45 am, Darrell Stec <dars...(a)neo.rr.com> wrote: >> >> Richard Vaughn wrote: >> >> > On a 64-bit Scientific Linux 5.4 machine, I get the following >> >> > when I try to compile the basic "Hello world" program: >> >> >> > [root]# g++ -Wall hello.cc -o hello >> >> > /tmp/ccglIDXK.s: Assembler messages: >> >> > /tmp/ccglIDXK.s:10: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:38: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:55: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:79: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:81: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:85: Error: suffix or operands invalid for `push' >> >> > /tmp/ccglIDXK.s:94: Error: suffix or operands invalid for `pop' >> >> > /tmp/ccglIDXK.s:95: Error: suffix or operands invalid for `pop' >> >> >> > Contents of hello.cc: >> >> > #include <iostream> >> >> >> > int >> >> > main () >> >> > { >> >> > std::cout << "Hello, world!\n"; >> >> > return 0; >> >> > } >> >> >> > Same program compiles/runs fine on 32-bit Scientific Linux 5.4. >> >> >> > Is there an Assembler issue re 64-bit v. 32-bit? >> >> >> > Thanks, >> >> > -Richard Vaughn >> >> >> The difference could be whether or not you have all the header, source >> >> and development files installed. >> >> >> -- >> >> Later, >> >> Darrell >> >> -- >> Later, >> Darrell -- Later, Darrell
From: Nico Kadel-Garcia on 25 Mar 2010 07:49
On Mar 24, 6:17 pm, Robert Heller <hel...(a)deepsoft.com> wrote: > At Wed, 24 Mar 2010 12:58:46 -0700 (PDT) Richard Vaughn <rvaug...(a)gmail.com> wrote: > > > > > I think I know what the problem is. > > > I had initially installed 32-bit Scientific Linux 5.4 on this machine. > > Then I installed the 64-bit version; upgrade, not full re-install > > (partitions, file systems, etc. remain). > > > Apparently in so doing, not all 32-bit software is over-written > > by the 64-bit version. > > > So now I'll install the 64-bit version from the ground up > > and suspect I'll be fine. > > Yep. 'Upgrading' from 32-bit to 64-bit is NOT a recomended procedure.... *Ouch*. did that once by accident. I'd suggest backing it up, wiping the disks and starting over. If not, Then install the 64-bit version somewhere, git the list of all the standard RPM's, and use yum and rpm to reinstall *everything*, including both i386 and x86_64 versions of things, and discard the i386 versions lying around. But it would be much faster to re-install. |