08-14-2008
gcc compiled executable not working across x86_64 linux platforms
Hi
I compiled a hello world program on two different 64-bit Linux machines, named quimby and node0331. When I compile on quimby and run on node0331 I get a "Floating exception (core dumped)" error. But if I do it in reverse, things work fine.
Here's my compilation on quimby:
$ uname -a
Linux quimby 2.6.18-8.1.15.el5 #1 SMP Mon Oct 22 08:32:28 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
$ cat hello.c
#include <stdio.h>
int main()
{
printf("Hello World\n");
return 0;
}
$ gcc -c hello.c -o hello.o ;
$ gcc -o hello hello.o
$ ./hello
Hello World
The I go to node0331 and run there:
$ uname -a
Linux node0331 2.6.9-42.0.3.ELsmp #1 SMP Fri Oct 6 06:28:26 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux
$ ./hello
Floating exception (core dumped)
But again if I do this in reverse, things work fine. Has anyone ever experienced this problem.
Thanks in advance,
Sam
10 More Discussions You Might Find Interesting
1. Programming
Hi,
We are trying to run dbx on a core file for which we have the original executable and libs, but not the source / object tree. We have recompiled the objects from the original source, but dbx complains that they were compiled at a different time, and refuses to read them:
Object file:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies
2. Linux
Hi,
I am building GCC cross compiler for x86_64-elf
for that a have followed steps,
1. mkdir build-gmp build-mpfr
2. cd build-gmp
3. ../gmp-4.2/configure --prefix=/usr/local
4. make all install
5. make check
6.cd ../build-mpfr
7. ../mpfr-2.3.2/configure... (5 Replies)
Discussion started by: Mandar123
5 Replies
3. Linux
Hi,
I am tried to install GCC cross compiler for 64-bit machine.
i want compile one application for 64 bit machine.
I have followed steps form GCC Cross-Compile - OSDev Wiki .
Please if anybody have installed cross compiler successfully, please tell me the steps followed by you.
Thanking... (0 Replies)
Discussion started by: Mandar123
0 Replies
4. Solaris
Hi
I compiled an executable on Solaris 10 which creates semaphore ( semget)
but it didn't work on solaris 9 , while it is executing sucessfully on solaris 10. It is throwing the system error that Invalid arguments ( system error 22) on solaris 9.
the ldd for the executable on two servers is as... (4 Replies)
Discussion started by: ash_bit2k2
4 Replies
5. Programming
Hi,
Can anyone tell me how to find out how many bits a c executable was compiled in?
I am trying to do some investigation of running 32bit programs in 64bit systems. (1 Reply)
Discussion started by: Leion
1 Replies
6. UNIX for Advanced & Expert Users
I've got a executable binary file (source code fortran77, compiled using gfortran).
I'm not sure this is even possible but I remember someone I knew was able to view the source code that created this binary file, i.e. he used a program that enabled him to see what the source code was.
Is this... (2 Replies)
Discussion started by: lost.identity
2 Replies
7. Programming
I have put some yellow color codes and works well.
I call the funstion using
print_usage(stderr, 0);
I would like to know if there is any way, to store the ansi color codes in variables and then call them inside fprintf.
Or have a format followed by the strings I want to output.
... (5 Replies)
Discussion started by: kristinu
5 Replies
8. Solaris
Hello experts,
This issue has kept me busy all day long. It started off with openssl compilation which was giving linking error with following message:
/usr/local/bin/ld: target elf32-sparc not found
collect2: ld returned 1 exit status
I tried every step possible thing that I could think... (2 Replies)
Discussion started by: d_shanke
2 Replies
9. Linux
Hello Friends,
I tried to take tar backup in my server, but it ended with an error.
It said that:
/home/back/pallava_backup/fbackup_backup/stape_config
/home/back/romam_new.tar.gz
tar: /home/backup/back.tar.gz: Cannot write: No space left on device
tar: Error is not recoverable: exiting... (10 Replies)
Discussion started by: siva3492
10 Replies
10. Programming
Hi,
I am working in UEFI EDK2 Bios source. We created a platform related new package in the EDK2 source. I find a strange issue with the platform related code we added.
When I did source level debugging I noticed the
local variable in a C function is not getting created in stack when its... (6 Replies)
Discussion started by: Divya R
6 Replies
LEARN ABOUT DEBIAN
pdebuild-user-mode-linux
pdebuild-user-mode-linux(1) pbuilder pdebuild-user-mode-linux(1)
NAME
pdebuild-user-mode-linux - pbuilder-user-mode-linux way of doing debuild
SYNOPSIS
pdebuild-user-mode-linux [pdebuild-user-mode-linux options] -- [pbuilder-user-mode-linux options]
DESCRIPTION
A convenience program for pbuilder-user-mode-linux which invokes pbuilder after obtaining appropriate root privilege in a Debian source
directory. One must be inside the source tree containing the debian directory, in order to make it work.
PDEBUILD OPTIONS
--buildsourceroot [fakeroot]
The command used to gain root privilege for invoking dpkg-buildpackage
--auto-debsign
Invoke debsign at the end of pdebuild process.
--debsign-k [key-id]
Pass -k option to debsign to specify which keyid to sign.
--buildresult [Directory for build results]
The place which build result is stored.
--configfile [Extra config file to use]
The configuration file is used, but not passed on to pbuilder-user-mode-linux.
--debbuildopts [options to pass to dpkg-buildpackage]
The space-delimited list of options are passed to dpkg-buildpackage. This option appends to pbuilder option --debbuildopts and may
also be used to reset the list of options by passing the empty string.
--use-pdebuild-internal
Uses a different implementation of pdebuild, which calls clean and build inside the chroot, using bind-mounts.
pdebuild-internal tries to run debian/rules clean inside the chroot. To achieve the goal, the working directory is passed on inside
the chroot, in the form of bind-mounting and debuild is run.
This option will not protect the working directory and its parent directories from the build scripts.
-- [pbuilder options]
After the -- symbol, an arbitrary number of pbuilder options can be specified. See pbuilder-user-mode-linux.1 for full list of
options.
There is an exception that --buildresult needs to be specified as pdebuild option before the -- to be effective.
FILES
/etc/pbuilderrc
The configuration file for pbuilder-user-mode-linux, used in pdebuild-user-mode-linux.
/usr/share/pbuilder/pbuilderrc
The default configuration file for pbuilder-user-mode-linux, used in pdebuild-user-mode-linux.
${HOME}/.pbuilderrc
Configuration file for pbuilder-user-mode-linux, used in pdebuild-user-mode-linux, overrides what is written in /etc/pbuilderrc
AUTHOR
Initial coding, and main maintenance is done by Junichi Uekawa <dancer@debian.org>.
The homepage is available at http://pbuilder.alioth.debian.org
SEE ALSO
/usr/share/doc/pbuilder/pbuilder-doc.html, pbuilder-user-mode-linux(1), pbuilderrc(5), pbuilder-uml.conf(5)
Debian 2006 May 24 pdebuild-user-mode-linux(1)