Sponsored Content
Full Discussion: 64-Bit gcc Compilation
Top Forums Programming 64-Bit gcc Compilation Post 302212696 by Sivaswami on Tuesday 8th of July 2008 06:27:42 AM
Old 07-08-2008
How to dynamically modify the Library path in that case ?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

64 bit file using gcc

Hi, I am compiling a C program using gcc. gcc -c test.c The OS is Solaris 2.8 (64 bit). We dont have cc compiler on the box. When I do a file test.o , I get this: test.o: ELF 32-bit MSB relocatable SPARC Version 1 In one of my scripts I need a 64 bit object file. Is it... (1 Reply)
Discussion started by: nattynatty
1 Replies

2. Programming

32-bit code with gcc

I want to create a 32 bit shared library. I am using following commands 1. gcc -c test1.c 2. ld -b test1.o -o test1.sl But this creates 64 bit shared library. Unix version of the server on which I am working is HP-UX 11.11 (1 Reply)
Discussion started by: amol.chavan
1 Replies

3. Programming

gcc compilation

how can i do static compilation in gcc my gcc version is # gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/u sr/share/info --enable-shared --enable-threads=posix --disable-checking... (3 Replies)
Discussion started by: collins
3 Replies

4. Programming

compilation error in gcc

Hi, Should be too simple... I wrote a sample c++ program like #include <iostream.h> int main() {$ int ab=455; cout << ab << endl; return 1; } I am getting error like $ gcc u1.cpp Undefined first referenced ... (9 Replies)
Discussion started by: ls1429
9 Replies

5. Solaris

Compilation on SunOs5.7 using gcc 3.3.5

I have the following declaration in file named vx_solaris.h (Path : /usr/share/src/tpkgs/veritas/solaris_sparc/include/sys/fs/vx_solaris.h) typedef (*vx_creatfptr_t)(struct vnode *, char *, struct vattr *, vcexcl_t, int, struct vnode **, vx_cred_t *, int); I include vx_solaris.h in one of... (5 Replies)
Discussion started by: amitc
5 Replies

6. Solaris

Installing gcc - recieve error message gcc : cannot execute

AIM- Install Oracle 11g on Solaris using VMWare Steps 1.Logged on as root 2.Created subfolders à /usr/local/bin & /usr/local/bin/gcc 3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD 4.Copied files from CD to /usr/local/bin/gcc 5.Terminal (root) à pkgadd -d... (8 Replies)
Discussion started by: Ackers
8 Replies

7. Solaris

Solaris 10 and 64 bit apache/openssl/gcc

I installed Solaris 10 on a v440. I installed v3.4.6 gcc from Sun Freeware. I was considering installing 64 bit Apache/Openssl and wondered if people encountered any problems with it. What config parameters did you have to compile openssl and apache? Thank you (3 Replies)
Discussion started by: csross
3 Replies

8. Programming

Header file compilation using gcc in Sparc Solaris

I am facing problem while migrating the c++ code from Linux to Solaris. In linux the code is absolutly compiled fine with GCC compiler but when i am using the same in Solaris it coomplains bash-3.1$ gcc LibSip.h gcc: Compilation of header file requested The same command is working fine in... (2 Replies)
Discussion started by: mrupesh74
2 Replies

9. AIX

Gcc compilation problem on AIX 6.1

Hi, I have to compile a program on my server, runs on AIX 6.1. On my test server the compilation is ok (AIX 6.1); but when I try it on production server, I have this gcc prog.c -o prog_out In file included from resmon.c:111: /usr/include/unistd.h:924: error: expected ')' before ' I noticed... (1 Reply)
Discussion started by: tnjulius
1 Replies
FORT77(1)						     Linux Programmer's Manual							 FORT77(1)

NAME
fort77 - invoke f2c Fortran translator transparently, like a compiler SYNOPSIS
fort77 [-c] [-g] [-v] [-k] [-P] [-cpp] [f2c option ...] [-L directory ...] [gcc-option ...] [link option ...] [-O optlevel] [-o out- file] [-s] [-w] [-Wx,arg1[,arg2]...] file ... DESCRIPTION
The fort77 script invokes the f2c command transparently, so it can be used like a real Fortran compiler. It can be used to compile For- tran, C and assembler code, and to link it with the f2c libraries. File arguments ending with .f are compiled as Fortran source files. Files which end with .P are passed through to f2c, and files ending with .F are passed to the C preprocessor (invoked as "/lib/cpp -traditional") first. Any switches passed via -D will be passed to the pre- processor. If the translation is successful, the resulting C files will be passed to cc for translation into an object file. Files ending in .c, .C, .cc, .i, .s, .S, .m, .cc or .cxx are passed to the GNU C compiler directly; see gcc(1). All other files are passed to the linker. OPTIONS
-c Supress linking and produce an object ( .o ) file from each source file. -g Include debugging information. -v Be verbose; supplying this twice will also tell the C compilers etc to be verbose. -k Keep the C files generated by f2c around. -cpp Pass Fortran code through the C preprocessor, as if filenames ended in .F. -P Generate f2c .P files. -Ldirectory Include directory in the search for libraries in the final linking stage. -o outfile Send output to outfile. -trapuv Have f2c generate code to trap uninitialized values. -Wx,arg1[,arg2...] Pass the argument[s] argi through to the subprocess x, where x can assume one of the following values: f for the f2c step, p for the preprocessing step, c for the C compiler, a for the assembler (this is actually passed to the C compiler, too), and l for the linker. As an example, defining a preprocessor constant for the C compilation step would be done with -Wc,-DUNIX=1. Specifying the -f option to f2c would be done via -Wf,-f. f2c option fort77 passes through almost all f2c options: -C, -U, -u, -a, -E, -h, -P, -R, -r, -z, -I2, -I4, -onetrip, -!c, -!l, -!P, -!R, -ext, -!bs, -W[n], -trapuv, -w8, -r8 and -w66. gcc options The following options are passed through to gcc: -f*, -W*, -U*, -A*, -m*, -S, -E, -v, -x, -pipe, -o, -I, -V, -b*, -p, -pg. linker option The options passed to the linking stage are -static, -shared, -v, -V, and -symbolic. BUGS
To make debugging work, you need to set a breakpoint at MAIN__ before you start. f2c This script automatically supplies the -I. option to f2c. Older versions of f2c may not support this. This script is for the interaction of gcc and f2c; using it with another compiler will probably require modification. The fort77 script does not strictly conform to Posix.2, because it acceppts long options with one leading slash. This is done for gcc com- patibility. SEE ALSO
f2c(1), cc(1), as(1), ld(1) AUTHOR
Thomas Koenig, ig25@rz.uni-karlsruhe.de Linux Nov 1996 FORT77(1)
All times are GMT -4. The time now is 04:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy