All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Joshua Brindle <method@manicmethod.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Failure to build policycoreutils from git
Date: Wed, 24 Jun 2009 09:22:14 -0400	[thread overview]
Message-ID: <4A422886.2000406@redhat.com> (raw)
In-Reply-To: <4A4127B0.4010801@manicmethod.com>

On 06/23/2009 03:06 PM, Joshua Brindle wrote:
> Manoj Srivastava wrote:
>> Hi,
>>
>> __> tar zvvfx
>> /usr/local/src/selinux-dev-release/policycoreutils-2.0.64.tar.gz
>> __> cd policycoreutils-2.0.64
>> __> make
>> make[1]: Entering directory `/tmp/policycoreutils-2.0.64/setfiles'
>> cc -Werror -Wall -W -D_FILE_OFFSET_BITS=64 -I/usr/include -c -o
>> setfiles.o setfiles.c
>> cc setfiles.o -lselinux -lsepol -L/usr/lib -o setfiles
>>
>> …
>>
>> cc setsebool.o -lsepol -lselinux -lsemanage -L/usr/lib -o setsebool
>> make[1]: Leaving directory `/tmp/policycoreutils-2.0.64/setsebool'
>> make[1]: Entering directory `/tmp/policycoreutils-2.0.64/po'
>> make[1]: *** No rule to make target `../gui/booleansPage.py', needed
>> by `policycoreutils.pot'. Stop.
>> make[1]: Leaving directory `/tmp/policycoreutils-2.0.64/po'
>> make: *** [all] Error 1
>>
>>
>> Indeed, there is no policycoreutils-2.0.64/gui directory at
>> all. I think the pot file needs to be redone, without any extraneos
>> directories, or a means for generating the gui dir should be given.
>>
>> Thanks,
>>
>> manoj
>
> Hrm, those entries were added to POTFILES last September and haven't
> seemed to cause a problem. When I build I always build from the top of
> the repo and this didn't happen at all but indeed when I built from the
> policycoreutils directory it did.
>
> I don't really know anything about POTFILES or generating it, the po
> patches were pretty much accepted blindly, perhaps a mistake in hindsight.
>
> --
> 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.
Yes you should remove the gui lines from the Makefile.* and probably 
POTFILES.*

Some one is working on a system-config-selinux package to remove the gui 
from policycoreutils and make it a separate package.



--
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:[~2009-06-24 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 17:52 Failure to build policycoreutils from git Manoj Srivastava
2009-06-23 19:06 ` Joshua Brindle
2009-06-24 13:22   ` Daniel J Walsh [this message]
2009-06-24 14:43     ` Joshua Brindle

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=4A422886.2000406@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=method@manicmethod.com \
    --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.