9 More Discussions You Might Find Interesting
1. Programming
recently i was been to an interview to an automotive company, they have posed me a question that what section of compiler must be changed if the target is changed.
ie,if ur compiler is meant for generating executable to a 8051 target what changes do you do to make it flexible to generate the... (2 Replies)
Discussion started by: shyam.sunder91
2 Replies
2. UNIX for Dummies Questions & Answers
hi,
can we install gcc compiler in unix based OS(sun solar,IBM AIX,HP,etc) and also
can we install sun cc compiler in AIX environment and vice versa.
and more ..is linux support cc compiler
regards
Ajay (3 Replies)
Discussion started by: ajaysahoo
3 Replies
3. Linux
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (1 Reply)
Discussion started by: raghuhb
1 Replies
4. UNIX for Advanced & Expert Users
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (1 Reply)
Discussion started by: raghuhb
1 Replies
5. Red Hat
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (0 Replies)
Discussion started by: raghuhb
0 Replies
6. SuSE
Hi All
I want to create build machine for three architecture (i386, amd64 and ia64) on 32bit machine on OpenSUSE 10.0
I installed:
cross-i386-gcc-icecream-backend-4.3.1_20080507-7.1
cross-i386-binutils-2.18.50.20080409-12.1
cross-x86_64-gcc-icecream-backend-4.3.1_20080507-7.1... (0 Replies)
Discussion started by: Kolesar
0 Replies
7. Linux
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
8. Linux
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
9. Solaris
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
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)