Sponsored Content
Operating Systems AIX xlc compiler options versus gcc Post 302489033 by domiq44 on Wednesday 19th of January 2011 09:33:20 AM
Old 01-19-2011
Yes, I've already look at the manual.

There are a lot of compiling options, and no global option for a "usefull" compilation Smilie

And with
Code:
-qinfo=all

I get a big list (more than 3000 lines!) of warning concerning headers in /usr/include/ directory like this : Smilie
Quote:
...
"/usr/include/unistd.h", line 950.2: 1506-456 (I) Stop skipping tokens.
"/usr/include/unistd.h", line 952.2: 1506-460 (I) endif nesting level is 1.
"manager02.c", line 8: 1506-733 (I) Processing #include file /usr/include/errno.h.
"/usr/include/errno.h", line 35.2: 1506-460 (I) ifndef nesting level is 1.
"/usr/include/errno.h", line 35.2: 1506-454 (I) ifndef condition evaluates to 1.
"/usr/include/errno.h", line 37.23: 1506-457 (I) File /usr/include/standards.h has already been included.
"/usr/include/errno.h", line 37: 1506-530 (I) Header /usr/include/standards.h not included again because it would have no effect due to conditional compilation.
"/usr/include/errno.h", line 48.2: 1506-460 (I) ifdef nesting level is 2.
"/usr/include/errno.h", line 48.2: 1506-454 (I) ifdef condition evaluates to 1.
"/usr/include/errno.h", line 50.2: 1506-460 (I) ifndef nesting level is 3.
"/usr/include/errno.h", line 50.2: 1506-454 (I) ifndef condition evaluates to 1.
"/usr/include/errno.h", line 52.2: 1506-460 (I) if nesting level is 4.
"/usr/include/errno.h", line 52.13: 1506-455 (I) defined(_THREAD_SAFE) evaluates to 0.
"/usr/include/errno.h", line 52.38: 1506-455 (I) defined(_THREAD_SAFE_ERRNO) evaluates to 0.
"/usr/include/errno.h", line 52.2: 1506-454 (I) if condition evaluates to 0.
"/usr/include/errno.h", line 52.2: 1506-464 (I) Begin skipping tokens.
"/usr/include/errno.h", line 60.2: 1506-460 (I) else nesting level is 4.
"/usr/include/errno.h", line 60.2: 1506-456 (I) Stop skipping tokens.
"/usr/include/errno.h", line 64.2: 1506-460 (I) endif nesting level is 4.
"/usr/include/errno.h", line 66.2: 1506-460 (I) endif nesting level is 3.
...
Does anyone can give me some usefull standards options of xlc to use with common project ?

Last edited by domiq44; 01-19-2011 at 10:43 AM..
 

8 More Discussions You Might Find Interesting

1. HP-UX

cc compiler options

hi , I am compiling a C program with ccopts and cflags . i am getting error message main ( Not referenced yet ! probably due -u option ) can you please adice , how to get rid of this error. Many thanks Narendra babu C (3 Replies)
Discussion started by: naren_chella
3 Replies

2. UNIX for Dummies Questions & Answers

xl C/C++ compiler to GCC compiler

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

3. AIX

AIX Xlc compiler

Hi Team I have a native applicaiton built on AIX using the xLC v8 Which could be the possible impacts from a code change point of view if I'll compile with the xLC v10? Thanks Marco (0 Replies)
Discussion started by: antcos
0 Replies

4. UNIX for Advanced & Expert Users

XLC compiler: enterprise edition VS XLC for AIX

Who can explain in a few words the difference between XLC for AIX and XLC enterprise Edition for AIX (0 Replies)
Discussion started by: fvaltat1
0 Replies

5. UNIX for Dummies Questions & Answers

cc compiler and gcc compiler

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

6. AIX

Checking xlc compiler version

Hi, Below is output of lslpp command. bash-3.00# lslpp -L | grep xlC xlC.aix50.rte 11.1.0.1 C F XL C/C++ Runtime for AIX 5.3 xlC.cpp 9.0.0.0 C F C for AIX Preprocessor xlC.msg.en_US.cpp 9.0.0.0 C F C for AIX... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

7. AIX

AIX xlc compiler vs gcc

Hello, We are migrating some applications from previously running on an AIX system to a Linux RedHat system. I was tasked with recompiling some of the code. Unfortunatly I am a big novice on this. So i have the commands used to compile the code with xlc compiler in the AIX environment and i am... (0 Replies)
Discussion started by: spooksman
0 Replies

8. Linux

Xlc compiler on Redhat Linux

Hi , Currently i have my c and pro*c code got compiled in IBM POWER - AIX machine with xlc compiler version 9. We are planning to migrate all our applications from IBM POWER - AIX to Redhat Linux. Can i use the same current (IBM AIX) xlc compiler with the same compiling... (3 Replies)
Discussion started by: mugunthanvh
3 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 05:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy