The 2.6.10 kernel seems to have enabled the noexec for
i386 too. I have no idea if i386 kernels are affected
too, but I think they are.
Booting the kernel with noexec=off fixes the problem.
Here is a log from IRC a few days ago with Colin Watson:
perhaps whatever in sablevm needs an executable
severity 289494 important
thanks
It seems this is caused by the 2.6.10 amd64 kernel. It
didn't enter sid yet (it's in NEW) so I can't reassign this to
kernel-image-2.6.10-amd64 yet.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL P
On Wed, Jan 12, 2005 at 01:47:59AM -0500, Grzegorz B. Prokopski wrote:
>
> But the configure itself (at least the one executed at the beginning,
> not sure that is the only one) seemed to execute properly.
And that is a current sid or sarge? In that case, feel free to
lower the severity (and tag
Hi,
I tried to reproduce the problem by building db4.2-4.2.52 source on a
sparc machine, but it failed after a few minutes, during the compilation
of native code:
/usr/lib/gcc-lib/sparc-linux/3.3.5/../../../../lib/crti.o(.init+0x0): In
function `_init':
/build/buildd/glibc-2.3.2.ds1/build-tree/sp
4 matches
Mail list logo
