-
Notifications
You must be signed in to change notification settings - Fork 18k
misc/cgo/testsanitizers: for MemorySanitizer, Linux kernel ≥ 4.1 requires clang ≥ 3.8.0 #12898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Which distro? |
Arch Linux. |
What does |
|
Also observing it on ubuntu 15.10.
Must add that I'd never run into this earlier (upgraded recently from ubuntu 15.04 which had gcc 4.9.x and kernel 3.19.0.31). Relevant output from
|
Looks like an upstream issue with LLVM/compiler-rt: https://llvm.org/bugs/show_bug.cgi?id=24155 A fix was pushed earlier this month (Oct 2015), it will likely be shipped with 3.8.0 (no backport to 3.7 given the API breakage). I've proposed a backport for Arch Linux users: https://bugs.archlinux.org/task/46913 I don't see any similar bug for Ubuntu at https://launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bugs, you could report it if you find it useful. I have not checked whether the patches apply to 3.6 though. |
@Lekensteyn, thanks for those links. @ianlancetaylor, sent you CL 17254. |
CL https://golang.org/cl/17254 mentions this issue. |
CL https://golang.org/cl/17323 mentions this issue. |
Fix a typo in de5b386; using `$ver` to determine linux major/minor versions would produce those for clang, use `$linuxver` instead. Updates #12898. Change-Id: I2c8e84ad02749fceaa958afd65e558bb0b08dddb Reviewed-on: https://go-review.googlesource.com/17323 Reviewed-by: Ian Lance Taylor <[email protected]> Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
I get this error while running
all.bash
. It looks similar issue #12814, but as I've got GCC installed, I don't think it is related to Clang. (also, my installed version of Clang is above 3.6). Re-posting this in a separate issue, per Ian's requestAnd the error is as follows:
Please let me know if any other information is required.
The text was updated successfully, but these errors were encountered: