There are a lot of compiling options, and no global option for a "usefull" compilation
And with
Code:
-qinfo=all
I get a big list (more than 3000 lines!) of warning concerning headers in /usr/include/ directory like this :
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 ?
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
hardened-cc
HARDENED-CC(1) Debian GNU/Linux HARDENED-CC(1)NAME
hardened-cc - gcc wrapper to enforce hardening toolchain improvements
SYNOPSIS
export DEB_BUILD_HARDENING=1
gcc ...
DESCRIPTION
The hardened-cc wrapper is normally used by calling gcc as usual when DEB_BUILD_HARDENING is set to 1. It will configure the necessary
toolchain hardening features. By default, all features are enabled. If a given feature does not work correctly and needs to be disabled,
the corresponding environment variables mentioned below can be set to 0.
ENVIRONMENT
DEB_BUILD_HARDENING=1
Enable hardening features.
DEB_BUILD_HARDENING_DEBUG=1
Print the full resulting gcc command line to STDERR before calling gcc.
DEB_BUILD_HARDENING_STACKPROTECTOR=0
Disable stack overflow protection. See README.Debian for details.
DEB_BUILD_HARDENING_RELRO=0
Disable read-only linker sections. See README.Debian for details.
DEB_BUILD_HARDENING_FORTIFY=0
Don't fortify several standard functions. See README.Debian for details.
DEB_BUILD_HARDENING_PIE=0
Don't build position independent executables. See README.Debian for details.
DEB_BUILD_HARDENING_FORMAT=0
Disable unsafe format string usage errors. See README.Debian for details.
NOTES
System-wide settings can be added to /etc/hardening-wrapper.conf, one per line.
The real gcc symlinks are renamed gcc.real, and a diversion is registered with dpkg-divert(1). Thus hardened-cc's idea of the default gcc
is dictated by whatever package installed /usr/bin/gcc.
SEE ALSO hardened-ld(1)gcc(1)Debian Project 2008-01-08 HARDENED-CC(1)
01-19-2011
