sparse as a compiler front-end

sparse as a compiler front-end

[Jeff Garzik]

I see that sparse made it into Fedora Extras, so that 'yum install' 
automatically pulls it down for me.  Yay!  Thanks, Matt.

Can libsparse.a and necessary includes be packaged as well?

I have wild ambitions of rewriting compile-i386.c (my int-only x86 
pseudo-compiler) using the new basic block stuff, into a proper [if very 
very basic] C99 compiler.

	Jeff

Re: sparse as a compiler front-end

[Matt Domsch]

On Sat, Nov 11, 2006 at 04:54:08PM -0500, Jeff Garzik wrote:
> I see that sparse made it into Fedora Extras, so that 'yum install' 
> automatically pulls it down for me.  Yay!  Thanks, Matt.
> 
> Can libsparse.a and necessary includes be packaged as well?

.a or .so?  The .so just got dropped from the standard sparse 'make
install' with the 0.1 release.  If it comes back, I can put it into
the sparse package and the appropriate headers (please specify in the Makefile) into a
sparse-devel subpackage.

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

Re: sparse as a compiler front-end

[Josh Triplett]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

Jeff Garzik wrote:
> I see that sparse made it into Fedora Extras, so that 'yum install' 
> automatically pulls it down for me.  Yay!  Thanks, Matt.

Thanks indeed.

> Can libsparse.a and necessary includes be packaged as well?

Sure, assuming you don't mind coding against something potentially fluid.  The
next release will install the library and headers.  (At the moment, "necessary
headers" seems to mean "all of them".)

> I have wild ambitions of rewriting compile-i386.c (my int-only x86 
> pseudo-compiler) using the new basic block stuff, into a proper [if very 
> very basic] C99 compiler.

I look forward to seeing that.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: sparse as a compiler front-end

[Jeff Garzik]

Matt Domsch wrote:
> On Sat, Nov 11, 2006 at 04:54:08PM -0500, Jeff Garzik wrote:
>> I see that sparse made it into Fedora Extras, so that 'yum install' 
>> automatically pulls it down for me.  Yay!  Thanks, Matt.
>>
>> Can libsparse.a and necessary includes be packaged as well?
> 
> .a or .so?  The .so just got dropped from the standard sparse 'make

Doesn't matter to me...  Something is better than nothing.  With 
sparse's license, .a is no big deal.

Thanks,

	Jeff

Re: sparse as a compiler front-end

[Matt Domsch]

On Sat, Nov 11, 2006 at 08:45:41PM -0500, Jeff Garzik wrote:
> Matt Domsch wrote:
> >On Sat, Nov 11, 2006 at 04:54:08PM -0500, Jeff Garzik wrote:
> >>I see that sparse made it into Fedora Extras, so that 'yum install' 
> >>automatically pulls it down for me.  Yay!  Thanks, Matt.
> >>
> >>Can libsparse.a and necessary includes be packaged as well?
> >
> >.a or .so?  The .so just got dropped from the standard sparse 'make
> 
> Doesn't matter to me...  Something is better than nothing.  With 
> sparse's license, .a is no big deal.

Fedora Extras strongly discourages shipping and using .a if only to
ensure that any security issue uncovered can be addressed without
always rebuilding all downstream dependent apps.  Not too likely a
problem with a tool like sparse, but always a concern.

The .so would need to start being versioned, and care paid to bump the
version as the ABIs change.

That's one thing the opensuse build system does differently - tracking
the full dependency tree, and automatically rebuilding all downstream
dependent apps when an upstream app changes.


-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

Re: sparse as a compiler front-end

[Jeff Garzik]

Matt Domsch wrote:
> On Sat, Nov 11, 2006 at 08:45:41PM -0500, Jeff Garzik wrote:
>> Matt Domsch wrote:
>>> On Sat, Nov 11, 2006 at 04:54:08PM -0500, Jeff Garzik wrote:
>>>> I see that sparse made it into Fedora Extras, so that 'yum install' 
>>>> automatically pulls it down for me.  Yay!  Thanks, Matt.
>>>>
>>>> Can libsparse.a and necessary includes be packaged as well?
>>> .a or .so?  The .so just got dropped from the standard sparse 'make
>> Doesn't matter to me...  Something is better than nothing.  With 
>> sparse's license, .a is no big deal.
> 
> Fedora Extras strongly discourages shipping and using .a if only to
> ensure that any security issue uncovered can be addressed without
> always rebuilding all downstream dependent apps.  Not too likely a
> problem with a tool like sparse, but always a concern.
> 
> The .so would need to start being versioned, and care paid to bump the
> version as the ABIs change.

Or alteratively we could recognize that sparse is a bit of an unusual 
lib.  With the library likely to be changing rapidly, caring about ABIs 
at this early stage probably isn't in anybody's best interests.

	Jeff

Re: sparse as a compiler front-end

[Josh Triplett]

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

Josh Triplett wrote:
> Jeff Garzik wrote:
>> Can libsparse.a and necessary includes be packaged as well?
> 
> Sure, assuming you don't mind coding against something potentially fluid.  The
> next release will install the library and headers.  (At the moment, "necessary
> headers" seems to mean "all of them".)

The Sparse 0.2 release installs the library and headers, as well as a
pkg-config file.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: sparse as a compiler front-end

[Matt Domsch]

On Tue, Dec 05, 2006 at 08:53:04AM -0800, Josh Triplett wrote:
> Josh Triplett wrote:
> > Jeff Garzik wrote:
> >> Can libsparse.a and necessary includes be packaged as well?
> > 
> > Sure, assuming you don't mind coding against something potentially fluid.  The
> > next release will install the library and headers.  (At the moment, "necessary
> > headers" seems to mean "all of them".)
> 
> The Sparse 0.2 release installs the library and headers, as well as a
> pkg-config file.

I've got a test build of sparse-0.2 posted at
http://domsch.com/linux/fedora/extras/sparse/0.2/ which I intend to
put into Fedora Extras for FC5,6,devel.  This puts the libsparse.a and
headers into a -devel package.

Jeff, does this suit your needs?

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

Re: sparse as a compiler front-end

[Josh Triplett]

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Matt Domsch wrote:
> On Tue, Dec 05, 2006 at 08:53:04AM -0800, Josh Triplett wrote:
>> Josh Triplett wrote:
>>> Jeff Garzik wrote:
>>>> Can libsparse.a and necessary includes be packaged as well?
>>> Sure, assuming you don't mind coding against something potentially fluid.  The
>>> next release will install the library and headers.  (At the moment, "necessary
>>> headers" seems to mean "all of them".)
>> The Sparse 0.2 release installs the library and headers, as well as a
>> pkg-config file.
> 
> I've got a test build of sparse-0.2 posted at
> http://domsch.com/linux/fedora/extras/sparse/0.2/ which I intend to
> put into Fedora Extras for FC5,6,devel.  This puts the libsparse.a and
> headers into a -devel package.

From the spec file, I notice that you install the pkg-config file to
/usr/lib/pkgconfig (or equivalent), rather than /usr/share/pkgconfig (or
equivalent) as the Makefile does; any particular reason for that?

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: sparse as a compiler front-end

[Jeff Garzik]

Josh Triplett wrote:
> From the spec file, I notice that you install the pkg-config file to
> /usr/lib/pkgconfig (or equivalent), rather than /usr/share/pkgconfig (or
> equivalent) as the Makefile does; any particular reason for that?

The pkgconfig file describes an architecture-specific library, so it 
goes into /usr/lib/pkgconfig/$pkg.pc if its 32-bit (or the rare 64-bit 
arch that uses /usr/lib), and it goes into /usr/lib64/pkgconfig/$pkg.pc 
if the library is 64-bit.

/usr/share is not appropriate for architecture-specific data.

	Jeff

Re: sparse as a compiler front-end

[Jeff Garzik]

Matt Domsch wrote:
> On Tue, Dec 05, 2006 at 08:53:04AM -0800, Josh Triplett wrote:
>> Josh Triplett wrote:
>>> Jeff Garzik wrote:
>>>> Can libsparse.a and necessary includes be packaged as well?
>>> Sure, assuming you don't mind coding against something potentially fluid.  The
>>> next release will install the library and headers.  (At the moment, "necessary
>>> headers" seems to mean "all of them".)
>> The Sparse 0.2 release installs the library and headers, as well as a
>> pkg-config file.
> 
> I've got a test build of sparse-0.2 posted at
> http://domsch.com/linux/fedora/extras/sparse/0.2/ which I intend to
> put into Fedora Extras for FC5,6,devel.  This puts the libsparse.a and
> headers into a -devel package.
> 
> Jeff, does this suit your needs?

Yep, both sparse and sparse-devel look great, here on FC6!

Thanks,

	Jeff

Re: sparse as a compiler front-end

[Matt Domsch]

On Sat, Dec 09, 2006 at 05:17:46AM -0500, Jeff Garzik wrote:
> Matt Domsch wrote:
> >I've got a test build of sparse-0.2 posted at
> >http://domsch.com/linux/fedora/extras/sparse/0.2/
> >
> >Jeff, does this suit your needs?
> 
> Yep, both sparse and sparse-devel look great, here on FC6!

Great.  This will be in tomorrow's push of Fedora Extras for
FC{5,6,devel} then.

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

Re: sparse as a compiler front-end

[Josh Triplett]

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

Jeff Garzik wrote:
> Josh Triplett wrote:
>> From the spec file, I notice that you install the pkg-config file to
>> /usr/lib/pkgconfig (or equivalent), rather than /usr/share/pkgconfig (or
>> equivalent) as the Makefile does; any particular reason for that?
> 
> The pkgconfig file describes an architecture-specific library, so it 
> goes into /usr/lib/pkgconfig/$pkg.pc if its 32-bit (or the rare 64-bit 
> arch that uses /usr/lib), and it goes into /usr/lib64/pkgconfig/$pkg.pc 
> if the library is 64-bit.
> 
> /usr/share is not appropriate for architecture-specific data.

Latest sparse from Git now installs sparse.pc to $(LIBDIR)/pkgconfig (default
/usr/lib/pkgconfig).

Thanks,
Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]