08-24-2016
First off: welcome to the forum, but PLEASE use code-tags!
Quote:
I have exactly the same problem, did you manage to solve it?.
See above, i posted the solution: install one of the packages with the
--nodeps-option. I know this to work because i did so and it worked for me with (in the meantime) several versions of the gcc-compiler.
I hope this helps.
bakunin
9 More Discussions You Might Find Interesting
1. IP Networking
hi,
i am a pretty good linux user..but i have no idea on building a server witha domain and everthing. please help! (5 Replies)
Discussion started by: hamza11050
5 Replies
2. UNIX for Dummies Questions & Answers
Hi, im building a new PC for my FreeBSD - sorry it's not really UNIX related but I dont really visit any other online forums, and lost ideas of people to ask,
Basically would it work if bought this motherboard -... (0 Replies)
Discussion started by: ErNci
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
we are converting from IBM-AIX(xl c/c++ compiler) to Linux(GCC complier).
As a part of this i need to change the CFLAGS.
The xl c/c++ complier CFLAGS is
CFLAGS := $(CDEBUG) $(PROJECT_INCLUDE_DIRS) $(COBJECT_MODE) -qcpluscmt -qmakedep -qcheck=all \
-qalign=bit_packed $(LINT_FLAGS)... (0 Replies)
Discussion started by: pbattu1
0 Replies
4. Programming
To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first?
The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's...
Eventhough i... (12 Replies)
Discussion started by: f.ben.isaac
12 Replies
5. UNIX and Linux Applications
Hi,
I've installed firewall builder into my operating system (PCLinuxOS) from the repository. Now I need to configure and make run firewall builder in the main server (production server) of my company.
The technique that I want to use is pushing the script from my laptop (where I've got the... (3 Replies)
Discussion started by: anaigini45
3 Replies
6. 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
7. 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
8. 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
9. 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
LEARN ABOUT DEBIAN
fort77
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)