Re: Cannot enable executable stack

2005-08-07 Thread Bob Proulx
Nils Durner wrote: > > > cannot enable executable stack as shared object requires: Error 14 > #uname -a > Linux 2.4.18-bf2.4 #1 Fri Jun 7 06:12:37 UTC 2002 i586 GNU/Linux That is the problem. The 2.4.18-bf2.4 is a Woody kernel. Woody to Sarge is supported. And Sarge to Etch/Sid is supported.

Re: Cannot enable executable stack

2005-08-07 Thread N. Durner
It seems that glibc upgrade is causing two problems: 1) related to PaX-enabled kernels - that's reason for my problems 2) related to old kernels - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321718 [...] Do you think switching to another kernel would help? Yes, I think 'Error 14'

Re: Cannot enable executable stack

2005-08-07 Thread Nils Durner
> Do you have kernel patched with PaX/grsecurity? I don't think so: --- #uname -a Linux 2.4.18-bf2.4 #1 Fri Jun 7 06:12:37 UTC 2002 i586 GNU/Linux --- > As a temporary solution, if you use PaX, you can disable memory > protection with 'chpax -m `which mutt`', etc chpax and paxctl don't work for m

Re: Re: Cannot enable executable stack

2005-08-07 Thread Jerzy Kozera
-- Pozdrawiam, Jerzy Kozera -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Cannot enable executable stack

2005-08-07 Thread Jerzy Kozera
07-08-2005, 01:40 +0200, Nils Durner wrote: > after a online update using dselect, some programs (wget, sendmail, > mutt, qpopper...) fail with > --- > mutt: error while loading shared libraries: libgcrypt.so.11: cannot > enable executable stack as shared object requires: Error 14 > in.qpopper: err