public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Nix <nix@esperi.org.uk>
Cc: java@gcc.gnu.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [RFC PATCH] make libgcj_bc prims symbol sizes correct
Date: Tue, 18 Aug 2009 08:42:00 -0000	[thread overview]
Message-ID: <4A8A695D.7020607@redhat.com> (raw)
In-Reply-To: <87r5va3zn0.fsf@spindle.srvr.nix>

Nix wrote:
> On 17 Aug 2009, Andrew Haley spake thusly:
>> Please let me know if this works for you.
> 
> Doesn't apply against 4.4-branch, but the fix is trivial (no
> @ATOMICSPEC@ in libgcj.spec.in), so I did that.
> 
> Unfortunately you touched configure.ac and Makefile.am both, and I hit a
> wall trying to convince autoreconf to play along. GCC is famously picky
> about the exact versions of the autotools in use, so I installed
> automake-1.9.6 and autoconf-2.59 (libtool was fine), which were used to
> generate the stuff in libjava/, but then got this:
> 
> spindle 564 /usr/src/gcc/gcc/libjava% AUTOCONF=autoconf-2.59 AUTOHEADER=autoheader-2.59 AUTOMAKE=automake-1.9 autoreconf-2.59 -fiv
> autoreconf-2.59: Entering directory `.'
> autoreconf-2.59: configure.ac: not using Gettext
> autoreconf-2.59: running: aclocal --force -I . -I .. -I ../config -I libltdl
> libltdl/acinclude.m4:6188: the serial number must appear before any macro definition
> ../config/override.m4:24: error: m4_copy: won't overwrite defined macro: AC_PREREQ
> ../config/override.m4:24: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: autom4te failed with exit status: 1
> autoreconf-2.59: aclocal failed with exit status: 1
> 
> (I tried at the top level too: same result.)
> 
> I do not claim to be clueless at autoconfery, but this error has me
> stumped. What magic invocation do I need to regenerate these things?
> This error isn't happening at the macro that's supposed to prevent
> regeneration with th ewrong autoconf version, but at the one above it...

In my experience the only thing that works is to add autoconf and
automake to the head of your PATH and invoke them as "autoconf" and
"automake".

Andrew.

  reply	other threads:[~2009-08-18  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15  0:08 Nix
2009-08-15  8:56 ` Andrew Haley
2009-08-15  9:34   ` Andrew Haley
2009-08-15 19:13     ` Nix
2009-08-17  9:54       ` Andrew Haley
2009-08-17 17:24         ` Andrew Haley
2009-08-17 21:21           ` Nix
2009-08-18  8:42             ` Andrew Haley [this message]
2009-08-18 22:25               ` Nix

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=4A8A695D.7020607@redhat.com \
    --to=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=nix@esperi.org.uk \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).