Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
	kazu@cs.umass.edu, aoliva@redhat.com
Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name)
Date: Sat, 28 Dec 2002 04:36:00 -0000	[thread overview]
Message-ID: <20021228093127.GA455@doctormoo> (raw)

Alex pointed out:
>This unfortunately means that your fix is not quite perfect yet, since
>multiple transform commands would be word-split and sed might take
>them as input file names.  I suggest replacing:
>
>        t='$(program_transform_name)'; echo as | sed -e $$t ; \
>
>with
>
>        echo as | sed '$(program_transform_name)'; \
>
>that is the construct used by automake.

Unfortunately, I really have to go to sleep now. :-(  And I have to 
focus my mind on other things for a few days, too.

Please feel free to make this change on your own; it's obviously 
correct as far as I'm concerned.

And likewise to anyone else who wants to improve the top level;
now that autoconfiscation, and configure-on-demand, have actually 
happened, I just don't need the tight control on the top level files 
which I was exercising before.  (At least until I start on the new build 
scheme, which won't be for a while.)  

Part of the motivation for autoconfiscating was to make the top level less 
of a "secret region" which only the "initiated" could hack on.  I hope 
I've accomplished that.

--Nathanael


             reply	other threads:[~2002-12-28  9:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28  4:36 Nathanael Nerode [this message]
2002-12-28  8:33 ` Alexandre Oliva
2002-12-28  9:51   ` Daniel Jacobowitz
2002-12-28  9:56     ` Alexandre Oliva
2002-12-28  9:59       ` Daniel Jacobowitz
2002-12-28 10:41         ` Alexandre Oliva
2002-12-28 10:46           ` Dan Kegel
2002-12-28 11:07             ` DJ Delorie
2002-12-28 12:26               ` Daniel Jacobowitz
2002-12-28 10:50           ` Daniel Jacobowitz
2002-12-28 11:01             ` DJ Delorie
2002-12-28 12:57               ` Alexandre Oliva
2002-12-28 13:51                 ` Alexandre Oliva
2002-12-29 18:57                   ` Alexandre Oliva
2002-12-28 14:14                 ` DJ Delorie
2002-12-28 15:22                   ` Alexandre Oliva
2002-12-28 10:54           ` Alexandre Oliva
2002-12-28 10:49       ` DJ Delorie
2002-12-28 11:00 ` DJ Delorie
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06  0:49 Michael Elizabeth Chastain
2002-12-29  0:39 Michael Elizabeth Chastain
2002-12-29  2:48 ` Alexandre Oliva
2002-12-28 13:22 Michael Elizabeth Chastain
2002-12-28 13:44 ` Alexandre Oliva
2003-01-06  0:04 ` Ben Elliston
2002-12-28  1:00 Nathanael Nerode
2002-12-28  1:22 ` Alexandre Oliva
2002-12-28  1:33 ` Alexandre Oliva
2002-12-28  7:47 ` Kazu Hirata

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=20021228093127.GA455@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kazu@cs.umass.edu \
    /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