Hi Danilo,
On 14/02/2017 16:01, Danilo Guerrera wrote:
Dear list,
I tried to install a Clang-3.4-GCC-4.9.3-2.25 (I need to install a
software that relies on that particular version of Clang). It resulted
in an error while making the test (the Clang test that
takes place after every phase, not the sanity checking). A partial log
of the error can be found here:
http://pastebin.com/qVZFPTDp
I tried locally and everything works. It just fails when installing on
NFS.
Googling a little bit I found an issue with a previous Clang version
and EB:
https://github.com/hpcugent/easybuild-easyconfigs/issues/466
We do not use noatime, and we have a bind mount. So all the
things/possible solutions discussed in that issue do not work for us.
Interestingly, the only other info related to this error comes from a
clang developers mailing list:
http://clang-developers.42468.n3.nabble.com/3-7-Release-RC1-has-been-tagged-Testing-Phase-I-begins-td4046646i20.html#a4046725
There you find this comment:
“clang+llvm-3.7.0-rc1-mipsel-linux-gnu.tar.xz
Failing Tests (4):
AddressSanitizer-mipsel-linux ::
TestCases/Linux/kernel-area.cc <http://kernel-area.cc>
Clang :: Modules/prune.m <- expected since this system uses an
NFS mount with noatime.”
But again, we do not use noatime.
Any idea? Is there a way to let EB skip that “error”?
In the past, we have disabled individual quirky tests for Clang with a
patch, see for example
https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/c/Clang/Clang-3.4-failing-sanitizer-tests.patch
.
Maybe that's a reasonable way out?
regards,
Kenneth
