From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11552 invoked by alias); 28 Nov 2011 16:46:09 -0000 Received: (qmail 11541 invoked by uid 22791); 28 Nov 2011 16:46:07 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.fgznet.ch (HELO smtp.fgznet.ch) (81.92.96.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Nov 2011 16:45:50 +0000 Received: from deuterium.andreas.nets (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id pASGilnr073671; Mon, 28 Nov 2011 17:44:49 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4ED3BAB8.1070909@fgznet.ch> Date: Mon, 28 Nov 2011 16:46:00 -0000 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Mark Wielaard CC: java@gcc.gnu.org, classpath@gnu.org Subject: Re: classpath configure update? References: <4ED34B4D.2070505@fgznet.ch> <1322498361.19629.31.camel@springer.wildebeest.org> In-Reply-To: <1322498361.19629.31.camel@springer.wildebeest.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2011-11/txt/msg00006.txt.bz2 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