Bug 200561

True. Fix in next release.

BTW. 2.39 only builds with selinux disabled, due to one of the
memory protection features of selinux. This was not the case
in 2.38. It is currently not a great problem, since on the
buildsystem selinux is not enabled while building packages.
However, it might be worthwhile to look into the issue.

(In reply to comment #1)
> BTW. 2.39 only builds with selinux disabled, due to one of the
> memory protection features of selinux. This was not the case
> in 2.38. It is currently not a great problem, since on the
> buildsystem selinux is not enabled while building packages.
> However, it might be worthwhile to look into the issue.

this depends on what "enabled selinux" means.
I have no problem building clisp on my fc5 (I have no idea if selinux is enabled).

look for "--with-gmalloc" in clisp/unix/PLATFORMS

The particular selinux error is the following:

type=AVC msg=audit(1154112641.464:3957): avc:  denied  { execheap } for 
pid=18875 comm="test1" scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process

so it execheap policy that is violated

I tried with --with-gmalloc but no change.
The exact place of the error is this:
./test1
trampoline: cannot make memory executable
make[2]: *** [check] Aborted
make[2]: Leaving directory
`/home/gemi/Projects/fedora/extras/clisp/FC-5/clisp-2.39/build/callback/trampoline_r'
make[1]: *** [check-subdirs] Error 2
make[1]: Leaving directory
`/home/gemi/Projects/fedora/extras/clisp/FC-5/clisp-2.39/build/callback'
./configure: despite --with-dynamic-ffi, FFCALL could not be built
error: Bad exit status from /usr/tmp/rpm/rpm-tmp.96860 (%build)

(In reply to comment #3)
> The particular selinux error is the following:
> 
> type=AVC msg=audit(1154112641.464:3957): avc:  denied  { execheap } for 
> pid=18875 comm="test1" scontext=user_u:system_r:unconfined_t:s0
> tcontext=user_u:system_r:unconfined_t:s0 tclass=process
> 
> so it execheap policy that is violated

I thought this was fixed in 2.33.2
2004-05-21 - LINUX_NOEXEC_HEAPCODES
(indeed clisp --version indicated that this memory model is used).
could you please file a self-contained bug report about selinux/clisp
interaction on the clisp SF bug tracker?
thanks.

(In reply to comment #4)
> I tried with --with-gmalloc but no change.
> The exact place of the error is this:
> ./test1
> trampoline: cannot make memory executable
> make[2]: *** [check] Aborted
> make[2]: Leaving directory
>
`/home/gemi/Projects/fedora/extras/clisp/FC-5/clisp-2.39/build/callback/trampoline_r'
> make[1]: *** [check-subdirs] Error 2
> make[1]: Leaving directory
> `/home/gemi/Projects/fedora/extras/clisp/FC-5/clisp-2.39/build/callback'
> ./configure: despite --with-dynamic-ffi, FFCALL could not be built
> error: Bad exit status from /usr/tmp/rpm/rpm-tmp.96860 (%build)
> 

so this is not a CLISP problem.
this is an FFCALL problem.
please remove "--with-dynamic-ffi" from the configure line and see if clisp builds.
please _DO_ submit the FFCALL bug report to the CLISP bug tracker!

Without --with-dynamic-ffi, basic compilation proceeds with selinux
enabled, but fails, of course, on the postgres module.
I will submit the bug report about FFCALL then.

Are there any issues with the current release, or should I
proceed with a new build with current fixes?

(In reply to comment #7)
> Are there any issues with the current release, or should I
> proceed with a new build with current fixes?

everything else looks fine, thanks.