All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Ambrose <Vikram.Ambrose@windriver.com>
To: Joshua Brindle <method@manicmethod.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	SELinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>,
	Manoj Srivastava <srivasta@debian.org>,
	Caleb Case <ccase@tresys.com>
Subject: Re: New SELinux toolchain build system
Date: Wed, 27 Aug 2008 14:06:29 -0400	[thread overview]
Message-ID: <48B597A5.40809@windriver.com> (raw)
In-Reply-To: <48B34EA0.8040302@manicmethod.com>

Joshua Brindle wrote:
> Vikram Ambrose wrote:
>   
>> Joshua Brindle wrote:
>>     
>  
>   
>>> * make clean from the top doesn't actually clean anything, it just
>>> removes the makefiles
>>>
>>> * there is no way to distclean from the top level, eg., make the
>>> repository look like it will when we package up a release
>>>   
>>>       
>> The top level makefile was just a proof-of-concept. If you need a top
>> level makefile, then write one. The one i supplied was only intended to
>> show that the tree builds.
>>     
>
> So, the things you expect others to do include:
> make the top level makefile useful (clean, distclean, debug build, etc)
>   

I'll do that one if i get time this week.

> fix the CFLAGS in all the app/lib makefiles
>   

Like i said previously, do not force unnecessary CFLAGS onto the package 
builder. If you need special flags add it to your configure line, 
./configure CFLAGS="-Wall -I/blah -fPIC" --prefix=/usr --bindir=/bin 
etc...  A good place for these would be in the top level Makefile, which 
would be a hard coded makefile.

> add the dispol/dismod makefile
>   

I'm doing this one

> add the ruby swig support
> add make test targets to all lib Makefiles
>
>   

I'll try to do these this week, but I cannot test it, so be warned.

> Anything else?
>   

Nope.

> I'm not adverse to the patch set, and when/if we ack and merge it, it will be our responsibility to maintain but I'm worried about it not being completed before that. I'm not an autotools expert (or even a beginner) and neither are the other maintainers. As such I don't see much motivation to finish up the patch set for you in order to get it in a mergeable state (and this isn't abnormal for opensource projects, try dropping an incomplete patch on lkml and see where it gets you).
>   

Surprised, a little, so I'll try my best to help with anything I can, 
but time is not on my side.

Updates are in the mix, coming to a mailing list near you! :)


Vikram

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2008-08-27 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 14:36 New SELinux toolchain build system Vikram Ambrose
2008-08-12 19:35 ` Daniel J Walsh
2008-08-12 20:47 ` Joshua Brindle
2008-08-14 18:19   ` Vikram Ambrose
2008-08-25  1:17     ` Joshua Brindle
2008-08-25 14:06       ` Vikram Ambrose
2008-08-26  0:30         ` Joshua Brindle
2008-08-27 18:06           ` Vikram Ambrose [this message]

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=48B597A5.40809@windriver.com \
    --to=vikram.ambrose@windriver.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=ccase@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=method@manicmethod.com \
    --cc=sds@tycho.nsa.gov \
    --cc=srivasta@debian.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.