From: Daniel Jacobowitz <drow@mvista.com>
To: binutils@sources.redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: [toplevel] Gas install name problem from autoconf 2.5x
Date: Wed, 03 Sep 2003 14:49:00 -0000 [thread overview]
Message-ID: <20030903144928.GA7255@nevyn.them.org> (raw)
In-Reply-To: <m38yp6v607.fsf@gossamer.airs.com>
On Tue, Sep 02, 2003 at 09:40:56PM -0700, Ian Lance Taylor wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> > I've gotten a report that gas now installs after a native build as
> > $(target_alias)-as. This is presumably the one consequence of autoconf
> > 2.5x's "specify absolutely nothing on the command line unless absolutely
> > necessary" policy.
> >
> > I see two basic choices:
> > - Override AC_CANONICAL_TARGET.
> > - Always pass down --program-transform-name from the top level.
> >
> > I think the latter is the way to go. Any other opinions?
>
> Is this yet another quiet autoconf change? Formerly,
> program_transform_name didn't do anything in the case where host_alias
> and target_alias were the same.
>
> I see that now it does something whenever target_alias is set. I
> can't see any documentation about this behaviour, but then the old
> behaviour probably wasn't documented either.
Yes, that appears to be what's going on.
> I guess my question is: why is --target being passed down from the top
> level in the native case? I thought part of the autoconf conversion
> was that the top level had to stop passing down --target all the time.
>
> Anyhow, I think it would be moderately useful if `make install' worked
> correctly in the gas subdirectory. I don't know what is required to
> make that happen.
Well, up to now, it didn't make any difference. We could use the third
option:
- Don't pass $target unless it was given on the command line.
This is definitely a good idea, but I was going to do that after most
directories had converted. Enough people configure native compilers
now by giving all of build/host/target that I'm not very happy with the
solution.
How do we feel about migrating towards the new autoconf definitions -
i.e. anything with --host is cross-compiled, anything with --target is
a cross-compiler.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-03 14:49 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 [this message]
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
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=20030903144928.GA7255@nevyn.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.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