From: Felix Lee <felix.1@canids.net>
To: "Theodore A. Roth" <troth@openavr.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] more sed fixes for Makefile.in
Date: Wed, 08 Oct 2003 00:07:00 -0000 [thread overview]
Message-ID: <20031008000714.5CAE1158F81@kanga.canids.net> (raw)
In-Reply-To: Message from Daniel Jacobowitz <drow@mvista.com> of "Tue, 07 Oct 2003 19:50:54 EDT." <20031007235054.GA14654@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com>:
> I think you may be right about the -e -e thing, but autoconf 2.5x and
> 2.13 both use ; instead.
yeah.
looks like the right way these days is
sed -e $$t
no quotes around the $$t, because configure does the quoting (and
uses 's,x,x,' for null transformation).
I just looked, there are lots of old configures in the tree that
don't do that quoting, but I think they're in directories that
don't use program_transform_name, so it might not matter.
also, sim/common/configure.in has a
t='\$(program_transform_name)'; echo gcc | sed -e 's/x/x/' \$\$t; \
that needs to be fixed
--
next prev parent reply other threads:[~2003-10-08 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 22:30 Theodore A. Roth
2003-10-07 22:55 ` Daniel Jacobowitz
2003-10-07 23:38 ` Felix Lee
2003-10-07 23:50 ` Daniel Jacobowitz
2003-10-08 0:07 ` Felix Lee [this message]
2003-10-08 0:15 ` Theodore A. Roth
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=20031008000714.5CAE1158F81@kanga.canids.net \
--to=felix.1@canids.net \
--cc=gdb-patches@sources.redhat.com \
--cc=troth@openavr.org \
/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