Bug 387877 – sys-kernel/hardened-sources-3.0.4-r2 fails to compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Vicente Olivert Riera (RETIRED) 2011-10-20 15:44:15 UTC]

This is the error:

  LD      block/built-in.o
  CC      grsecurity/grsec_chdir.o
  CC      grsecurity/grsec_chroot.o
  CC      grsecurity/grsec_exec.o
  CC      grsecurity/grsec_fifo.o
  CC      grsecurity/grsec_fork.o
  CC      grsecurity/grsec_mount.o
  CC      grsecurity/grsec_sig.o
  CC      grsecurity/grsec_sysctl.o
  CC      grsecurity/grsec_time.o
  CC      grsecurity/grsec_tpe.o
  CC      grsecurity/grsec_link.o
  CC      grsecurity/grsec_pax.o
  CC      grsecurity/grsec_ptrace.o
  CC      grsecurity/grsec_sock.o
  CC      grsecurity/grsec_disabled.o
  LD      grsecurity/built-in.o
grsecurity/grsec_disabled.o: In function `gr_is_capable':
grsec_disabled.c:(.text+0x10): multiple definition of `gr_is_capable'
grsecurity/grsec_exec.o:grsec_exec.c:(.text+0x0): first defined here
grsecurity/grsec_disabled.o: In function `gr_is_capable_nolog':
grsec_disabled.c:(.text+0x20): multiple definition of `gr_is_capable_nolog'
grsecurity/grsec_exec.o:grsec_exec.c:(.text+0x10): first defined here
make[1]: *** [grsecurity/built-in.o] Error 1
make: *** [grsecurity] Error 2

[Comment 1 Vicente Olivert Riera (RETIRED) 2011-10-20 15:51:19 UTC]

Created attachment 290375 [details]
.config

This is the .config file I have used to compile the kernel.

[Comment 2 Anthony Basile 2011-10-20 23:14:20 UTC]

Thanks for reporting.  I never thought of testing these kernels with grsec off.  I can confirm this is a problem.

Can you please test 3.0.4-r3 with your config and see if it clears the problem.  There are are few changes which I think might fix the problem in -r3 or -r4

#
# Grsecurity
#
# CONFIG_GRKERNSEC is not set

[Comment 3 Vicente Olivert Riera (RETIRED) 2011-10-21 12:15:14 UTC]

(In reply to comment #2)
> Thanks for reporting.  I never thought of testing these kernels with grsec off.
>  I can confirm this is a problem.
> 
> Can you please test 3.0.4-r3 with your config and see if it clears the problem.
>  There are are few changes which I think might fix the problem in -r3 or -r4
> 
> #
> # Grsecurity
> #
> # CONFIG_GRKERNSEC is not set

3.0.4-r3 doesn't work, but 3.0.4-r4 yes.

[Comment 4 Vicente Olivert Riera (RETIRED) 2011-10-21 12:31:48 UTC]

atom ~ # uname -r && zgrep CONFIG_GRKERNSEC /proc/config.gz 
3.0.4-hardened-r4
# CONFIG_GRKERNSEC is not set

[Comment 5 Anthony Basile 2011-10-21 19:10:27 UTC]

(In reply to comment #4)
> atom ~ # uname -r && zgrep CONFIG_GRKERNSEC /proc/config.gz 
> 3.0.4-hardened-r4
> # CONFIG_GRKERNSEC is not set

Thanks, it may be premature but I think I'm going to have to stabilize it and punt -r1 through -r3.  I'll do that tomorrow.  I want to make sure I'm not trading one problem with another.

[Comment 6 Anthony Basile 2011-10-23 11:58:17 UTC]

Stabilized hardened-sources-3.0.4-r4 on amd64 and x86.  Please reopen if this is still a problem.