libseccomp-golang: BUG: mismatched types C.uint32_t and C.uint on older gcc versions
root@meihuabo:~/goWorkspace/src/github.com/seccomp/libseccomp-golang# go install
# github.com/seccomp/libseccomp-golang
./seccomp_internal.go:298: invalid operation: in.toNative() == *_Cvar_C_ARCH_BAD (mismatched types C.uint32_t and C.uint)
./seccomp_internal.go:328: invalid case *_Cvar_C_ARCH_X86 in switch on a (mismatched types C.uint and C.uint32_t)
./seccomp_internal.go:330: invalid case *_Cvar_C_ARCH_X86_64 in switch on a (mismatched types C.uint and C.uint32_t)
./seccomp_internal.go:332: invalid case *_Cvar_C_ARCH_X32 in switch on a (mismatched types C.uint and C.uint32_t)
./seccomp_internal.go:334: invalid case *_Cvar_C_ARCH_ARM in switch on a (mismatched types C.uint and C.uint32_t)
./seccomp_internal.go:336: invalid case *_Cvar_C_ARCH_NATIVE in switch on a (mismatched types C.uint and C.uint32_t)
./seccomp_internal.go:338: invalid case *_Cvar_C_ARCH_AARCH64 in switch on a (mismatched types C.uint and C.uint32_t)
root@AY14052923334089220fZ:/mydata/goWorkspace/gotest/src/github.com/seccomp/libseccomp-golang# nt and C.uint32_t)
server info:
Ubuntu 12.04.5 LTS \n \l
Linux meihuabo 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15 04:01:04
go version go1.4.1 linux/amd64
issue in runc mismatched types C.uint32_t and C.uint
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 16 (12 by maintainers)
Commits related to this issue
- doc: document some minimal dependency versions See GH issue #2 for more information: * https://github.com/seccomp/libseccomp-golang/issues/2 Suggested-by: Thordur Bjornsson <thorduri@secnorth.net>... — committed to seccomp/libseccomp-golang by pcmoore 8 years ago
- README: rm go/gcc version warning Those were added based on the discussion in https://github.com/seccomp/libseccomp-golang/issues/2. Nowadays, though, it seems highly unlikely someone will use golan... — committed to kolyshkin/libseccomp-golang by kolyshkin 3 years ago
- README: rm go/gcc version warning Those were added based on the discussion in https://github.com/seccomp/libseccomp-golang/issues/2. Nowadays, though, it seems highly unlikely someone will use golan... — committed to kolyshkin/libseccomp-golang by kolyshkin 3 years ago
- README: rm go/gcc version warning Those were added based on the discussion in https://github.com/seccomp/libseccomp-golang/issues/2. Nowadays, though, it seems highly unlikely someone will use golan... — committed to pcmoore/misc-libseccomp_golang by kolyshkin 3 years ago
- README: rm go/gcc version warning Those were added based on the discussion in https://github.com/seccomp/libseccomp-golang/issues/2. Nowadays, though, it seems highly unlikely someone will use golan... — committed to pcmoore/misc-libseccomp_golang by kolyshkin 3 years ago
- README: rm go/gcc version warning Those were added based on the discussion in https://github.com/seccomp/libseccomp-golang/issues/2. Nowadays, though, it seems highly unlikely someone will use golan... — committed to pcmoore/misc-libseccomp_golang by kolyshkin 3 years ago
@thorduri I hope you don’t mind, I went ahead and added some text to the README via ab55783446ad1ca5c740040f73ee629fe113521e, does this look okay to you?