From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7617 invoked by alias); 11 Jun 2003 19:39:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7526 invoked from network); 11 Jun 2003 19:39:57 -0000 Received: from unknown (HELO delta.ds2.pg.gda.pl) (213.192.72.1) by sources.redhat.com with SMTP; 11 Jun 2003 19:39:57 -0000 Received: from localhost by delta.ds2.pg.gda.pl (8.9.3/8.9.3) with SMTP id VAA14371; Wed, 11 Jun 2003 21:32:12 +0200 (MET DST) X-Authentication-Warning: delta.ds2.pg.gda.pl: macro owned process doing -bs Date: Wed, 11 Jun 2003 19:39:00 -0000 From: "Maciej W. Rozycki" To: Alexandre Oliva cc: Nathanael Nerode , gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com Subject: Re: Partial autoconf transition thoughts In-Reply-To: Message-ID: Organization: Technical University of Gdansk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-06/txt/msg00190.txt.bz2 On 11 Jun 2003, Alexandre Oliva wrote: > > Agreed, as long as there is a way to have $host_alias and $target_alias > > set up as desired. > > We (toplevel, not autoconf) call them $host_noncanonical and > $target_noncanonical now. autoconf no longer provides this feature. It's good we do that, but it's bad autoconf does not. Any reasonable justification? > > $ locate libbfd-2.13.2.1.so > > /usr/i386-linux/mips64el-linux/lib/libbfd-2.13.2.1.so > > /usr/i386-linux/mipsel-linux/lib/libbfd-2.13.2.1.so > > /usr/lib/libbfd-2.13.2.1.so > > > Where does that "i386-linux" above come from, then? > > Seems like an artifact of your install. I don't think we use host in > install pathnames by default. Well, see how AM_INSTALL_LIBBFD is defined. ;-) There was a discussion last year... > > Well, this is probably an option, but I don't know why such a > > complication necessary. > > It's necessary because of changes in autoconf that make the > propagation of command-line flags from build to host and host to > target not easily available. If we want to avoid using the 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. Why can't the same be done for $host_alias and $target_alias at the same place? I hope not for the lone reason of differing between implied and user-specified values -- it can be trivially be done differently and more explicitly => cleanlier. > canonicalized names, which we do, using the macros written by > Nathanael is pretty much the only way to go. That's a reasonable approach for now, but why can't autoconf be fixed ultimately? > > Have you seen the dependency graphs I sent yesterday? I believe my > > proposal is the simplest solution. > > I believe Nathanael's macros are the implementation of the solution. > BTW, we already use them. See config/acx.m4. Indeed, but I would prefer to see it done in autoconf so that it need not be repeated locally elsewhere. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +