When emerging glibc-2.3.4.20040808-r1, the newly compiled iconvconfig is automacally executed in the postinstall step of the ebuild: if [ -x "${ROOT}/usr/sbin/iconvconfig" ]; then # Generate fastloading iconv module configuration file. ${ROOT}/usr/sbin/iconvconfig --prefix=${ROOT} fi However, on my hardened system with grsecurity/pax enabled, this gets killed due to a pax violation: Jan 18 12:42:40 kklaptop kernel: PAX: execution attempt in: <anonymous mapping>, 5b3e1000-5b3f8000 5b3e1000 Jan 18 12:42:40 kklaptop kernel: PAX: terminating task: /usr/sbin/iconvconfig(ic onvconfig):5432, uid/euid: 0/0, PC: 5b3f5908, SP: 5b3f5824
smells like somebody dropped the trampoline patch.
My kernel is configured with PAX-EMUTRAMP=N (off). I'm using PaX segment based execution protection. Is this a problem when emerging gcc, do I have to use a kernel with PAX-EMUTRAMP=Y?
should be fixed now [again]
thanks spanky