public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: sed: command garbled
Date: Thu, 03 Aug 2000 15:02:00 -0000 [thread overview]
Message-ID: <or4s52atr6.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200008032149.RAA07730@disaster.jaj.com>
On Aug 3, 2000, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> 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.
What do you get for CXX_FOR_TARGET in the top-level Makefile?
> 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?
It just doesn't matter at all. configure.in is always run with
${CONFIG_SHELL-/bin/sh}.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-08-03 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 14:47 Phil Edwards
2000-08-03 15:02 ` Alexandre Oliva [this message]
2000-08-03 15:17 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 16:15 Phil Edwards
2000-08-03 16:51 ` Alexandre Oliva
[not found] <200008031956.PAA07178@disaster.jaj.com>
2000-08-03 13:09 ` Alexandre Oliva
2000-07-31 21:45 Mike Stump
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=or4s52atr6.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=pedwards@disaster.jaj.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).