I have a laptop with a dead motherboard - I was wondering if it might be
possible to install an ARM5 motherboard in it for testing (I don't need
it to be portable anymore) so I can reuse the keyboard, screen and HD?
(as well as test out F11 on ARM).
GPO Box 3411
Sydney NSW 2001
Got The X-server and Gnome Desktop to build on ARM. Attaching
screenshots of an ARM board running Gnome! (yay!)
The packages needed for X and Gnome aren't in the repo yet. Hopefully,
I'll mash out a repo this weekend.
I plan to add arm-toolchain into Fedora and encountered a difficulty -
how to properly name the package? From what I found in the Internets,
the cross-toolchains *often* named with the following prefix:
However sometimes they named differently (arm-none-eabi-,
arm-uclinuxeabi-, etc). Some cross-compilers already included into
Fedora, and their packages naming schemes are also different - some
examples of prefixes are arm-gp2x-linux-, avr-, msp430-, spu-
(mingw32 differs from others because it, at least, implies target OS
I'm sure, it's time to create unified rules for packaging of
cross-toolchains, but right now I'm asking you for help in proper
naming of it. Should we name it as <arch>-<vendor>-<operating
system>-<libc>-gcc or should we use some other naming schemes? What
values should be used for <vendor> - "fedora" maybe? O should we
simply drop this field ("unknown")?
With best regards!
Fedora-11 ARM Repositories are now available!
Details: built for ARMv5 EABI, soft-float, little endian.
Currently there are packages from three yum groups: Base, Core
A yum-enabled pre-built root filesystem is available along with
instructions for working with known platforms (currently Qemu,
The Fedora/ARM architecture wiki page has more information:
Do let us know any issues that you may face, or any additional
Fedora Packages/Groups that you would like to have in the
Our next steps include a) making the package repository much more
complete by building packages from more package groups (starting
with the Gnome Desktop group) b) tracking f11-updates for these packages.
Seems that absence of gcj is the most significant difference between
Fedora-ARM and main Fedora repository. What issues prevents gcj from
being built? While digging spec-file for GCC, I found %bootstrap_java
condition - maybe we should simply turn it on? :)
With best regards!