blob: c33865c9ff571ae151b413c21fb4c9519574bad4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
no member named '__sem_otime_high' in 'semid_ds'
Looks like a glibc and kernel desync. Needs to get investigated.
```
now stuck in
../Source/Tests/LinuxSyscalls/x64/Types.h:83:11: error: no member named '__sem_otime_high' in 'semid_ds'
buf.__sem_otime_high = sem_otime_high;
Loads of these?
skmp@mangie:~/projects/FEX/build$ uname -a
Linux mangie.hosts.hn.nilware.io 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
skmp@mangie:~/projects/FEX/build$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
uhoh
#ifndef _M_ARM_64
// AArch64 doesn't have these legacy high variables
buf.__sem_otime_high = sem_otime_high;
buf.__sem_ctime_high = sem_ctime_high;
#endif
apparently, x86_64 doesn't either?
yes
those ifdefs seem broken
Sonicadvance1 — Today at 4:33 AM
Create an issue report about it. Will need to double check the kernel interface and see if this is a mismatch between glibc and kernel
```
|