toralf
Developer
Joined: 01 Feb 2004
Posts: 3922
Location: Hamburg
|
 Posted: Sat Apr 30, 2016 7:56 pm Post subject: extend the tinderbox coverage to grsec failures |
 |
|
I do run the tinderbox at a hardened host. There are packages which refuses to build due to the grsecurity + PAX hardened features of the host, eg.: | Code: | # grep polyml /var/log/grsec.log
Apr 30 21:32:11 ms-magpie kernel: [ 2879.163865] grsec: denied RWX mmap of <anonymous mapping> by /home/tinderbox/images1/amd64-desktop-unstable_20160420-104159/var/tmp/portage/dev-lang/polyml-5.5.2/work/polyml.5.5.2/.libs/polyimport[polyimport:12207] uid/euid:250/250 gid/egid:250/250, parent /home/tinderbox/images1/amd64-desktop-unstable_20160420-104159/bin/bash[sh:12206] uid/euid:250/250 gid/egid:250/250
|
coming from | Code: | make[2]: Entering directory '/var/tmp/portage/dev-lang/polyml-5.5.2/work/polyml.5.5.2'
cp ./imports/polymlx86_64.txt polytemp.txt
./polyimport -H 50 polytemp.txt -I . < ./exportPoly.sml
Insufficient memory to allocate the heap
Makefile:1145: recipe for target 'polyexport.o' failed
make[2]: *** [polyexport.o] Error 1 |
I do wonder if those build failures are helpful (for whom ?, who would work on this ?) and if yes (and yes), if there's already a tracker for that ? |
|
Portage & Programming
