Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fixes #184

Closed
wants to merge 2 commits into from
Closed

Conversation

tpetazzoni
Copy link
Contributor

This pull request contains two build fixes that were needed in the context of packaging SELinux in the Buildroot project. They are sent in a single pull request because even though they address different issues, the second commit modifies the same line of code as the first commit, even if for two completely different reasons.

The ln --relative option is not available in fairly old versions of
ln, which are still in use in older Linux distributions.

Since the two use of ln --relative can very trivially be implemented
differently in libselinux/src/Makefile, let's do so.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
PYCEXT is computed by asking the Python intrepreter what is the
file extension used for native Python modules.

Unfortunately, when cross-compiling, the host Python doesn't give the
proper result: it gives the result matching the build machine, and not
the target machine. Due to this, the symlink has an incorrect name,
and doesn't point to the .so file that was actually built/installed.

To address this and keep things simple, this patch just changes the ln
invocation to rely on the name of the _selinux*.so Python module that
was installed.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
@stephensmalley
Copy link
Member

Can you send these via git send-email or equivalent to selinux @ vger.kernel.org? That's the preferred way for submitting selinux patches.

@tpetazzoni
Copy link
Contributor Author

Ah, yes, sure thing!

@tpetazzoni tpetazzoni closed this Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants