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, binutils@sources.redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: [toplevel patch] Macroize build_subdir & target_subdir, newest version
Date: Sat, 31 May 2003 21:58:00 -0000	[thread overview]
Message-ID: <or65nqn5hc.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030317144503.GA16592@doctormoo>

On Mar 17, 2003, Nathanael Nerode <neroden@twcny.rr.com> wrote:

> 	* config/acx.m4: Introduce _GCC_TOPLEV_NONCANONICAL_BUILD,
> 	_GCC_TOPLEV_NONCANOICAL_HOST, _GCC_TOPLEV_NONCANONICAL_TARGET,
> 	GCC_TOPLEV_SUBDIRS.
> 	* configure.in: Use GCC_TOPLEV_SUBDIRS.

This is ok, if still appropriate.  Sorry that it took so long for me
to get to it.

We still have problems in deciding what options to pass down to
sub-configures, because autoconf 2.5x's behavior in deciding whether
we're cross compiling or not depends on the actual command-line flags,
not only on the implied defaults.  Still, your patch is a step in the
right direction.

As for solving the problem of not passing --build, --host or --target
to sub-configures when it's implied, to avoid crossification :-), one
idea that was floated in the GCC Summit (was it Zack?  I seem to
recall two people independently proposing it, but I don't remember who
else did it, sorry) was to set up two different _CONFIGARGS variable
per build, host and target, and grep the autoconf version number in
the configure script to tell which version to use.  This sounds like
the only sane (even if ugly) way to avoid having to convert the entire
tree (gcc, src and what not) to the new autoconf at the same time.

-- 
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-05-31 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 14:45 Nathanael Nerode
2003-05-31 21:58 ` Alexandre Oliva [this message]

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=or65nqn5hc.fsf@livre.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