From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Alexandre Oliva <aoliva@redhat.com>
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: Thu, 12 Jun 2003 11:21:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.1030612130728.25948D-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <oru1awnycc.fsf@free.redhat.lsd.ic.unicamp.br>
On 11 Jun 2003, Alexandre Oliva wrote:
> > 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.
But libbfd is target-specific, so you can't install it directly in
$exec_prefix. As the result of the discussion I wrote of, the current
approach was selected from two alternatives:
$exec_prefix/$host_alias/$target_alias/lib and
$exec_prefix/$target_alias/$host_alias/lib. Of coures neither
$exec_prefix/lib nor $exec_prefix/$target_alias/lib can be used as they
(may) hold other versions of libbfd and $exec_prefix/$host_alias cannot
be, either, as it would work for a single target only.
> > 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?
2.57
> > I hope not for the lone reason of differing between
> > implied and user-specified values
>
> This was the reason for the behavior change, yes.
IMHO, it should be stated explicitly, e.g. $host_cross and $target_cross
be set to "yes" if --host and --target are specified by a user,
respectively, otherwise they should be set to "no" and
${build,host,target}_alias should be set to valid system names
unconditionally. This should simplify the generated output and move the
decision on native vs cross to a single place.
> > 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.
OK, so I assume that's more an accident during the transition to the new
setup of 2.5x than a design decision. Good.
> > 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
I would actually do that a bit differetly, more or less as I stated
above, but I would of course look at the Nathanael's macros and reuse to
good bits. Anyway don't hold your breath -- I lack time these days
desperately. I'll look at this problem when I can afford.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-06-12 11:21 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
2003-06-12 11:21 ` Maciej W. Rozycki [this message]
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=Pine.GSO.3.96.1030612130728.25948D-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).