Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: (toplevel patch) Use canonical names for target_subdir, build_subdir.
Date: Fri, 24 Jan 2003 19:16:00 -0000	[thread overview]
Message-ID: <orsmvis6il.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3E3186B3.2050906@twcny.rr.com>

On Jan 24, 2003, Nathanael Nerode <neroden@twcny.rr.com> wrote:

>> I see where you're coming from, but we're really going to have to bite
>> the bullet and duplicate autoconf 2.5x's behavior WRT machine name

> You mean autoconf 2.13's behavior, I assume...

No, I meant duplicating the logic that 2.5x uses to set canonical
names to propagate the corresponding non-canonical names.

> OK.  I'll do this the easy way:  I'll write Autoconf macros which
> determine the "target_subdir" and "build_subdir" (exactly the same way
> they're determined now), put the macros in an include file, and
> rewrite the configure scripts to include it.  How does that sound?

I fail to see the point, but if you want to take the code out into a
macro, don't let me stop you.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


  reply	other threads:[~2003-01-24 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  3:41 Nathanael Nerode
2003-01-24 16:51 ` Alexandre Oliva
2003-01-24 18:32   ` Nathanael Nerode
2003-01-24 19:16     ` Alexandre Oliva [this message]
2003-01-26 12:22   ` Phil Edwards
2003-01-26 12:45     ` Alexandre Oliva
2003-01-27 14:56       ` Phil Edwards
2003-01-27 15:26         ` Phil Edwards
2003-01-25  0:56 ` Andreas Schwab
2003-01-25 21:27   ` Phil Edwards

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=orsmvis6il.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=neroden@twcny.rr.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