View previous topic :: View next topic |
Author |
Message |
Shadow_Fury Apprentice
Joined: 20 Apr 2021 Posts: 180 Location: 11.435765792823453, 143.05926743686274
|
Posted: Thu Aug 15, 2024 4:44 pm Post subject: [resolved] dev-lang/go fails to install |
|
|
as said in title, dev-lang/go fails to install
this is a still-being-installed system
build log
emerge --info '=dev-lang/go-1.22.6::gentoo'
emerge -pqv '=dev-lang/go-1.22.6::gentoo' :
Code: |
[ebuild N ] dev-lang/go-1.22.6 CPU_FLAGS_X86="sse2"
|
the issue is that it is failing it's tests
here\s one example:
Code: |
--- FAIL: TestMSAN (34.38s)
--- FAIL: TestMSAN/msan8 (2.42s)
msan_test.go:84: /var/tmp/portage/dev-lang/go-1.22.6/temp/TestMSAN1208246300/msan8 exited with exit status 1
==10504==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x3dfb59 in msanGoLoop (/var/tmp/portage/dev-lang/go-1.22.6/temp/TestMSAN1208246300/msan8+0x3dfb59)
#1 0x3dfd5c in _cgo_a322d3c7e754_Cfunc_msanGoLoop (/var/tmp/portage/dev-lang/go-1.22.6/temp/TestMSAN1208246300/msan8+0x3dfd5c)
#2 0x3daa23 in runtime.asmcgocall.abi0 /usr/lib/go/src/runtime/asm_amd64.s:918
SUMMARY: MemorySanitizer: use-of-uninitialized-value (/var/tmp/portage/dev-lang/go-1.22.6/temp/TestMSAN1208246300/msan8+0x3dfb59) in msanGoLoop
Exiting
FAIL
|
i'm really not sure why this is happening. any help is appreciated
Last edited by Shadow_Fury on Thu Aug 15, 2024 6:20 pm; edited 1 time in total |
|
Back to top |
|
|
alamahant Advocate
Joined: 23 Mar 2019 Posts: 3916
|
Posted: Thu Aug 15, 2024 5:42 pm Post subject: |
|
|
Please try to compile it with GCC instead of clang. _________________
|
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31256 Location: here
|
Posted: Thu Aug 15, 2024 6:00 pm Post subject: |
|
|
Upstream bug, _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Shadow_Fury Apprentice
Joined: 20 Apr 2021 Posts: 180 Location: 11.435765792823453, 143.05926743686274
|
Posted: Thu Aug 15, 2024 6:20 pm Post subject: |
|
|
thank you.
it seems the bug has been fixed upstream , and the changes are on the master git. i just need to wait for golang to release a new version with the patch. |
|
Back to top |
|
|
|