ARM Tools
by nihed mbarek
Hello,
I'm new here and i want to have information about how to begin in this area.
I want to have links of documentations and if possible repo for fedora 7
that regroups packages for arm developping.
Thanks.
--
M'BAREK Med Nihed,
Fedora Ambassador, TUNISIA, Northern Africa
16 years, 9 months
FW: gcj-4.2 bootstrap on arm needed
by Manas Saksena
FYI.
This is from debian-arm mailing list. I guess this means that we should
be able to get gcc building with gcj -- or am I missing something?
Manas
Matthias Klose wrote:
> Please try building gcj-4.2 on arm manually (using gcj-4.1 packages
> from etch); all arm patches from Andrew Hailey are now integrated in
> the gcj-4.2 package. Before gcc-4.2-source is installable, just
> ignore the build-dependency and copy the gcc tarball from the gcc-4.2
> source into the gcj-4.2 directory.
>
> Matthias
16 years, 9 months
arm port status
by Lennert Buytenhek
Hi all,
Feedback on the gcc ARM patches I submitted (bug 246800) seemed mostly
positive, apart from the patch that disables building objc/java on ARM
(which is necessary since upstream gcc doesn't support those on EABI
ARM yet.) Jakub didn't agree with it on the basis that many things in
Fedora depend on it. Since this is only a minor spec file change, I'll
probably just keep carrying this separately until the necessary bits
get implemented upstream.
As to glibc (bug 246801): Jakub suggested that, considering that the
ARM support for glibc support lives in a separate upstream 'ports'
sub-repository, to build ARM glibc from a separate source package.
I'll look into getting a glibc-ports source package into Fedora.
Almost all rpm diffs have been merged at this point as well. The
only unfixed issue was how to handle -gnueabi in our target triple,
but I've submitted a patch for that that will hopefully suffice.
Most of the other diffs I've submitted (which mostly only add %{arm}
to ExclusiveArch:) are still sitting in bugzilla untouched. Maybe
I'll just have to start offering people $10 per reviewed patch or
something like that..
(The ARM tracker bug is here:)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245418
cheers,
Lennert
16 years, 10 months
Cross-Compilers for ARM
by Manas Saksena
Now that we have a substantial chunk of the packages built for ARM,
I think it would be interesting to see if we can build a cross-compiler
that is aligned with the native toolchain. And, at this stage, we dont
need to worry about bootstrapping gcc since we already have a glibc
available.
I think it would be useful to bundle a cross-compiler/debugger toolchain
with the release even if all the other packages are built natively. As
much of the development tends to be with the kernel and the
applications, the cross-compiler is virtually a necessity for those.
Is anyone interested in working on that?
Manas
16 years, 10 months
arm port status
by Lennert Buytenhek
I didn't get any feedback from the relevant maintainers, so I
decided to just go ahead and submit the ARM gcc and glibc package
diffs to BZ:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246800
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246801
I've included a backport of the upstream fix for gcc PR30486, which
fixes the ARM EABI fortran bootstrap, so we now have gcc-gfortran
packages as well. It's not very likely that people would want to
use ARM systems for their nuclear weapons simulations, but at least
it brings the selection of available packages closer to what's in
x86 Fedora, which is a Good Thing.
Also, since our ARM changes are in rpm 4.4.2.1-rc1, I've BZ'd that
as well:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246803
I'm not entirely sure what it takes to get someone to look at our
BZs. We might have to start bribing package maintainers (say, with
large quantities of various alcoholic beverages) at some point.
Looking beyond getting the ARM diffs into Fedora, I'm very
interested in things like footprint optimisation, cross compiling,
and such.
I posted initial diffs for a cross-gcc package from Fedora sources
to fedora-devel-list@ recently. A set of i386 RPMS for an arm
cross-toolchain is available here:
http://www.wantstofly.org/~buytenh/cross/
It's still somewhat experimental (for example, I'm not entirely
satisfied yet about the sysroot handling), but it works well enough
to cross-compile an ARM kernel, and it manages to cross-compile a
native ARM gcc (i.e. build=i386 host=arm target=arm cross build) as
well. Eventually, we'd like to be able to cross-build entire RPMS.
Also, I've started collecting patches to break e.g. the python-
dependent parts of packages off into separate subpackages, and
patches to allow rebuilding packages with less dependencies (e.g.
to not pull in libselinux), etc. Packaging things like eglibc
and dropbear is also on the list.
Since a lot of these patches aren't likely to go into Fedora
soon, I'm looking into a way of making maintaining sets of diffs
against Fedora sources easier. In essence, to have local branches
of the distro, e.g. a "cross branch" with diffs to make various
packages cross-compile-able, a "footprint branch" with diffs to
reduce package footprint/dependencies, and such. (Judging by the
uptake of the ARM diffs so far, we'll probably need an "ARM branch"
as well.)
I've played around a bit with creating minimal root filesystems
(in the 4-8 MiB range, for use as the flash image in your wireless
access point / VoIP gateway / ADSL router.) Manually creating a 8
MiB minimal ARM filesystem based on the ARM RPMS that we carry
actually isn't all that hard. Doing it in an automated and
repeatable way is somewhat harder. Most of the work to be done in
this area is in the tools, and should probably tie in closely with
revisor, pilgrim, and such.
16 years, 10 months
Running Fedora ARM on QEMU
by Manas Saksena
I have posted instructions on how to run Fedora-ARM on QEMU
at:
http://fedoraproject.org/wiki/ARM/HowToQemu
So if you are interested in trying it out and don't have
suitable hardware -- then this should make it easy.
And, if you do, please clean up the how to, if something is
not clear etc. Or, extend it (for e.g., to run QEMU using
QEMU's user-mode networking).
Regards,
Manas
16 years, 10 months
Fedora ARM and Devices
by Peter Robinson
Hi All,
I've got a couple of different ARM devices that I would like to
eventually get Fedora running on so I just thought I'd post to the
list and say Hi. I've been a RHL./Fedora user since 1995 or RHL-4.0...
so a little while. I've got reasonable packaging skills, debug etc but
never done much coding.
I have 3 (well 4 actually I think) that either run linux already or
can run Linux. They are:
- Nokia 770
- O2 XDA (or a HTC Wallaby -
http://wiki.xda-developers.com/index.php?pagename=Wallaby)
- A router (can't remember make/model but I'm sure its ARM based)
- A Sarotech 3.5 ABIGS 570HD
(http://www.sarotech.com/english/cgi/pd.cgi?cmd=view&rno=19) - already
run Linux but not sure if a Sigma Designs EM8621 is an ARM variant or
something else)
I was also wonder whether ScratchBox (http://www.scratchbox.org/) as
used by Maemo to cross compile stuff would be an appropriate tool for
cross compiling.
Anyway first on the list to play with will be the Wallaby as its not
currently in general use.
I've found the Fedora ARM wiki http://fedoraproject.org/wiki/ARM and
there's a general get Linux booting howto for it
(http://wiki.xda-developers.com/index.php?pagename=WallabyLinuxBooting).
Is there a general "this is roughly how to get your dev booting Fedora
ARM but your milage may vary dependant on your device" howto?
Cheers,
Pete
16 years, 10 months
