Hello, On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote: > On 31/08/17 21:55, Uwe Kleine-König wrote: > > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote: > >> That is very much like on x86_64 missing define "#weak_define __x86_64__ 1" > >> > >> Does cgcc work for you? In the future we do want to move the archetecture > >> related define from cgcc into sparse by itself. For now you can set > >> "sparse" as "cgcc -no-compile" > > > > Yes that works. So to address the Debian bug I can do: > > > > - move sparse to /usr/lib > > - teach cgcc about the move of sparse > > - make /usr/bin/sparse call cgcc -no-compile "$@" > > Hmm, I don't think that would be a good idea ... > > > or is it easier to teach sparse about the architecture stuff? > > I now understand (I think!) that you are building a sparse > package (presumably a .deb) and you are concerned that sparse > does not pass it's own testsuite on those platforms. Nearly right. I'm responsible for the sparse Debian package and the problem at hand is https://bugs.debian.org/873508. This bug report has "Severity: serious" wihch might eventually result in the removal of sparse from the Debian archive. @anarcat: Given that cgcc seems to work, would you agree to apply the following patch to horst: diff --git a/Makefile b/Makefile index 4f924fa..d563652 100644 --- a/Makefile +++ b/Makefile @@ -110,7 +110,7 @@ $(NAME): $(OBJS) $(OBJS): .buildflags check: - sparse $(CFLAGS) *.[ch] + cgcc -no-compile $(CFLAGS) *.[ch] clean: -rm -f *.o radiotap/*.o *~ and downgrade the bug to "important"? That would be a compromise that buys us a bit of time. > As I said before, the additional failures you are seeing are > in the 'llvm backend' code (which, as far as I know, only passes > on x86_64 Linux), and in my opinion the llvm-backend programs should > not be installed. (The Makefile will build them automatically if > you have llvm installed, likewise for c2xml/libxml and test-inspect/gtk). Currently the sparse package contains /usr/include/sparse/, c2xml, cgcc, sparse, sparse-llvm, sparsec and a separate package sparse-test-inspect includes test-inspect. (That's how I inherited the package some time ago.) > [I would like to see build variable(s) to allow the user to suppress > the build (or installation) of the other 'non-primary' sparse programs.] > > Anyway, if you were to un-install llvm, sparse-llvm etc., would not > be built, and the tests would not be run ... ;-) > > Christopher, as the project maintainer, has the joy of making these > kinds of decisions! :-D This only solves a part of the problem because the bug report is about sparse itself, not it's llvm part. Best regards Uwe
Attachment:
signature.asc
Description: PGP signature
