This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: sed: command garbled
- To: aoliva at redhat dot com
- Subject: Re: sed: command garbled
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Thu, 3 Aug 2000 17:49:21 -0400
- Cc: gcc-bugs at gcc dot gnu dot org
> >> > breaks a build when libstdc++-v3 is enabled:
> >>
> >> Yup, I've already posted another patch that addresses this problem.
>
> > Which patch was it, so I can push for inclusion
>
> It's already checked in. Update your tree to the current HEAD and you
> should get it.
I already had the current HEAD, and just now updated it to be sure.
The problem is fixed with the configuration defaults, but passing
--enable-libstdcxx-v3 breaks it again.
And I can't seem to come up with a minimal change to configure.in that
lets it work. The amount of nested quoting required is just too much.
(It's around line 54 currently, setting libstdcxx_flags.) There's probably
a clean solution, but one that requires more rewriting, and I don't know
what that section of the script is supposed to do.
Phil
P.S.- Should that top-level configure.in really have /bin/bash as its
#! invocation line? I'm all for a Bourne shell that doesn't suck,
but is that safe?