Support arm64/aarch64 architecture

[Felix Bünemann]

It would be great if the PPA could be updated to include arm64 (aarch64) builds.

This should work fine for Ruby 1.9.3 and later on Trusty and later, I had no problems building those with RVM in Docker on an arm64 M1 Mac.

Since Trusty is already EOL and Xenial is EOL in April it would probably be fine to just support arm64 for Bionic and Focal.

I would be happy to test packages on arm64 hardware or help out with required changes.

Regards, Felix

[John Leach]

Hi Felix,

I've enabled the arch on the PPAs and agree we should just target Bionic and Focal, though we might be able to squeeze in some Xenial builds before the EOL. We can't commit to continuing support for them, but if they build without any extra work then it's worth a shot.

I think I just need to make a new release for each ruby version (just a version release bump should do it). I'll see if I can get around to that soon.

Our builds run the full ruby test suite though (with a few exclusions that don't run properly in the launch build environment) - did you run the tests against the RVM builds? If the tests fail during the launchpad build, the packages won't be published. If you could run them and flush out any issues, that would be great.

Thanks,

John.

--
You received this message because you are subscribed to the Google Groups "Brightbox Ruby Ubuntu Packaging" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brightbox-ruby-ubuntu...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/brightbox-ruby-ubuntu-packaging/4954683c-ca43-4a84-a01c-8256cbf375b0n%40googlegroups.com.

--

https://www.brightbox.com

[Jeremy Beker]

Just curious if there is a status on adding arm64? 

I am looking specifically for ruby2.6 on Focal, but the only package that seems to be available is ruby2.6-doc.

Thanks so much!

-Jeremy

On Wednesday, February 24, 2021 at 12:26:40 PM UTC-5 jo...@brightbox.com wrote:

Hi Felix,

I've enabled the arch on the PPAs and agree we should just target Bionic and Focal, though we might be able to squeeze in some Xenial builds before the EOL. We can't commit to continuing support for them, but if they build without any extra work then it's worth a shot.

I think I just need to make a new release for each ruby version (just a version release bump should do it). I'll see if I can get around to that soon.

Our builds run the full ruby test suite though (with a few exclusions that don't run properly in the launch build environment) - did you run the tests against the RVM builds? If the tests fail during the launchpad build, the packages won't be published. If you could run them and flush out any issues, that would be great.

Thanks,

John.

Jeremy Beker Principal Software Engineer 122 West 26th Street, 8th Floor, New York City 10001 www.food52.com More Food52, Sent Right To You

[Felix Bünemann]

Hi John,

I took the time to build all the ruby-ng-experimental rubies on Xenial, Bionic and Focal for arm64.

On Xenial ruby1.9.1 and ruby2.0 failed to build, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 were fine.

On Bionic ruby2.2, 2.3, 2.4, 2.5, 2.6 worked, older rubies have a wrong libssl dependency (1.1 vs 1.0) and also fail on intel.

On Focal ruby2.4, 2.5, 2.6, 2.7 worked.

Since the only build failures are old versions I think it is fine to enable for Xenial (if still active), Bionic, Focal.

Maybe enable them with the currently missing patch releases 2.7.3, 2.6.7, 2.5.9?

There's also no package for ruby3.0, which would be nice to have at least on Focal.

Regards, Felix