X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_GC X-Spam-Check-By: sourceware.org Subject: Re: gcj exception compiling From: "Yaakov (Cygwin/X)" To: cygwin Date: Wed, 09 Nov 2011 23:53:42 -0600 In-Reply-To: <4EBB612A.2030104@gmail.com> References: <3E1FD932-EE66-4151-A2B4-026F1D6FA7F0@flashpixx.de> <1320542893.7860.7.camel@YAAKOV04> <4EBB5E84.9060101@gmail.com> <4EBB612A.2030104@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Message-ID: <1320904424.3872.59.camel@YAAKOV04> Mime-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, 2011-11-10 at 05:29 +0000, Dave Korn wrote: > *Four* things to remember for next build: remove ecj dependency, change > libgcj9 -> 11, add missing libmpfr4, and restore the missing download_ecj.sh > script. I wasn't expecting some kind of a Spanish Inquisition ...... I keep all the build files for a package in a persistent, version-controlled directory (one dir per source package) so that whenever I come to change or update a package, the files are all ready to go. Fixes like these could be made now to your local copy so that you don't forget when you next update the package. As for ecj, I'm afraid that was my fault; I have a package in Ports as part of the Java stack, so my gcc4-java worked OOTB. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple