On Thu, Sep 26, 2019 at 07:50:27PM +0100, Ramsay Jones wrote: > > Welcome back Luc. ;-) Thank you! > [BTW, we are still in 'RC' period! I have been using sparse > version v0.6.1-rc1-7-g2b96cd8 in 'production' all this time ...] Yes, I know. In March-April I was close to get v0.6.1 out but then ... > I just fetched sparse and tested master@3c74809, and it failed > on cygwin! > > At first I thought it was this patch (ie it was all sparse-llvm > tests which failed), but I was equally sure I had tested back > when Randy sent the patch (_not_ just compile tested). > > However, if I go back to v0.6.1-rc1-7-g2b96cd8, it also fails, so > this is not the smoking gun. Then I remembered that the cygwin > package for clang/llvm was updated recently ... > > Back when Randy sent the patch I was on clang/llvm v3.x.y (I _think_ > it was 3.0.1, but don't quote me), but now I am on v8.0.1. Randy had the problem on llvm-3.8.0. > I haven't looked into the errors/warnings yet, but they seem to > relate to 'unknown/misused' pseudo-ops used for debug info. I really don't think it could be related to the last patch. I don't use or have access to cygwin but I've tested on Debian (bullseye/sid) with gcc-7 & gcc-9 and there wasn't any problem with llvm-8 (on Ubuntu I can only test with llvm-7). So, I'm curious to know more about this error you're seeing. Two years ago or so, I had once a problem with the version of the C++ library (libc++ vs. libstc++) and the Makefile currently contains a hack for it (the line using llvm-config --cxxflags and then grepping for -stdlib=libc++). Can you check the output of this comand and, if it doesn't report '-stdlib=libc++', try to explicitly add -lc++ in LLVM_LIBS? Thanks for the report. -- Luc
