<snip> >>> Don't you actually want to also pick up utils/sefcontext_compile? >>> That is built and used on the build host. And I'm not sure why we'd >>> drop the other SUBDIRS. >> >> You'll start running into linking issues if things that use >> libselinux, use something not >> in the build host IIRC. Perhaps, if that is the issue, we just limit >> it to sefcontext_compile. > > Sure, the utils/Makefile can remove entries the same way it already does > for DISABLE_*. Well actually, that means every-time their is a new file added, the Makefile needs to be modified, I was trying to avoid that. Also, the remove list is super long, so it looks pretty unwieldy. <snip> _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
