From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warnings
Date: Mon, 28 Jan 2019 20:13:03 +0000 [thread overview]
Message-ID: <a6b689da-b002-0aa2-e9d6-755d004bc320@ramsayjones.plus.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1901281706440.41@tvgsbejvaqbjf.bet>
On 28/01/2019 16:10, Johannes Schindelin wrote:
> Hi Ramsay,
>
> On Sat, 26 Jan 2019, Ramsay Jones wrote:
>
>>
>> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
>> ---
>>
>> Hi Johannes,
>>
>> If you need to re-roll your 'js/vsts-ci' branch, could you please
>> squash this into the relevant patch (commit af7747e7c7 ("tests: optionally
>> write results as JUnit-style .xml", 2019-01-23)).
>
> Certainly!
>
> BTW would you be interested in working with me on an Azure Pipeline that
> runs `sparse` on all of Junio's branches? (I am now pretty proficient with
> building a software package in one Azure Pipeline, publishing it as a
> build artifact, then consuming it from another Azure Pipeline, so I would
> build the `sparse` package as an Ubuntu package and offer it as a build
> artifact.)
Happy to help, if I can.
Looking at the sparse wiki [1] we can see that the most recent
release of sparse is v0.6.0, released on December 26th 2018
(just too late for crimble!). This is the release you will
need to use for more recent Linux distros (eg. fedora 27+,
Ubuntu 18.04, 18.10, etc).
The releases are available from [2] as a compressed tar-ball
using '.gz' or .'xz' compression. eg. sparse-0.6.0.tar.gz
(there is also a sparse-0.6.0.tar.sign).
[The git repo is at [3], BTW].
[I was a little surprised that Linux Mint 19.1 (based on Ubuntu
18.04) has v0.5.1 - Debian unstable has v0.5.2, but both of those
are just a little too old for use with git on recent Linux.]
It seems Ubuntu has split sparse into two packages, the main
'sparse' package, which contains the command-line programs and
a 'sparse-test-inspect' package, which contains the 'test-inspect'
GUI program (and so depends on GTK).
The dependencies for the 'sparse' package includes: libc6 (>= 2.14),
libllvm4.0 (>= 1:4.0~), libxml2 (>= 2.7.4), perl:any
However, for git, we only need to build 'cgcc' and 'sparse', which
means we can forget about libxml (only used for c2xml), and libllvm
(only used for sparse-llvm/sparsec/sparsei). Also, I'm not sure what
perl is doing there ...
Note that these dependencies (along with the dependent programs) are
optional and I can happily build sparse without them:
$ make clean
Makefile:124: Your system does not have libxml, disabling c2xml
Makefile:146: Your system does not have gtk3/gtk2, disabling test-inspect
Makefile:179: Your system does not have llvm, disabling sparse-llvm
CLEAN
$
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?
ATB,
Ramsay Jones
[1] https://sparse.wiki.kernel.org/index.php/Main_Page
[2] http://www.kernel.org/pub/software/devel/sparse/dist/
[3] git://git.kernel.org/pub/scm/devel/sparse/sparse.git
next prev parent reply other threads:[~2019-01-28 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 21:03 [PATCH] test-xml-encode: fix sparse NULL pointer warnings Ramsay Jones
2019-01-28 16:10 ` sparse job, was " Johannes Schindelin
2019-01-28 20:13 ` Ramsay Jones [this message]
2019-01-28 22:34 ` Johannes Schindelin
2019-01-29 0:02 ` Ramsay Jones
2019-01-29 1:44 ` Jonathan Nieder
2019-01-29 1:52 ` Luc Van Oostenryck
2019-01-29 2:23 ` Ramsay Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6b689da-b002-0aa2-e9d6-755d004bc320@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox