All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>, tresys <refpolicy@oss1.tresys.com>
Subject: Re: [refpolicy] No rule to make target `/seusers', needed by `tmp/seusers'. Stop.
Date: Tue, 17 Nov 2009 12:25:43 -0800	[thread overview]
Message-ID: <4B0306C7.8010200@gmail.com> (raw)
In-Reply-To: <1258465270.27504.194.camel@gorn.columbia.tresys.com>

Christopher J. PeBenito wrote:
> On Mon, 2009-11-16 at 22:44 -0800, Justin Mattock wrote:
>    
>> I've hit something confusing to me.
>> When building a Monolithic policy everything
>> goes good. But as soon as I build a binary I hit this:
>>
>> m4 -D distro_redhat -D enable_ubac -D mls_num_sens=16 -D
>> mls_num_cats=256 -D mcs_num_cats=256 -D hide_broken_symptoms -D
>> users_extra support/divert.m4 policy/support/file_patterns.spt
>> policy/support/ipc_patterns.spt policy/support/loadable_module.spt
>> policy/support/misc_macros.spt policy/support/misc_patterns.spt
>> policy/support/mls_mcs_macros.spt policy/support/obj_perm_sets.spt
>> support/undivert.m4 policy/users | \
>>                  sed -r -n -e 's/^[[:blank:]]*//g' -e '/^user/p'>
>> tmp/users_extra
>> make: *** No rule to make target `/seusers', needed by `tmp/seusers'.  Stop.
>>
>> I've looked at the Makefile to make sure
>> I didn't forget anything(python,sed,awk,m4,flex)
>> but still can't seem to figure out what I'm missing
>> to have the policy compile the modules correctly.
>>
>> Keep in mind I don't want to wast any of your guy's time,
>> so any quick hints are appreciated.
>>      
>
> I can't reproduce this.  My guess is that either your policy sources are
> corrupt or the seusers makefile variable is being changed somehow, eg.
> by environmental variables.
>
>    
once again I find myself in a situation in of
which I can't comprehend(the enjoyment of
developing).

I think I'm missing a package, or built
a package without a certain package to
do this correctly. positive side is I'm able to
have monolithic build correctly.

At this point I'll just keep with monolithic on this machine,
and have binary on another machine so I can spend more time
at this problem.(and to think I figured "oh yeah
should be no problem with binary").

Justin P. Mattock

--
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.

WARNING: multiple messages have this Message-ID (diff)
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] No rule to make target `/seusers', needed by `tmp/seusers'. Stop.
Date: Tue, 17 Nov 2009 12:25:43 -0800	[thread overview]
Message-ID: <4B0306C7.8010200@gmail.com> (raw)
In-Reply-To: <1258465270.27504.194.camel@gorn.columbia.tresys.com>

Christopher J. PeBenito wrote:
> On Mon, 2009-11-16 at 22:44 -0800, Justin Mattock wrote:
>    
>> I've hit something confusing to me.
>> When building a Monolithic policy everything
>> goes good. But as soon as I build a binary I hit this:
>>
>> m4 -D distro_redhat -D enable_ubac -D mls_num_sens=16 -D
>> mls_num_cats=256 -D mcs_num_cats=256 -D hide_broken_symptoms -D
>> users_extra support/divert.m4 policy/support/file_patterns.spt
>> policy/support/ipc_patterns.spt policy/support/loadable_module.spt
>> policy/support/misc_macros.spt policy/support/misc_patterns.spt
>> policy/support/mls_mcs_macros.spt policy/support/obj_perm_sets.spt
>> support/undivert.m4 policy/users | \
>>                  sed -r -n -e 's/^[[:blank:]]*//g' -e '/^user/p'>
>> tmp/users_extra
>> make: *** No rule to make target `/seusers', needed by `tmp/seusers'.  Stop.
>>
>> I've looked at the Makefile to make sure
>> I didn't forget anything(python,sed,awk,m4,flex)
>> but still can't seem to figure out what I'm missing
>> to have the policy compile the modules correctly.
>>
>> Keep in mind I don't want to wast any of your guy's time,
>> so any quick hints are appreciated.
>>      
>
> I can't reproduce this.  My guess is that either your policy sources are
> corrupt or the seusers makefile variable is being changed somehow, eg.
> by environmental variables.
>
>    
once again I find myself in a situation in of
which I can't comprehend(the enjoyment of
developing).

I think I'm missing a package, or built
a package without a certain package to
do this correctly. positive side is I'm able to
have monolithic build correctly.

At this point I'll just keep with monolithic on this machine,
and have binary on another machine so I can spend more time
at this problem.(and to think I figured "oh yeah
should be no problem with binary").

Justin P. Mattock

  reply	other threads:[~2009-11-17 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  6:44 No rule to make target `/seusers', needed by `tmp/seusers'. Stop Justin Mattock
2009-11-17  6:44 ` [refpolicy] " Justin Mattock
2009-11-17 13:41 ` Christopher J. PeBenito
2009-11-17 13:41   ` Christopher J. PeBenito
2009-11-17 20:25   ` Justin P. Mattock [this message]
2009-11-17 20:25     ` Justin P. Mattock

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=4B0306C7.8010200@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=cpebenito@tresys.com \
    --cc=refpolicy@oss1.tresys.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.