libstdc++ multilib configury broken in CVS head
Benjamin Kosnik
bkoz@redhat.com
Tue Dec 17 13:51:00 GMT 2002
>... that with_build_subdir and with_target_subdir are used
>but not defined here.
Ouch. As you can see, I stole the code outright from libiberty/configure.in...
>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?
Yes, sorry about that.
>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).
I'm using the autoconf 2.13 that ships on RH 7.3
-benjamin
More information about the Gcc
mailing list