public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: gcj exception compiling
Date: Thu, 10 Nov 2011 05:53:00 -0000	[thread overview]
Message-ID: <1320904424.3872.59.camel@YAAKOV04> (raw)
In-Reply-To: <4EBB612A.2030104@gmail.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

  reply	other threads:[~2011-11-10  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05 18:13 Kraus Philipp
2011-11-06  1:28 ` Yaakov (Cygwin/X)
2011-11-06 20:16   ` Philipp Kraus
2011-11-07  2:05     ` Yaakov (Cygwin/X)
2011-11-07  6:36       ` Philipp Kraus
2011-11-07 14:12         ` Jon Clugston
2011-11-10  5:18   ` Dave Korn
2011-11-10  5:29     ` Dave Korn
2011-11-10  5:53       ` Yaakov (Cygwin/X) [this message]
2011-11-10  6:07       ` Christopher Faylor

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=1320904424.3872.59.camel@YAAKOV04 \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    /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).