Re: sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warnings
- Date: Tue, 29 Jan 2019 00:02:14 +0000
- From: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warnings
On 28/01/2019 22:34, Johannes Schindelin wrote:
> Hi Ramsay,
> On Mon, 28 Jan 2019, Ramsay Jones wrote:
>> Hmm, I've never built an Ubuntu package before, so I don't know
>> exactly what would be required (spec file etc.) to create a PPA.
>> But I suspect you are not talking about doing that, right?
> I would have gone for `checkinstall`... That still works, right?
Ah, I never think about using checkinstall - I haven't really used
it in anger. For some reason, I thought you needed to structure your
Makefile a certain way (using $DESTDIR or somesuch), but I seem to
be confusing it with something else. Apparently, no change to the
Makefile is required - it uses some kind of filesystem watcher to
note which files are copied into place by 'make install'. heh, go
So, I think you only need to set the PREFIX when building (the
default installation PREFIX is $HOME), or create a local.mk file
to configure the build (I don't do that). The 'sparse' build
does not make use of any 'auto-tools', so no configure script.
Ah, I think you will need to have pkg-config installed. I have
never built sparse from a tar-ball - I assume it works! ;-)
So (just typing into my email client - not tested):
$ wget http://www.kernel.org/pub/software/devel/sparse/dist/sparse-0.6.0.tar.gz
$ tar xvf sparse-0.6.0.tar.gz
$ cd sparse-0.6.0
$ make PREFIX=/usr/local
$ sudo checkinstall make PREFIX=/usr/local install
... should do it. (famous last words).