Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

2018-09-25 Thread Luc Van Oostenryck
On Tue, Sep 25, 2018 at 04:38:01PM +0200, Uwe Kleine-König wrote: > > By *default*, if no -gcc-base-dir is used, sparse use the same dir > > as the one used by the GCC used to compile sparse itself. It's only > > this default that is hardcoded. > > I wasn't sure if this is expected to work. I had

Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

2018-09-24 Thread Luc Van Oostenryck
On Fri, Sep 14, 2018 at 09:45:44PM +0200, Uwe Kleine-König wrote: > Hello, > > [Cc += sparse mailing list] Sorry for the late answer. > > > Santiago Vila wrote... > > > > > > > make -j1 check > > > > make[1]: Entering directory '/<>' > > > > sparse -g -O2 -fdebug-prefix-map=/<>=. > >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

2017-09-10 Thread Luc Van Oostenryck
On Sun, Sep 10, 2017 at 10:43 AM, Uwe Kleine-König wrote: > >> Meanwhile, is it possible to have the build logs but with 'make V=1 ...' ? >> It would also be useful to have: >> - the output of 'uname -a' >> - the details about the version of LLVM you're using > > Sure, can

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

2017-09-10 Thread Luc Van Oostenryck
On Sun, Sep 10, 2017 at 10:43 AM, Uwe Kleine-König <u...@kleine-koenig.org> wrote: > On 09/10/2017 03:22 AM, Luc Van Oostenryck wrote: >> >> I fully test on x86, x86-64, arm & ARM64 (with LLVM 3.9 or 4.0). >> I also test on ppc64 but not the LLVM part because the ma

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

2017-09-09 Thread Luc Van Oostenryck
On Sat, Sep 9, 2017 at 11:02 PM, Uwe Kleine-König wrote: > > I tried this on ppc64le and it fixes 2 tests, so were at > > Out of 287 tests, 273 passed, 14 failed (10 of them are known to fail) > > The repaired tests are: > > backend/hello.c >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

2017-09-03 Thread Luc Van Oostenryck
auto-extracted from GCC when doing a native build. Using some sort of spec file or a .sparserc can help too. I also note that currently, sparse is already largely universal *because* it *doesn't* need those platform details (or only the very minimal: word size). -- Luc Van Oostenryck