01-12-2009
I have gcc 4.1.1 installed. Maybe you have an older version. If so, this might not apply to you.
I am not familiar with the options you mentioned, but the v9 is definitely SPARC architecture specific. Using "-m64" will produce code for the 64-bit platform, which would be the default anyway. ints will be 32 bits, and pointers and longs will be 64-bits. You could use -mabi=32 will generate 32-bit code for your 64-bit platform. This might result in an inability to link against 64-bit libraries, but if you have 32-bit libraries also installed, it should work. You can do something similar with "-mlong32", which forces all longs and pointer types to 32 bits (but still uses the 64-bit abi so it could run on a 64 bit platform). It might be possible to combine -mlong-calls with this to ensure proper behavior with the linker, but that's just a WAG (wild ass guess).
I thought there was a way to tell the compiler to treat an "int" as 64-bits, but I cannot find an option for that in the manual. You can always use the preprocessor to try to change "int" into "long", but that might not work in some instances.
I found some links that might help:
http://gcc.fyxm.net/summit/2003/Port...2064%20bit.pdf
This link specifically says you must use gcc 4 and later, and mentions a few options pertinent to your task.
64-Bit Transition Guide: Compiling 64-Bit Code Using GCC
9 More Discussions You Might Find Interesting
1. AIX
Hi all,
I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue
thanks in advance
vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies
2. UNIX for Dummies Questions & Answers
Alright. As the title states, I'm working with a UNIX based web server(Sun Fire v120). The problem I'm currently having is trying to properly configure it for hosting. If anyone could help me out, it would be great.
Much thanks.
-XTIZ3 (2 Replies)
Discussion started by: XTIZ3
2 Replies
3. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
4. Red Hat
I am just trying to get the warning while compiling for 64-bit on Linux
>>
uname -a
Linux mms4.es.cpth.ie 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:00:54 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux
===================================
Written test.c file which conatin :
#include<stdio.h>... (1 Reply)
Discussion started by: amit_27
1 Replies
5. HP-UX
Dear All,
I am new on Tru 64 bit Unix platform. I have a database server "HP AlphaServer ES45" version p5.1 of Tru Ux 64 bit installed. I have 4 hard drives in this system (1,2,3,4). My 4th hard drive is damaged which contain Oracle database files including partitions on 4th drives... (2 Replies)
Discussion started by: hellozishan
2 Replies
6. HP-UX
Hello All,
I have HP Openview storage data protector version 5.5. When I am going to write my backup I have an error message saying "Connot Open Device /dev/rmt/0mn"
Follownig is my output:
# ls -l /dev/rmt/0mn
crw-rw-rw- 2 bin bin 205 0x080140 Jan 17 16:41 /dev/rmt/0mn
# uname -a... (2 Replies)
Discussion started by: hellozishan
2 Replies
7. HP-UX
i am trying to build on hpux-itanium 64 bit platform. my application needs to link to 64 bit version of the library libCsup.so
This library is present in /usr/lib/hpux64/libCsup.so
I am specifying the location of this library as linker flags
LDFLAGS := -Wl,-N -Wl,+s... (0 Replies)
Discussion started by: skyineyes
0 Replies
8. Red Hat
Hi,
I installed Db2 9.7 on RHEL5 32bit .
Instance Name is db2inst1 amd in that i created database as mydb.
I exported env variables for
classpath ,db2dir,db2instance
LD_LIBRARY_PATH ,PATH ,ODBC, ODBCHOME ,ODBCINI
My application needs ODBC connectivity and so I modified odbc.ini file . ... (0 Replies)
Discussion started by: roopalidalvi231
0 Replies
9. Solaris
Hello,
I am fairly new to Solaris so please be gentle ;). I am trying to install apache 2.4.3 adapting a script one of my colleagues wrote for version 2.2.23. The problem lies in the fact that I am aiming at creating a 64bit package hence I've already amended the script to reflect that. I... (3 Replies)
Discussion started by: teotao
3 Replies
LEARN ABOUT DEBIAN
sdl-config
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)