From: Daniel J Walsh <dwalsh@redhat.com>
To: Michael Seyfert <michael@codesand.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: Current Makefile system is inconvenient/limited
Date: Mon, 06 May 2013 12:16:21 -0400 [thread overview]
Message-ID: <5187D755.2020001@redhat.com> (raw)
In-Reply-To: <5181072c.4648320a.7ef1.ffff8111@mx.google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/01/2013 08:14 AM, Michael Seyfert wrote:
> The current system for building selinux requires a lot of workarounds like
> C_INCLUDE_PATH and is also interdependent on setools. I was looking at the
> debian packages and they require two build throughs of selinux just to get
> things to compile properly. Am I the only one that thinks this is a
> problem?
>
Patches Welcomed.
I don't think anyone loves it, but most people do not hate it enough to fix it...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlGH11UACgkQrlYvE4MpobPkHwCfXbAlk6WCJdhXqH0g4jaeCYp9
BSQAnij1i4qDFngpO0zhKxmbKt2X/MG5
=tYfk
-----END PGP SIGNATURE-----
--
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.
next prev parent reply other threads:[~2013-05-06 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 12:14 Current Makefile system is inconvenient/limited Michael Seyfert
2013-05-01 12:40 ` piruthiviraj natarajan
2013-05-01 12:43 ` Joshua Brindle
2013-05-01 22:57 ` Michael Seyfert
2013-05-01 23:33 ` William Roberts
2013-05-06 16:16 ` Daniel J Walsh [this message]
2013-05-08 6:44 ` Michael Seyfert
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=5187D755.2020001@redhat.com \
--to=dwalsh@redhat.com \
--cc=michael@codesand.org \
--cc=selinux@tycho.nsa.gov \
/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.