Page 1 of 1

compilation error - all grsecurity-2.2.2-3.0.3

PostPosted: Mon Aug 29, 2011 9:02 am
by blablo
Code: Select all
  CC [M]  arch/x86/platform/iris/iris.o
  LD      arch/x86/platform/mrst/built-in.o
  CC      arch/x86/platform/olpc/olpc.o
  CC      arch/x86/platform/olpc/olpc_ofw.o
  CC      arch/x86/platform/olpc/olpc_dt.o
arch/x86/platform/olpc/olpc_dt.c:159:26: error: prom_olpc_ops causes a section type conflict
make[3]: *** [arch/x86/platform/olpc/olpc_dt.o] Error 1
make[2]: *** [arch/x86/platform/olpc] Error 2
make[1]: *** [arch/x86/platform] Error 2
make: *** [arch/x86] Error 2


distro: arch linux (32 bit)
gcc: gcc-4.6.1-4
kernel: linux-3.0.3 (vanilla)
grsec: grsecurity-2.2.2-3.0.3-201108281458.patch

Kernel compiles without a grsecurity patch.
Thanks

Re: compilation error - all grsecurity-2.2.2-3.0.3

PostPosted: Mon Aug 29, 2011 6:42 pm
by PaX Team
blablo wrote:[code]arch/x86/platform/olpc/olpc_dt.c:159:26: error: prom_olpc_ops causes a section type conflict
that struct needs to be __no_const, the next patch will fix it, thanks.

Re: compilation error - all grsecurity-2.2.2-3.0.3

PostPosted: Tue Aug 30, 2011 2:46 am
by blablo
I checked and still is a error.

Code: Select all
  CC [M]  arch/x86/platform/iris/iris.o
  LD      arch/x86/platform/mrst/built-in.o
  CC      arch/x86/platform/olpc/olpc.o
  CC      arch/x86/platform/olpc/olpc_ofw.o
  CC      arch/x86/platform/olpc/olpc_dt.o
arch/x86/platform/olpc/olpc_dt.c:166:3: error: expected ‘,’ or ‘;’ before ‘__attribute__’
make[3]: *** [arch/x86/platform/olpc/olpc_dt.o] Error 1
make[2]: *** [arch/x86/platform/olpc] Error 2
make[1]: *** [arch/x86/platform] Error 2
make: *** [arch/x86] Error 2


kernel: linux-3.0.4 (vanilla)
grsec: grsecurity-2.2.2-3.0.4-201108300001.patch

thanks

Re: compilation error - all grsecurity-2.2.2-3.0.3

PostPosted: Tue Aug 30, 2011 9:08 am
by blablo
grsecurity-2.2.2-3.0.4-201108300622.patch works, thanks

Re: compilation error - all grsecurity-2.2.2-3.0.3

PostPosted: Tue Aug 30, 2011 9:14 am
by PaX Team
blablo wrote:I checked and still is a error.
yeah because the attribute must be on the type, not the variable, next patch will get it right ;).