From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: frysk on fedora rawhide
Date: Wed, 14 Mar 2007 13:56:00 -0000 [thread overview]
Message-ID: <1173880583.4302.21.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1173791331.4262.19.camel@dijkstra.wildebeest.org>
FYI. Stepan rebuild a frysk package from yesterdays CVS against the
latest tools on Fedora rawhide/development.
And the following packages just entered the repository:
libgcj 4.1.2-4
frysk[-gnome|-devel] 0.0.1.2007.03.13.rh1-1.fc7
eclipse-ecj 1:3.2.2-3.fc7
They seem to work fine together (frysk runs from the package, and
builds with the new gcj and eclipse-ecj from CVS with --disable-werror).
If you have an old version of libgcj installed try yum upgrade libgcj
first before yum installing frysk and only then install eclipse-ecj
(note that yum dependency checking for eclipse-ecj takes forever so be
patient - 10 minutes on my system), otherwise you will get some
transaction check failures with old and new i386/x86_64 libgcj fighting
over files. Note that the new eclipse-ecj/gcj combo support -Wall now
and that gives us lots and lots of warnings to go through :)
Cheers,
Mark
parent reply other threads:[~2007-03-14 13:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1173791331.4262.19.camel@dijkstra.wildebeest.org>]
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=1173880583.4302.21.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.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).