Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH] Unbreak program transformation name `configure' options
Date: Fri, 27 Apr 2012 16:49:00 -0000	[thread overview]
Message-ID: <4F9AC55F.5050404@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1204271642090.19835@tp.orcam.me.uk>

On 04/27/2012 04:46 PM, Maciej W. Rozycki wrote:

> On Fri, 27 Apr 2012, Pedro Alves wrote:
> 
>> It indeed removed AC_ARG_PROGRAM.  It also does this though:
>>
>> -AC_CONFIG_AUX_DIR(`cd $srcdir;pwd`/..)
>> +AC_CONFIG_AUX_DIR(..)
>>
>> I wonder if we need to restore that bit as well.
> 
>  I built out of the source directory so perhaps not?  This looks weird to 
> me, autoconf should handle that just fine:
> 
> "-- Macro: AC_CONFIG_AUX_DIR (DIR)
>      Use the auxiliary build tools (e.g., `install-sh', `config.sub',
>      `config.guess', Cygnus `configure', Automake and Libtool scripts,
>      etc.) that are in directory DIR.  These are auxiliary files used
>      in configuration.  DIR can be either absolute or relative to
>      `SRCDIR'.  The default is `SRCDIR' or `SRCDIR/..' or
>      `SRCDIR/../..', whichever is the first that contains `install-sh'."
> 
> -- perhaps this was a left-over from times when autoconf was more fragile?  
> I bet we have more places where we have some work-around logic left from 
> the old days.


Yeah, sounds like at some point AC_CONFIG_AUX_DIR didn't handle
relative paths to srcdir.  Thanks.

-- 
Pedro Alves


      reply	other threads:[~2012-04-27 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 15:23 Maciej W. Rozycki
2012-04-27 15:37 ` Tom Tromey
2012-04-27 15:38 ` Pedro Alves
2012-04-27 15:50   ` Maciej W. Rozycki
2012-04-27 16:49     ` Pedro Alves [this message]

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=4F9AC55F.5050404@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=tromey@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