Bug 137860 - (PATCH) Compilation problems with selinux on RHEL 7.3
Summary: (PATCH) Compilation problems with selinux on RHEL 7.3
Alias: None
Product: Fedora
Classification: Fedora
Component: vim   
(Show other bugs)
Version: 2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-02 10:02 UTC by František Dvořák
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-02 11:08:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
New version of vim-selinux.patch included in vim source package (3.66 KB, patch)
2004-11-02 10:06 UTC, František Dvořák
no flags Details | Diff

Description František Dvořák 2004-11-02 10:02:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914

Description of problem:
vim package in Fedora has a selinux patch which breaks compilation on
systems without selinux. Only problem is in src/configure.in, I send a
corrected patch vim-selinux.patch.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. boot into RHEL 7.3
2. rpmbuild --rebuild vim-6.2.457-1.src.rpm


Actual Results:  Headar file selinux.h not found.

Expected Results:  Succesful compilation.

Additional info:

Comment 1 František Dvořák 2004-11-02 10:06:04 UTC
Created attachment 106063 [details]
New version of vim-selinux.patch included in vim source package

There is changed only begin of the patch - detection in src/configure.in.

Comment 2 Karsten Hopp 2004-11-02 11:08:20 UTC
I usually set the WITH_SELINUX variable in the spec file to 0. This
disables the selinux patch and removes the Buildrequires:
libselinux-devel, too.
Anyway, your patch looks correct and I've added it to the CVS repository.

Note You need to log in before you can comment on or make changes to this bug.