Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com, dj@redhat.com
Subject: Re: [toplevel] Gas install name problem from autoconf 2.5x
Date: Sun, 07 Sep 2003 03:59:00 -0000	[thread overview]
Message-ID: <20030907035909.GA10111@nevyn.them.org> (raw)
In-Reply-To: <oroey15cx3.fsf@free.redhat.lsd.ic.unicamp.br>

On Thu, Sep 04, 2003 at 02:40:40AM -0300, Alexandre Oliva wrote:
> On Sep  3, 2003, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> >> The new scheme is to specify --build instead.  $host defaults to
> >> $build.
> 
> > Unfortunately I'm not sure that this works with older versions of
> > autoconf.  In fact I'm pretty sure that it doesn't.
> 
> It doesn't.  You (toplev) have to know what (subdir's) autoconf you're
> talking to.
> 
> > I think that, as you said, we do not have any choice.  The alternative
> > is forking autoconf to reverse the decision, and I certainly don't
> > want to do that.
> 
> I think the autoconf decision was sound (although I disliked it
> because I could see the amount of disruption it would cause), but it's
> done, so we'll have to choose a date to call flag day.

In the mean time, how about a different solution?

I would like to explicitly pass --program-transform-name from the
toplevel to subdirectories, when configure implicitly generates it. 
How does that sound?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-07  3:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  4:10 Daniel Jacobowitz
2003-09-03  4:41 ` Ian Lance Taylor
2003-09-03 14:49   ` Daniel Jacobowitz
2003-09-03 15:31     ` DJ Delorie
2003-09-03 16:13       ` Ian Lance Taylor
2003-09-03 16:56         ` Daniel Jacobowitz
2003-09-04  5:40           ` Alexandre Oliva
2003-09-07  3:59             ` Daniel Jacobowitz [this message]
2003-09-07  4:08               ` Ian Lance Taylor
2003-09-07 17:33                 ` Daniel Jacobowitz
2003-09-03 16:12     ` Ian Lance Taylor
2003-09-04  5:37 ` Alexandre Oliva

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=20030907035909.GA10111@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.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