This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ multilib configury broken in CVS head
- From: Ulrich Weigand <weigand at immd1 dot informatik dot uni-erlangen dot de>
- To: dj at redhat dot com, bkoz at redhat dot com
- Cc: gcc at gcc dot gnu dot org, uweigand at de dot ibm dot com
- Date: Tue, 17 Dec 2002 22:19:43 +0100 (MET)
- Subject: Re: libstdc++ multilib configury broken in CVS head
DJ Delorie wrote:
>It looks like it should run config-ml.in (which is where that message
>comes from). Try "sh -vx configure ..." and see if it does.
Indeed, config-ml.in does not run. And the reason is ...
Benjamin Kosnik wrote:
>It's probaby the --enable-debug patch. I did some cleanups to
>libstdc++-v3/configure.in WRT multilibs.
[snip]
>! [test -z "$CONFIG_HEADERS" || echo timestamp > stamp-h
>! if test -n "$CONFIG_FILES"; then
>! if test -n "${with_build_subdir}" || test -n "${with_target_subdir}"; then
>! LD="${ORIGINAL_LD_FOR_MULTILIBS}"
>! ac_file=Makefile . ${glibcpp_basedir}/../config-ml.in
... that with_build_subdir and with_target_subdir are used
but not defined here.
Comparing with the setup in the working target library
configure.in files, it would appear that something like
this should fix the problem:
Index: libstdc++-v3/configure.in
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/configure.in,v
retrieving revision 1.111
diff -c -p -r1.111 configure.in
*** libstdc++-v3/configure.in 16 Dec 2002 19:01:55 -0000 1.111
--- libstdc++-v3/configure.in 17 Dec 2002 21:02:03 -0000
*************** chmod +x testsuite_flags
*** 489,494 ****
--- 489,496 ----
srcdir=${srcdir}
host=${host}
target=${target}
+ with_target_subdir=${with_target_subdir}
+ with_build_subdir=${with_build_subdir}
with_multisubdir=${with_multisubdir}
ac_configure_args="${multilib_arg} ${ac_configure_args}"
CONFIG_SHELL=${CONFIG_SHELL-/bin/sh}
I'm currently running a multilibbed bootstrap/regtest on
s390x-ibm-linux with this change; OK to commit if this
goes through?
B.t.w. I'm unable to regenerate an unchanged libstdc++
'configure' file. Which autoconf version was used to
generate it? Apparently not the same that is used for
the rest of gcc (e.g. the --site-file stuff is missing).
Thanks,
Ulrich
--
Dr. Ulrich Weigand
weigand@informatik.uni-erlangen.de