gcc compiled executable not working across x86_64 linux platforms Post: 302225416

10 More Discussions You Might Find Interesting

1. Programming

dbx error ("Executable contains object file compiled on ...")

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:...

2. Linux

GCC cross compiler for x86_64-elf

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...

3. Linux

GCC cross compiler for x86_64

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...

4. Solaris

Executable compiled on solaris 10 not working on solaris 9

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...

5. Programming

Finding the number of bits a executable was compiled

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.

6. UNIX for Advanced & Expert Users

Viewing a compiled executable file

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...

7. Programming

Using ANSI color codes in gcc compiled program

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. ...

8. Solaris

Newly Compiled GCC 4.4.4 on Solaris sparc gives problem with -m32/-m64 flags

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...

9. Linux

File size limitation in the EST 2012 x86_64 GNU/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. Programming

Local variable in a C function is not getting created in stack when its compiled with GCC

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...

LEARN ABOUT DEBIAN

hardened-cc

HARDENED-CC(1)							 Debian GNU/Linux						    HARDENED-CC(1)

NAME

       hardened-cc - gcc wrapper to enforce hardening toolchain improvements

SYNOPSIS

       export DEB_BUILD_HARDENING=1

       gcc ...

DESCRIPTION

       The  hardened-cc  wrapper  is  normally	used by calling gcc as usual when DEB_BUILD_HARDENING is set to 1. It will configure the necessary
       toolchain hardening features. By default, all features are enabled. If a given feature does not work correctly and needs  to  be  disabled,
       the corresponding environment variables mentioned below can be set to 0.

ENVIRONMENT

       DEB_BUILD_HARDENING=1
	      Enable hardening features.

       DEB_BUILD_HARDENING_DEBUG=1
	      Print the full resulting gcc command line to STDERR before calling gcc.

       DEB_BUILD_HARDENING_STACKPROTECTOR=0
	      Disable stack overflow protection. See README.Debian for details.

       DEB_BUILD_HARDENING_RELRO=0
	      Disable read-only linker sections. See README.Debian for details.

       DEB_BUILD_HARDENING_FORTIFY=0
	      Don't fortify several standard functions. See README.Debian for details.

       DEB_BUILD_HARDENING_PIE=0
	      Don't build position independent executables. See README.Debian for details.

       DEB_BUILD_HARDENING_FORMAT=0
	      Disable unsafe format string usage errors. See README.Debian for details.

NOTES

       System-wide settings can be added to /etc/hardening-wrapper.conf, one per line.

       The  real gcc symlinks are renamed gcc.real, and a diversion is registered with dpkg-divert(1).	Thus hardened-cc's idea of the default gcc
       is dictated by whatever package installed /usr/bin/gcc.

SEE ALSO

       hardened-ld(1) gcc(1)

Debian Project							    2008-01-08							    HARDENED-CC(1)