public inbox for
 help / color / mirror / Atom feed
From: Matthias Klose <>
To: Mark Wielaard <>
Cc:, GCC Java <>
Subject: Re: tagging classpath for GCC import
Date: Mon, 03 Dec 2012 07:15:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am 03.12.2012 02:15, schrieb Matthias Klose:
> Further, it looks like classpath did bump the requirement on autoconf to 2.69,
> and didn't even bother to document that (m4/iconv.m4 requires macros only found
> in 2.69).  classpath itself pretends to require 2.63.
> GCC has 2.64, and won't change for the next release. Any hint how to handle this
> properly?

no, looks like the iconv.m4 file was included without including lib-ld.m4,
lib-link.m4 and lib-prefix.m4, now copied from gettext, and the configure
scripts can be regenerated.

  reply	other threads:[~2012-12-03  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2012-12-03  1:15   ` Matthias Klose
2012-12-03  7:15     ` Matthias Klose [this message]
2012-12-03  9:05     ` Mark Wielaard
2012-12-03  9:29       ` [cp-patches] " Andrew Haley
2012-12-03 10:04         ` Mark Wielaard
2012-12-03 10:44           ` Pekka Enberg
2012-12-03 12:31             ` Mark Wielaard
2012-12-03 15:00     ` Andrew Hughes

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).