Sponsored Content
Operating Systems Linux gcc compiled executable not working across x86_64 linux platforms Post 302225187 by fpmurphy on Thursday 14th of August 2008 07:57:48 PM
Old 08-14-2008
Yes, this can happen. Depends on your OS and compiler versions. Generally executing a program on an earlier version of an OS than the version upon which the program was compiled, as is the case with your example, is not formally supported. It may or may not work.
 

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:... (0 Replies)
Discussion started by: Sabari Nath S
0 Replies

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... (5 Replies)
Discussion started by: Mandar123
5 Replies

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... (0 Replies)
Discussion started by: Mandar123
0 Replies

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... (4 Replies)
Discussion started by: ash_bit2k2
4 Replies

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. (1 Reply)
Discussion started by: Leion
1 Replies

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... (2 Replies)
Discussion started by: lost.identity
2 Replies

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. ... (5 Replies)
Discussion started by: kristinu
5 Replies

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... (2 Replies)
Discussion started by: d_shanke
2 Replies

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 Replies)
Discussion started by: siva3492
10 Replies

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... (6 Replies)
Discussion started by: Divya R
6 Replies
HF77(1) 							     LAM TOOLS								   HF77(1)

NAME
hf77, mpif77 - Compile LAM FORTRAN programs. SYNTAX
hf77 [-showme] ... see f77(1) (or whatever your underlying FORTRAN compiler is) for all other options. DESCRIPTION
hf77 is a convenience wrapper for the local native FORTRAN compiler. Translation of a LAM program requires the linkage of the LAM essen- tial services libraries which may not reside in one of the standard search directories of ld(1). hf77 passes its arguments along to the local native FORTRAN compiler along with the -L and -l options required by LAM/MPI programs. This includes all necessary options for ROMIO and/or C++ bindings support (if ROMIO/C++ support was included when LAM was compiled). mpif77 is now the same as hf77. See the NOTES section, below. By default, hf77 uses the FORTRAN compiler that was selected when LAM was configured (with the --with-fc flag to ./configure) as the local native FORTRAN compiler, but this can be overridden by the LAMHF77 environment variable. OPTIONS
-showme Does not invoke the underlying FORTRAN compiler. Instead, it shows the command line that would be executed to compile the FORTRAN program. NOTES
Previous versions of hf77 did not automatically link in the MPI library. Starting with LAM version 6.3, since hf77 has become the de facto LAM FORTRAN compiler, the -lmpi option is now automatically passed to the underlying compiler when linking LAM/MPI programs. Previous versions of LAM included the mpif77 wrapper script to automatically pass -lmpi to hf77. This script is now obsolete since hf77 now includes -lmpi automatically. mpif77 is now a symbolic link to hf77 to ensure backward compatibility. SEE ALSO
f77(1), ld(1), lam-helpfile(1) LAM 6.5.8 November, 2002 HF77(1)
All times are GMT -4. The time now is 08:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy