This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Version 1.126 of libstdc++-v3/configure.in broke pre-installednewlib builds
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 4 Jun 2003 14:47:42 -0400 (EDT)
- Subject: Re: Version 1.126 of libstdc++-v3/configure.in broke pre-installednewlib builds
On Wed, 4 Jun 2003, Benjamin Kosnik wrote:
> >You don't want to fix what you broke?
>
> I'd like to help you figure out a way to get your toolchain working
> again. I don't think just reverting this patch is the right idea, since
> the patch itself seems correct and fixes other bugs.
Yes.
> What needs to
> happen is additional bits need to get added so that your config works:
Yes, and as I indicated in my first mail, this is what I'm
suggesting. Since you're the one that broke this (by the new
requirement), I'm asking you to do it.
> this may be in the configure bits of libstdc++, or this may be you
> configuring with --with-sysroot.
>
> Can you try --with-sysroot? Personally, I think this best matches what
> you are trying to do.
No, I don't want to do that. I have a pre-installed library,
but not on the (different) path mandated with --with-sysroot.
Besides, that wouldn't fix the breakage or remove the
requirement that newlib be built at the same time libstdc++-v3
is, *or* possibly --with-sysroot be used. ;-)
Hum, speaking of that, I can't think of why --with-sysroot would
help; it's not tested by libstdc++-v3/configure.in.
brgds, H-P