Sponsored Content
Operating Systems Linux gcc compiled executable not working across x86_64 linux platforms Post 302225416 by same1290 on Friday 15th of August 2008 10:39:20 AM
Old 08-15-2008
Ah, thanks for that feedback.

I guess there's nothing that can be done about that right? no gcc options which create generally compatible instructions (if there is such a thing)?

In any case, thanks for sharing your experience.

Sam
 

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
sdl-config(1)						      General Commands Manual						     sdl-config(1)

NAME
sdl-config - script to get information about the installed version of SDL SYNOPSIS
sdl-config [ --prefix= DIR] [ --exec-prefix= DIR] [ --version ] [ --libs | --library-libs | --plugin-libs ] [ --cflags ] DESCRIPTION
sdl-config is a tool that is used to configure and determine the compiler and linker flags that should be used to compile and link pro- grams, libraries, and plugins that use SDL. It is also used internally by the m4 macros that are included with SDL. OPTIONS
--cflags Print the compiler flags that are necessary to compile a program or library that uses SDL. --exec-prefix=DIR If specified, use DIR instead of the installation exec prefix that SDL was build with when computing the output for the --cflags, --libs, --library-libs, and --plugin-libs options. This option must be specified before any of the --cflags, --libs, --library- libs, and --plugin-libs options. --libs Print the linker flags that are necessary to link a program that uses SDL. --static-libs Print the linker flags that are necessary to statically link a program that uses SDL. --library-libs Print the linker flags that are necessary to link a library that uses SDL. (This excludes any static objects required for linking, since these must be linked only by executable programs.) --plugin-libs Print the linker flags that are necessary to link an SDL-using object that is to be accessed via dlopen(3). This may include static objects with PIC symbol information. This option should not be used for ordinary shared libraries or standalone applications. --prefix=DIR If specified, use PREFIX instead of the installation prefix that SDL was built with when computing the output for the --cflags, --libs, --library-libs, and --plugin-libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any of the --cflags, --libs, --library-libs, and --plugin-libs options. --version Prints the currently installed version of SDL on standard output. EXAMPLES
gcc -o main.o $(sdl-config --cflags) main.c is how you might use sdl-config to compile a C source file for an executable program. gcc -o my_app $(sdl-config --libs) main.o util.o is how you might use sdl-config to link compiled objects into an executable program. gcc -o libSDL_nifty-1.2.so.0.0.1 $(sdl --library-libs) read.o write.o munge.o is how you might use sdl-config to link compiled objects into a shared library. gcc -o libnifty_xmms.so $(sdl --plugin-libs) stream.o blit.o deinterlace.o is how you might use sdl-config to link compiled objects into a plugin for use by another program. AUTHOR
The Simple DirectMedia Layer (SDL) library was written by Sam Lantinga. This manual page was written by Branden Robinson, originally for Progeny Linux Systems, Inc., and the Debian Project. SDL 1.2 2001-12-25 sdl-config(1)
All times are GMT -4. The time now is 05:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy