public inbox for
 help / color / mirror / Atom feed
From: Andreas Tobler <>
To: Dr Andrew John Hughes <>
Cc: Mark Wielaard <>,,
Subject: Re: classpath configure update?
Date: Mon, 28 Nov 2011 19:33:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 28.11.11 19:38, Dr Andrew John Hughes wrote:
> On 17:45 Mon 28 Nov     , Andreas Tobler wrote:
>> Hi Mark,
>> On 28.11.11 17:39, Mark Wielaard wrote:
>>> On Mon, 2011-11-28 at 09:50 +0100, Andreas Tobler wrote:
>>>> I recently pushed a commit to gcc head and gcc-4.6 to fix the detection
>>>> of FreeBSD-10.
>>>> Now I see that I need to do that for libjava/classpath/configure too.
>>>> My question, how do I do that? Means, can I simply commit the fix to the
>>>> gcc/libjava/classpath and don't care about upstream classpath?
>>>> Or how do I proceed?
>>> Upstream classpath doesn't check in generated files like configure, so
>>> if it is just the generated files, then nothing has to be done. If you
>>> have a patch against then please just post it to
>>> and/or and we take it
>>> from there. For changes that only apply to libjava/gcj there is a
>>> libjava/classpath/ChangeLog.gcj to track those.
>> Well, it is a regenerated configure (which pulls in gcc toplevel
>> libtool.m4 changes) and the config.rpath.
>> For the former I need to dive into cp sources to see how it works. For
>> the latter I guess it is a normal patch.
> configure is only present in gcj's copy of GNU Classpath.  config.rpath will
> need patching in GNU Classpath, so please post a patch to

Ok, will do.

> How does the change to configure persist if you don't change the source

libtool.m4 things get pulled in when running autoconf -I ../../ in 

So for the configure stuff I do not have to care about classpath, only 
for config.rpath.


      reply	other threads:[~2011-11-28 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 16:00 Andreas Tobler
2011-11-28 16:39 ` Mark Wielaard
2011-11-28 16:46   ` Andreas Tobler
2011-11-28 18:39     ` Dr Andrew John Hughes
2011-11-28 19:33       ` Andreas Tobler [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:

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