This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
[PATCH] Empty libstdc++ cpu config directories
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Mon, 2 Feb 2004 12:34:39 +0000
- Subject: [PATCH] Empty libstdc++ cpu config directories
- Organization: CodeSourcery
Libstdc++ currently fails to build if there is an empty directory in
config/cpu. This can happen in cvs checkouts eg. on arm where cvs only
contains deleted files.
We used to have logic to check if the required file (atomicity.h) actually
exists, but this seems to have disappeared when configure.target was renamed
configure.host. The patch below reinstates this check.
Tested on i686-linux and cross-compiler to arm-none-elf.
Ok? Or is the correct solution simply "don't do that"?
Paul
2004-02-02 Paul Brook <paul@codesourcery.com>
* libstdc++-v3/configure.host: Explicitly check for atomicity.h.
Index: configure.host
===================================================================
RCS file: /var/cvsroot/gcc-cvs/gcc/libstdc++-v3/configure.host,v
retrieving revision 1.22
diff -u -r1.22 configure.host
--- configure.host 27 Jan 2004 15:36:22 -0000 1.22
+++ configure.host 30 Jan 2004 14:26:06 -0000
@@ -106,8 +106,12 @@
# default choices for those if they haven't been explicitly set
# already.
cpu_include_dir="cpu/${try_cpu}"
-atomicity_include_dir=$cpu_include_dir
abi_baseline_pair=${try_cpu}-${host_os}
+if test -f ${glibcxx_srcdir}/config/${cpu_include_dir}/atomicity.h ; then
+ atomicity_include_dir=$cpu_include_dir
+else
+ atomicity_include_dir="cpu/generic"
+fi
# Set any OS-dependent bits.