Hi all,
I have built a set of experimental (!) Fedora 8/ARM root filesystems, which are currently being uploaded to the /rootfs directory of your favorite Fedora/ARM mirror. When the upload process finishes, they should be available at e.g.:
http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/
There is an F8/ARM yum repo config file available at:
http://ftp.linux.org.uk/pub/linux/arm/fedora/fedora-arm-f8.repo
There are still slightly too many rough edges at this point for me to be able to recommend FC6/ARM users to switch over to F8/ARM, but I hope to have an end-user usable F8/ARM out very soon.
One notable addition is the work that Andrew Haley has been doing on getting gcj (the GNU Java compiler) to work on ARM EABI (thanks!), which means that we have working gcc-java packages in the F8 repository now.
Since this enables building a whole set of packages that we couldn't build before, there is some amount of package building left to be done to fully make use of this, including some bootstrapping work (i.e. there are circular dependencies in the initial set of Java packages.) I _think_ I have the hardest stuff all built[*], but there are still a couple of bits missing.
In particular, to be able to build/use gcc-java, you need to have eclipse-ecj installed, which we don't have available in RPM form yet, as we don't have all eclipse dependencies in RPM form yet. So, to be able to use gcc-java and friends, you'll have to copy /usr/share/java/eclipse-ecj.jar over from an i386 or x86_64 Fedora 8 box for now. This will hopefully also be resolved soon.
cheers, Lennert
[*] Current set of Java packages in the F8/ARM repository: ant, antlr, jakarta-commons-codec, jakarta-commons-collections, jakarta-commons-io, jakarta-commons-lang, jakarta-commons-launcher, jakarta-commons-pool, java-1.5.0-gcj, java_cup, javacc, jdepend, jlex, jline, jrefactory, jsch, jtidy, junit, junit4, jzlib, regexp, sinjdoc, wsdl4j, xml-commons-apis, xml-commons-resolver
On Wed, 2007-12-12 at 21:54 +0100, Lennert Buytenhek wrote:
So, to be able to use gcc-java and friends, you'll have to copy /usr/share/java/eclipse-ecj.jar over from an i386 or x86_64 Fedora 8 box for now.
Why only i386 or x86_64? Does it have to be little-endian?
That seems strange, for a jar file -- although I seem to recall people complaining that Eclipse folks went to great lengths to break Eclipse and make it non-portable...
On Wed, Dec 12, 2007 at 04:10:49PM -0500, David Woodhouse wrote:
So, to be able to use gcc-java and friends, you'll have to copy /usr/share/java/eclipse-ecj.jar over from an i386 or x86_64 Fedora 8 box for now.
Why only i386 or x86_64? Does it have to be little-endian?
I don't think so -- although I haven't tried, I suspect that taking it from another arch that has it built would work as well.
Lennert Buytenhek writes:
In particular, to be able to build/use gcc-java, you need to have eclipse-ecj installed, which we don't have available in RPM form yet, as we don't have all eclipse dependencies in RPM form yet. So, to be able to use gcc-java and friends, you'll have to copy /usr/share/java/eclipse-ecj.jar over from an i386 or x86_64 Fedora 8 box for now. This will hopefully also be resolved soon.
I hope so. In particular, you should see a big performance improvement once a precompiled version of eclipse-ecj is installed.
Andrew.
-
Andrew Haley -
David Woodhouse -
Lennert Buytenhek