oops :)
Comment #4 on issue 323 by david...@chromium.org: boringssl fails on travis-ci/clang-9 https://bugs.chromium.org/p/boringssl/issues/detail?id=323#c4 Looks like the issue is you've managed to convince it that your C compiler is Clang and your C++ compiler is GCC. -- The C compiler identification is Clang 9.0.1 -- Check for working C compiler: /usr/bin/clang -- Check for working C compiler: /usr/bin/clang -- works [...] -- The CXX compiler identification is GNU 9.2.1 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works We use the same flags for the C and C++ compiler, since mixing them is pretty rare, and it turns out our clang logic is based on the C++ compiler. I'm guessing you've set the CC environment variable to clang or so? You need to also point CXX to your clang++. пн, 16 мар. 2020 г. в 16:02, Илья Шипицин <chipits...@gmail.com>: > > > пн, 16 мар. 2020 г. в 14:54, Willy Tarreau <w...@1wt.eu>: > >> On Mon, Mar 16, 2020 at 10:49:26AM +0100, Tim Düsterhus wrote: >> > Ilya, >> > >> > Am 16.03.20 um 07:52 schrieb ???? ???????: >> > > we use clang because of its address sanitizer. I found gcc asan more >> noisy >> > > and less usable. >> > >> > I believe you broke ASAN with clang-9 anyway, because the Travis >> > configuration checks for 'clang': >> > >> https://github.com/haproxy/haproxy/blob/67b095e797a156ae27b7b52f6ccf57171717dd16/.travis.yml#L108 >> > >> > It probably needs to read `if [ "$CC" = "clang*" ]` (unless I got my >> > bash syntax wrong). >> >> Indeed. However it should be: >> >> if [ "${CC%-*}" = "clang" ] >> > > it did not indicate any error. so it looked ok :) > > >> >> I'd like to focus on what's still broken (i.e. the abns seamless reload >> test) >> before adding more noise. It ought to be fixed but it is still random, it >> even failed once on amd64. I definitely need to be able to reproduce it, >> as >> I was certain the two recent bugs fixed were the only ones responsible for >> this. >> > > sure > > >> >> Willy >> >
