From: Alexandre Oliva <aoliva@redhat.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: Partial autoconf transition thoughts
Date: Wed, 11 Jun 2003 20:39:00 -0000 [thread overview]
Message-ID: <oru1awnycc.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.GSO.3.96.1030611210428.7397D-100000@delta.ds2.pg.gda.pl>
On Jun 11, 2003, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
> It's good we do that, but it's bad autoconf does not. Any reasonable
> justification?
It just isn't there. I don't remember whether Nathanael tried to
contribute his macros to autoconf. I do agree they'd make sense.
> Well, see how AM_INSTALL_LIBBFD is defined. ;-)
Presumably you're configuring with --enable-shared
--enable-install-libbfd. I'd never done that :-)
Anyway, $(exec_prefix)/$(host_alias) is entirely pointless.
$(exec_prefix) is already supposed to be host-specific.
> Why is that so? I am looking at what autoconf does right now and I can
> see that $ac_cv_host_alias is set to $ac_cv_build_alias if $host_alias is
> empty and $ac_cv_target_alias is set to ac_cv_host_alias if $target_alias
> is empty.
Which autoconf are you looking at?
> I hope not for the lone reason of differing between
> implied and user-specified values
This was the reason for the behavior change, yes.
> That's a reasonable approach for now, but why can't autoconf be fixed
> ultimately?
I can't think of any reason for that. But we're trying to move to
autoconf 2.57, not some hacked version thereof, so we have to cope
with its limitations for now.
> Indeed, but I would prefer to see it done in autoconf so that it need not
> be repeated locally elsewhere.
It feels like you're volunteering to convert Nathanael's macros into
autoconf, do I read it right? :-D :-D
--
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
next prev parent reply other threads:[~2003-06-11 20:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 0:40 Nathanael Nerode
2003-06-10 0:59 ` Alexandre Oliva
2003-06-10 10:59 ` Maciej W. Rozycki
2003-06-10 11:38 ` Andreas Schwab
2003-06-10 12:45 ` Maciej W. Rozycki
2003-06-10 22:06 ` Alexandre Oliva
2003-06-11 11:32 ` Maciej W. Rozycki
2003-06-11 18:04 ` Alexandre Oliva
2003-06-11 19:39 ` Maciej W. Rozycki
2003-06-11 20:39 ` Alexandre Oliva [this message]
2003-06-12 11:21 ` Maciej W. Rozycki
2003-06-12 12:10 ` Bernd Jendrissek
2003-06-12 12:26 ` Maciej W. Rozycki
2003-06-12 21:42 ` Alexandre Oliva
2003-06-13 10:35 ` Maciej W. Rozycki
2003-06-13 14:02 ` Alexandre Oliva
2003-06-13 18:32 ` Maciej W. Rozycki
2003-06-13 19:25 ` Alexandre Oliva
2003-06-13 20:15 ` Maciej W. Rozycki
2003-06-13 20:54 ` Alexandre Oliva
2003-06-14 14:33 ` Maciej W. Rozycki
2003-06-14 15:43 ` Alexandre Oliva
2003-06-14 18:27 ` Maciej W. Rozycki
2003-06-26 7:24 ` Alexandre Oliva
2003-06-28 0:35 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 1:40 Nathanael Nerode
2003-06-10 1:46 ` DJ Delorie
2003-06-09 22:02 Daniel Jacobowitz
2003-06-09 22:17 ` Andrew Cagney
2003-06-09 22:34 ` Alexandre Oliva
2003-06-09 23:14 ` Daniel Jacobowitz
2003-06-10 0:44 ` 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=oru1awnycc.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=macro@ds2.pg.gda.pl \
--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