You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Debian I maintain 2 packages which uses host_machine.cpu_family() to create configuration files and this causes problems on armel and armhf architectures. Because they both have cpu_family as arm and this creates conflicts if you tried to install both packages simultaneously. My first thought was to just use host_machine.cpu() but maybe there is more robust way?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In Debian I maintain 2 packages which uses
host_machine.cpu_family()
to create configuration files and this causes problems on armel and armhf architectures. Because they both have cpu_family asarm
and this creates conflicts if you tried to install both packages simultaneously. My first thought was to just usehost_machine.cpu()
but maybe there is more robust way?Theses 2 packages are:
https://github.com/flightlessmango/MangoHud/blob/10479eb59aa6c1c92af9d2afca3e33c5a17d875b/src/meson.build#L330
https://github.com/ValveSoftware/gamescope/blob/1faf7acd90f960b8e6c816bfea15f699b70527f9/layer/meson.build#L14
Beta Was this translation helpful? Give feedback.
All reactions