Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: <bonzini@gnu.org>, 	"'Andreas Schwab'" <schwab@suse.de>,
		"'Steve Ellcey'" <sje@cup.hp.com>, 	<binutils@sourceware.org>,
		<gcc-patches@gcc.gnu.org>, 	<gdb-patches@gcc.gnu.org>,
		<newlib@sourceware.org>, 	<aoliva@redhat.com>,
		<libtool@cwilson.fastmail.fm>
Subject: RE: Final(?) patch to update libtool in GCC and src trees
Date: Wed, 11 Apr 2007 09:23:00 -0000	[thread overview]
Message-ID: <00c101c77c1b$05fd0e20$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <461CA33C.2010209@lu.unisi.ch>

On 11 April 2007 09:59, Paolo Bonzini wrote:

>>> Does AS_IF put required macros outside its expansion?  That's a
>>> cool feature if it does.
>> 
>> Only with Autoconf 2.60 and newer.
> 
> I see; so it's ruled out for now.

  I used 2.60 to regenerate in newlib/, was that the wrong thing to do?

/usr/build/src-winsup/newlib $ head -3 configure
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.60 for newlib 1.15.0.

>>> However, if this is the case, it is also a problem.
>>> AM_PROG_LIBTOOL used to expand its subparts via
>>> AC_REQUIRE, which would sort of undo the effect of
>>> the if statement.
>> 
>> Yes, I don't think it'll help here.  But also I don't see why CXX should
>> come into play here at all, if not by an old 1.5.x libtool.m4 file that
>> is picked up by aclocal (without having tested anything, though).
> 
> Dave, can you check the content of newlib/aclocal.m4?
> 
> Paolo

  That would be the freshly regenerated one:

/usr/build/src-winsup/newlib $ head -1 aclocal.m4
# generated automatically by aclocal 1.9.6 -*- Autoconf -*-

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


  reply	other threads:[~2007-04-11  9:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 18:25 Steve Ellcey
2007-04-10 18:42 ` Andrew Pinski
2007-04-10 20:04   ` Steve Ellcey
2007-04-10 20:02 ` Dave Korn
2007-04-10 20:07   ` Steve Ellcey
2007-04-10 20:58     ` Dave Korn
2007-04-11  1:13     ` Dave Korn
2007-04-11  7:36       ` Paolo Bonzini
2007-04-11  8:47         ` Andreas Schwab
2007-04-11  8:51           ` Paolo Bonzini
2007-04-11  8:57             ` Ralf Wildenhues
2007-04-11  8:59               ` Paolo Bonzini
2007-04-11  9:23                 ` Dave Korn [this message]
2007-04-11  9:25                   ` Paolo Bonzini
2007-04-11 10:00                     ` Dave Korn
2007-04-11 10:19                       ` Paolo Bonzini
2007-04-11 21:41                         ` Christopher Faylor
2007-04-12 10:42                           ` Dave Korn
2007-04-11  2:38     ` Charles Wilson
2007-04-12  6:36       ` Charles Wilson
2007-04-12  7:03         ` Paolo Bonzini
2007-04-12 15:13         ` Steve Ellcey
2007-04-12 18:02           ` Charles Wilson
2007-04-13  7:18 ` Paolo Bonzini
2007-04-13 17:27   ` Steve Ellcey
2007-04-13 18:05     ` Daniel Jacobowitz
2007-04-13 18:18       ` Paolo Bonzini
2007-04-13 18:27         ` Steve Ellcey
2007-04-13 18:38           ` Paolo Bonzini
2007-04-13 18:44             ` Steve Ellcey
2007-04-13 20:19           ` Charles Wilson
2007-04-13 18:24     ` Paolo Bonzini

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='00c101c77c1b$05fd0e20$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=libtool@cwilson.fastmail.fm \
    --cc=newlib@sourceware.org \
    --cc=schwab@suse.de \
    --cc=sje@cup.hp.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