From: Andreas Tobler <andreast-list@fgznet.ch>
To: Mark Wielaard <mark@klomp.org>
Cc: java@gcc.gnu.org, classpath@gnu.org
Subject: Re: classpath configure update?
Date: Mon, 28 Nov 2011 16:46:00 -0000 [thread overview]
Message-ID: <4ED3BAB8.1070909@fgznet.ch> (raw)
In-Reply-To: <1322498361.19629.31.camel@springer.wildebeest.org>
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.
>>
>> http://gcc.gnu.org/ml/gcc-cvs/2011-11/msg00886.html
>>
>> 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 configure.ac then please just post it to
> java-patches@gcc.gnu.org and/or classpath-patches@gnu.org 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.
Thanks,
Andreas
next prev parent reply other threads:[~2011-11-28 16:46 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 [this message]
2011-11-28 18:39 ` Dr Andrew John Hughes
2011-11-28 19:33 ` Andreas Tobler
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=4ED3BAB8.1070909@fgznet.ch \
--to=andreast-list@fgznet.ch \
--cc=classpath@gnu.org \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
/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).