[opensuse-arm] openSUSE:Factory:ARM / aarch64 is now building on native hardware
Hi, for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available. == What changes == If you have packages enabled for building against openSUSE:Factory:ARM, nothing really changes for you. Just that the package will be build on native hardware now instead of using the user mode emulation on x86_64 that we've used before. Specifically, the macro %qemu_user_space_build is no longer set to 1. That said, for now it would still be a good idea to keep the %qemu_user_space_builds sections in your spec file as they are, as we still use user mode building for armv6 and for older targets (e.g. openSUSE 13.2). == What if I want to build locally? == Due to the use of user-mode qemu emulation, it was previously possible to build locally for aarch64 on a x86_64 host by running "osc build <project> <package> standard aarch64". This does not work anymore, since the "standard" repository is now requiring native aarch64 hardware. You can still build with user mode emulation by using this command: "osc build <project, e.g. openSUSE:Factory:ARM> <package> qemu aarch64". Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Can this hardware be used to build armv7 on it like x86_64 and i586? 28.04.2015 09:53, Dirk Müller пишет:
Hi,
for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available.
== What changes ==
If you have packages enabled for building against openSUSE:Factory:ARM, nothing really changes for you. Just that the package will be build on native hardware now instead of using the user mode emulation on x86_64 that we've used before. Specifically, the macro %qemu_user_space_build is no longer set to 1. That said, for now it would still be a good idea to keep the %qemu_user_space_builds sections in your spec file as they are, as we still use user mode building for armv6 and for older targets (e.g. openSUSE 13.2).
== What if I want to build locally? ==
Due to the use of user-mode qemu emulation, it was previously possible to build locally for aarch64 on a x86_64 host by running "osc build <project> <package> standard aarch64". This does not work anymore, since the "standard" repository is now requiring native aarch64 hardware. You can still build with user mode emulation by using this command:
"osc build <project, e.g. openSUSE:Factory:ARM> <package> qemu aarch64".
Greetings, Dirk
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 28.04.15 09:37, Matwey V. Kornilov wrote:
Hi,
Can this hardware be used to build armv7 on it like x86_64 and i586?
In theory yes, in practice not today. We only have 4 systems - throwing armv7 at them would completely overload the cluster, resulting in much slower builds for aarch64. Also there are a few technical hurdles. While the aarch64 kernel can execute armv7 code, it shows itself as "armv8l" in uname, breaking configure scripts, rpm, etc. Also we configure our aarch64 kernel with 64kb PAGE_SIZE which means you can only execute Factory and above armv7l binaries on it - 13.2 and below use 32kb alignment for binaries. So what we'd eventually need is an armv7l kernel-obs-build that runs a native armv7l kernel on an aarch64 worker. But I'd prefer to only investigate that deeper once we have enough build power to actually make use of it ;). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Matwey,
Can this hardware be used to build armv7 on it like x86_64 and i586?
No, we kept this separate for now. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Dirk Müller schrieb:
for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available.
Thanks to that aarch64 now builds in reasonable time and the automatic snapshoting mechanism that turns Factory into Tumbleweed has a chance to actually work. However, to determine whether a snapshot can be created the tools have to look at the overall state of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the "local" arch used for image building. So I'm wondering whether it would make sense to split aarch64 from armv6/7 and use a separate project? Alternatively we could use a frozen project link instead of using always the latest Factory packagse. That would slow down aarch64 considerably though. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 28 April 2015 at 03:30, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Dirk Müller schrieb:
for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available.
Thanks to that aarch64 now builds in reasonable time and the automatic snapshoting mechanism that turns Factory into Tumbleweed has a chance to actually work. However, to determine whether a snapshot can be created the tools have to look at the overall state of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the "local" arch used for image building. So I'm wondering whether it would make sense to split aarch64 from armv6/7 and use a separate project? Alternatively we could use a frozen project link instead of using always the latest Factory packagse. That would slow down aarch64 considerably though.
With the evidence provided, I would vote for splitting aarch64 from armv6/7. Having at least one of the ARM architectures running a full Tumbleweed would be great. Regards, Andy
cu Ludwig
-- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 28.04.2015 um 10:30 schrieb Ludwig Nussel <ludwig.nussel@suse.de>:
Dirk Müller schrieb:
for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available.
Thanks to that aarch64 now builds in reasonable time and the automatic snapshoting mechanism that turns Factory into Tumbleweed has a chance to actually work. However, to determine whether a snapshot can be created the tools have to look at the overall state of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the "local" arch used for image building. So I'm wondering whether it would make sense to split aarch64 from armv6/7 and use a separate project? Alternatively we could use a frozen project link instead of using always the latest Factory packagse. That would slow down aarch64 considerably though.
Let's try to see whether we can get more hardware first. If we can at least get armv7 to good speeds as well we could move armv6 out into a separate project as the oddball instead. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Ludwig,
of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the "local" arch used for image building.
armv7 isn't that slow, its just armv6. anyway, where is that restriction of "overall settlement" coming from? the OBS is not waiting for armv7 to finish in order to publish aarch64 (or waiting for armv6 for that matter). They're not in the same relsync group so to speak. Can you name which tool is waiting for this where? I'd love to investigate and fix that part. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Dirk Müller schrieb:
of the project and check if everything has settled. Due to armv6 and 7 beeing slow that almost never happens for the "local" arch used for image building.
armv7 isn't that slow, its just armv6. anyway, where is that restriction of "overall settlement" coming from? the OBS is not waiting for armv7 to finish in order to publish aarch64 (or waiting for armv6 for that matter). They're not in the same relsync group so to speak.
Can you name which tool is waiting for this where? I'd love to investigate and fix that part.
https://github.com/openSUSE/osc-plugin-factory/blob/master/totest-manager.py... cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Alexander Graf -
Andrew Wafaa -
Dirk Müller -
Ludwig Nussel -
Matwey V. Kornilov