Le 28/01/2013 14:36, Adrian Schröter a écrit :
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we
could store all our patches for AArch64.
What do you think about it?
Yes, but lets not do the mistake to store them there
to long. They should get
submitted to standard factory as soon as possible (maybe just ensuring that they
harm not other architectures :)
Ok. What would be the policy?
For example, I can build the "rpm" package without selinux support since it is
not yet available. Is it ok to add patches to Factory to disable selinux for aarch64?
Then, "autoreconf -fi" fails with an obscure reason. So, I workaround it with
"autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept
this kind of workaround.
> Le 15/01/2013 10:46, Guillaume Gardet a écrit :
>> First usefull infos are here:
>> Le 14/01/2013 16:50, Guillaume Gardet a écrit :
>>> I would like to make a wiki page about AArch64 (armv8) to list all things we
must do for AArch64 in openSUSE.
>>> A page name like openSUSE:AArch64 looks good to me. Any objection?
>>> I have already some informations about AArch64 build but nothing on what is
needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to
start building AArch64 packages?
>>> I guess we must have a minimal rootfs with some tools? Or maybe just
>>> I already tested my own rootfs (built with the buildroot tool).
>>> I used :
>>> * a bootimg:
>>> * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin
>>> * Foundation_v8 (sort of qemu but seems to not be redistribuable)
>>> * A custom rootfs (I built using buildroot. See: buildroot.net
>>> I built my own image with fdisk and files listed above and got it running:
>>> Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img
>>> So, what would be the next step?
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org