After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 792338 - meson, autotools: figure out if mem barrier is needed for arm64 host variant aarch64
meson, autotools: figure out if mem barrier is needed for arm64 host variant ...
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: build
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2018-01-08 18:46 UTC by Marc Micalizzi
Modified: 2018-05-24 20:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
meson: change error() to warning() when checking if membarrier is needed (1.12 KB, patch)
2018-01-08 18:56 UTC, Tim-Philipp Müller 		committed Details | Review

Description Marc Micalizzi 2018-01-08 18:46:46 UTC 
arm64 can be reffered to as aarch64, and when it is glib can't build through meson without changing meson.build as aarch64 doesn't start with 'arm'

Meson encountered an error in file meson.build, line 1267, column 2: 
Error encountered: Unknown host cpu: aarch64
In master it's on line 1288
Comment 1 Tim-Philipp Müller 2018-01-08 18:56:19 UTC 
Created attachment 366508 [details] [review]
meson: change error() to warning() when checking if membarrier is needed

If we don't know the exact architecture that's not fatal, might just be suboptimal, same as with autotools.

-- 

We should probably figure out into which category aarch64 falls and then add that in both the autotools build and the meson build. The meson checks just mirror the autotools ones.
Comment 2 Tim-Philipp Müller 2018-01-10 16:09:14 UTC 
pushed the build fix, retitling for accounting properly for the arch.
Comment 3 GNOME Infrastructure Team 2018-05-24 20:08:00 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1323.