bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: F13 SELinux failure


From: Peter O'Gorman
Subject: Re: F13 SELinux failure
Date: Mon, 07 Jun 2010 15:52:59 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4

On 06/07/2010 02:32 PM, Peter O'Gorman wrote:
On 06/07/2010 02:16 PM, Ralf Wildenhues wrote:

What's the nature of the failure? In general, we care about letting our
testsuite skip for cases it cannot reasonably pass, but only in those
cases. Can we detect it reliably?

It says this:

demo-exec.test: === Running demo-exec.test
demo-exec.test: === Executing uninstalled programs in libtool-2.2.8
Welcome to GNU Hell!
/home/pogma/tmp/libtool-2.2.8/tests/demo/.libs/lt-hell: error while
loading shared libraries:
/home/pogma/tmp/libtool-2.2.8/tests/demo/.libs/libhello.so.2: cannot
restore segment prot after reloc: Permission denied

We can check if selinux is in enforcing mode if getenforce(8) says
"Enforcing".


Ok spent 5 minutes with google and the selinux manpages (something I have to do any time I do anything related to selinux).

The above is, of course, after tests/demo-nopic.test, and the problem is the selinux boolean allow_execmod which disallows text relocations.

I'll look into making the test skip in this case.

Peter



reply via email to

[Prev in Thread] Current Thread [Next in Thread]