[opensuse-factory] Bootstrapping openSUSE for a new architecture
Hello! I have a question out of curiosity: How difficult is it to bootstrap openSUSE for a new architecture, let's say sparc64? I'm not so much asking about the technical details as this is something I have done already multiple times in Debian. But I'm rather interested to know how difficult it is to get a new port added to OBS. Is this something that involves jumping through many hoops or is it a matter of asking a few people and adding the new architecture to OBS and setting up some build machines? For reference, in Debian it's a matter of creating a folder for a specific architecture on ftp.ports.debian.org, setting up the build machines (buildds) and adding the new architecture to the build database (wanna-build). The server side changes (FTP and wanna-build) require talking to one of Debian's sys admins (DSA) and setting up the buildd is normally done by the porter. Bootstrapping a Linux distribution for a new architecture is interesting because it helps finding portability bugs and also allows one to learn how the distribution is actually fit together. I learned a lot about Debian when doing that in Debian. So it would be a very interesting exercise in openSUSE as well. Thanks, Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2018-02-16 23:47, John Paul Adrian Glaubitz wrote:
Hello!
I have a question out of curiosity: How difficult is it to bootstrap openSUSE for a new architecture, let's say sparc64?
Easy enough - it's been done before by none other than me (in 2012), with OBS. The thing ran and runs native, suffice to say that openSUSE 11.2 is dated by now. RPMS copied to http://blackares.de/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 16.02.2018 um 23:47 schrieb John Paul Adrian Glaubitz:
Hello!
I have a question out of curiosity: How difficult is it to bootstrap openSUSE for a new architecture, let's say sparc64?
I'm not so much asking about the technical details as this is something I have done already multiple times in Debian. But I'm rather interested to know how difficult it is to get a new port added to OBS.
Is this something that involves jumping through many hoops or is it a matter of asking a few people and adding the new architecture to OBS and setting up some build machines?
See how Andreas added riscv64 support: https://github.com/openSUSE/obs-build/pull/428 https://github.com/openSUSE/open-build-service/pull/4415 Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi! On 02/17/2018 08:11 AM, Stephan Kulow wrote:
Is this something that involves jumping through many hoops or is it a matter of asking a few people and adding the new architecture to OBS and setting up some build machines?
See how Andreas added riscv64 support: https://github.com/openSUSE/obs-build/pull/428 https://github.com/openSUSE/open-build-service/pull/4415
Ok, so we have one Sun Fire T2000 server in Debian which is idling because we currently have an overcapacity of SPARC hardware with a SPARC-T5 being our main machine. All machines run Debian unstable with a current toolchain and kernel. Would anyone be interested in setting up the free T2000 as a build instance for OBS? I would be really interested in learning the process and building openSUSE on sparc64 would help finding missing patches things which we haven't upstreamed yet. sparc64 is an interesting candidate because the port is relatively mature these days with even support for modern languages like Rust. There is also a Go port by Oracle for sparc64, but that is currently not merged because of Google's strict requirements to add support for a new architecture. Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Feb 16 2018, John Paul Adrian Glaubitz
I have a question out of curiosity: How difficult is it to bootstrap openSUSE for a new architecture, let's say sparc64?
It took me about a week to manually build the necessary bootstrap packages for riscv64, then another week to bootstrap it in a private OBS instance. The result can now be seen in https://build.opensuse.org/project/show/openSUSE:Factory:RISCV. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/19/2018 09:58 AM, Andreas Schwab wrote:
It took me about a week to manually build the necessary bootstrap packages for riscv64, then another week to bootstrap it in a private OBS instance. The result can now be seen in https://build.opensuse.org/project/show/openSUSE:Factory:RISCV.
Very cool. Is the initial bootstrap done via cross-compilation or did you use the existing Fedora bootstrap for riscv64 for that matter? On Debian there is a very useful project called "rebootstrap" which will automatically bootstrap an almost complete Debian base system (it's still missing Perl which is apparently hard to cross-compile automatically) from scratch. It produces around 650 binary packages and requires a single command invocation. It would be nice to have something like that for openSUSE. Also, once I have compiled the minimal package set for openSUSE, what is the usual way to get the packages uploaded onto the FTP servers? On Debian, I have to sign the .changes file of each package with my Debian GPG key and then I can upload the package to the Debian Ports FTP servers. Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Feb 19 2018, John Paul Adrian Glaubitz
Very cool. Is the initial bootstrap done via cross-compilation or did you use the existing Fedora bootstrap for riscv64 for that matter?
I started from scratch, the Fedora packages were based on an old version of the ABI.
Also, once I have compiled the minimal package set for openSUSE, what is the usual way to get the packages uploaded onto the FTP servers? On Debian, I have to sign the .changes file of each package with my Debian GPG key and then I can upload the package to the Debian Ports FTP servers.
Publishing on download.o.o is done automatically from build.o.o, but only for package that are built there. Our primary OBS instance doesn't allow arbitrary build workers. But it is very easy to set up your own OBS instance, hook up any build worker you have in your closet, and let it build your packages. (Packman is a well known public OBS instance that works that way.) Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andreas Schwab -
Jan Engelhardt -
John Paul Adrian Glaubitz -
Stephan Kulow