git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warnings

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Jan 29, 2019, 02:23 UTC
Message-ID
<f107d853-da55-ddd2-191f-8157cd5a8edd@ramsayjones.plus.com>
In-Reply-To
<20190129015207.6emajopy7xqmqo4j@ltop.local>
On 29/01/2019 01:52, Luc Van Oostenryck wrote:
Show 13 quoted lines
> On Mon, Jan 28, 2019 at 08:13:03PM +0000, Ramsay Jones wrote:
> 
> Hi
> 
>> 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 ...
> 
> perl is only used as the interpreter of cgcc.
heh, yeah (palm-face), I was only thinking about _build_ dependency! :-D

ATB, Ramsay Jones

Previous: Luc Van Oostenryck
Message 8 of 8 in “test-xml-encode: fix sparse NULL pointer warnings”
  1. test-xml-encode: fix sparse NULL pointer warningsRamsay Jones, Jan 26, 2019
  2. sparse job, was Re: [PATCH] test-xml-encode: fix sparse NULL pointer warningsJohannes Schindelin, Jan 28, 2019
  3. Ramsay JonesJan 28, 2019
  4. Johannes SchindelinJan 28, 2019
  5. Ramsay JonesJan 29, 2019
  6. Jonathan NiederJan 29, 2019
  7. Luc Van OostenryckJan 29, 2019
  8. Ramsay JonesJan 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.