grsecurity forums

Facing the same problem as Hal9000 in this thread. Just following up with the suggestion to start a new thread ...

I'm compiling with make-kpkg, the process ultimately fails with

Code: Select all

[..]
make[3]: *** [arch/i386/boot/compressed/vmlinux.bin] Error 153
make[2]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make[1]: *** [bzImage] Error 2
make[1]: Leaving directory `/usr/local/src/linux-2.6.19.1'
make: *** [stamp-build] Error 2

Full log
Kernel config

Edit: links removed

No problems with grsecurity-2.1.9-2.6.18.1-200610281533 or prior and identical configuration (chose defaults with make oldconfig).

Insights, anybody?

Hi,

Code: Select all

  LD      vmlinux
ld: vmlinux: warning: allocated section `.text.align' not in segment
ld: vmlinux: warning: allocated section `.module.text' not in segment

I got the same warnings.

Code: Select all

  OBJCOPY arch/i386/boot/compressed/vmlinux.bin

I had the build fail at the same point.
In my case upgrading binutils helped. (Not sure to which version - says here that 2.17 is needed, but 2.16.1 from Gentoo works fine and 2.15.92.0.2 from Slackware does not).

Hope this helps.

Running Debian sarge here ... and frankly, I'm not in the mood to install backports or custom packages unless must be. Thanks for your help. Looks like I'll have to hold on until etch is declared stable ;-).

i had the same problem.
problem was that i just copied over the .config file from 2.6.17 (or .18 dont remember), ran make menuconfig and had it save the config file.
well, this seems to break something and compilation goes wrong.
so i copied the .config from my earlier kernel again, then started compiling right away and answered the new questions interactivelly on console. this worked fine.
hal

Well, I did run make oldconfig after copying over the .config and was still experiencing the very same error ...

aldee wrote:Well, I did run make oldconfig after copying over the .config and was still experiencing the very same error ...

try make V=1 for more verbose messages, but it does look like you need a more recent binutils. i know that 2.17 works fine here.

PaX Team wrote:

aldee wrote:Well, I did run make oldconfig after copying over the .config and was still experiencing the very same error ...

try make V=1 for more verbose messages, but it does look like you need a more recent binutils. i know that 2.17 works fine here.

Thanks. I'll try this if it still fails after upgrading to etch in January (I don't think it will, though :-).

JFTR: as expected, binutils 2.17 took care of it (2.15 worked up to 2.6.18-grsec). Thanks again.