From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Khem Raj <raj.khem@gmail.com>
Subject: gcc 4.8
Date: Thu, 23 May 2013 18:23:47 -0500 [thread overview]
Message-ID: <519EA503.4000303@windriver.com> (raw)
I found an issue w/ the gcc 4.8 in oe-core as on Monday. Some of my automated
build machines are RHEL 5.9 machines. These boxes have a host compiler that
does not support -Wno-narrowing and -Wno-overlength-strings. Unfortunately,
when building target gcc (via the cross compiler) the system tries to use target
compiler options on the system host compiler.
I tracked this down to the configure script checks support for those warnings
(and others), but it only looks with the $CC value. It then passes these values
in via LOOSE_WARN and STRICT_WARN.. eventually these go through the system and
end up in BUILD_COMPILERFLAGS via ALL_CXXFLAGS via WARN_CXXFLAGS via
GCC_WARN_CXXFLAGS... So configure checking only the cross compiler is the issue.
Below is the error that I got:
g++ -c -O2 -pipe -g -fvisibility-inlines-hidden -DIN_GCC -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -DGENERATOR_FILE
-I. -Ibuild
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemu
ppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/build
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../include
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../libcpp/include
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../libdecnumber
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../libdecnumber/dpd
-I../libdecnumber
-I/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../libbacktrace
\
-DBASEVER="\"4.8.0\"" -DDATESTAMP="\"\"" \
-DREVISION="\"\"" \
-DDEVPHASE="\"\"" -DPKGVERSION="\"(GCC) \"" \
-DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o build/version.o
/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/version.c
cc1plus: error: unrecognized command line option "-Wno-narrowing"
cc1plus: error: unrecognized command line option "-Wno-overlength-strings"
make[2]: *** [build/version.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/bin/sh
/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/gcc/../move-if-change
tmp-optionlist optionlist
echo timestamp > s-options
make[2]: *** wait: No child processes. Stop.
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory
`/home/nxadm/nx/yow-blade16.1/builds-2013-05-23-130402/qemuppc_world/bitbake_build/tmp/work/ppc603e-wrs-linux/gcc/4.8.0-r0/gcc-4.8.0/build.powerpc-wrs-linux.powerpc-wrs-linux'
reply other threads:[~2013-05-23 23:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519EA503.4000303@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox