This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[toplevel] Set RAW_CXX_FOR_TARGET
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: binutils at sources dot redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Wed, 27 Aug 2003 13:00:17 -0400
- Subject: [toplevel] Set RAW_CXX_FOR_TARGET
Fixes some mysterious build failures in libstdc++-v3. I think a set of
"interesting configuration" autobuilders would be a Real Nice Thing...
If CXX_FOR_TARGET is set (either in the environment, which it is when I
build most of my host-x-host tools, or by configure.in, which it is for
all host-x-host builds anyway) then nothing sets RAW_CXX_FOR_TARGET. Then
it gets passed to the next level as "$(STAGE_CC_WRAPPER) $(FLAGS_FOR_TARGET)"
and we try to run -c, -V, etc as commands.
Is this patch OK?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-08-27 Daniel Jacobowitz <drow@mvista.com>
* configure.in: Set RAW_CXX_FOR_TARGET if unset.
* configure: Regenerated.
Index: configure.in
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/configure.in,v
retrieving revision 1.180
diff -u -p -r1.180 configure.in
--- configure.in 21 Aug 2003 02:21:21 -0000 1.180
+++ configure.in 27 Aug 2003 00:56:30 -0000
@@ -1938,7 +1938,9 @@ libstdcxx_flags='`test ! -f $$r/$(TARGET
raw_libstdcxx_flags=' -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src/.libs'
if test "x${CXX_FOR_TARGET+set}" = xset; then
- :
+ if test "x${RAW_CXX_FOR_TARGET+set}" != xset; then
+ RAW_CXX_FOR_TARGET=${CXX_FOR_TARGET}
+ fi
elif test -d ${srcdir}/gcc; then
# We add -shared-libgcc to CXX_FOR_TARGET whenever we use xgcc instead
# of g++ for linking C++ or Java, because g++ has -shared-libgcc by