From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, DJ Delorie <dj@redhat.com>,
gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org, newlib@sourceware.org
Subject: Re: Updating top-level autoconf to 2.59
Date: Tue, 13 Feb 2007 09:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64N.0702130909040.31957@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <m33b5fji8u.fsf@localhost.localdomain>
On Fri, 9 Feb 2007, Tom Tromey wrote:
> Maciej> Indeed, though they are not fatal. Perhaps Makefile.in files
> Maciej> in the affected directories (Makefile.am are OK as
> Maciej> sufficiently new automake will deal with that) could get
> Maciej> updated beforehand? It should not hurt at all.
>
> I think automake 1.10 requires the new autoconf. So, Makefile.ins
> can't be updated first.
Well, adding a definition of the $(datarootdir) variable like this:
datarootdir = @datadir@
datadir = $(datarootdir)
should not require any updates for tools and can then be converted to the
final form of:
datarootdir = @datarootdir@
datadir = @datadir@
for Makefile.in or removed altogether for Makefile.am files once the tools
have been updated. At least it seems to work on my system. :-)
Maciej
next prev parent reply other threads:[~2007-02-13 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070111225346.GA1335@nevyn.them.org>
[not found] ` <20070207193352.GA13757@nevyn.them.org>
[not found] ` <xnr6t1hdvt.fsf@greed.delorie.com>
2007-02-08 22:20 ` Daniel Jacobowitz
2007-02-08 22:30 ` DJ Delorie
2007-02-08 22:38 ` Daniel Jacobowitz
2007-02-08 22:44 ` DJ Delorie
2007-02-08 22:54 ` DJ Delorie
2007-02-09 15:16 ` Daniel Jacobowitz
2007-02-09 15:37 ` Maciej W. Rozycki
2007-02-09 15:39 ` Daniel Jacobowitz
2007-02-09 16:14 ` Maciej W. Rozycki
2007-02-09 16:17 ` Daniel Jacobowitz
2007-02-09 16:33 ` Andreas Schwab
2007-02-09 17:39 ` Maciej W. Rozycki
2007-02-09 17:42 ` Daniel Jacobowitz
2007-02-09 17:53 ` Maciej W. Rozycki
2007-02-09 17:48 ` Steve Ellcey
2007-02-09 20:45 ` Tom Tromey
2007-02-13 9:25 ` Maciej W. Rozycki [this message]
2007-02-13 10:30 ` Andreas Schwab
2007-02-09 16:29 ` Joseph S. Myers
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.LNX.4.64N.0702130909040.31957@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=newlib@sourceware.org \
--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