linux-kernel - Re: Minimum toolchain requirements?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121227200933.GC14257@digium.com>
Date:	Thu, 27 Dec 2012 14:09:33 -0600
From:	Shaun Ruffell <sruffell@...ium.com>
To:	Rob Landley <rob@...dley.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Minimum toolchain requirements?

Hi Rob,

On Fri, Dec 14, 2012 at 04:25:10PM -0600, Rob Landley wrote:
> Although the README and Documentation/Changes both say the kernel
> builds with gcc 3.2, this is no loner the case. In reality the new
> 3.7 kernel no longer builds under unpatched gcc 4.2.1 (the last
> GPLv2 release).
> 
> Building for i686 breaks with
> "arch/x86/kernel/cpu/perf_event_p6.c:22: error:
> p6_hw_cache_event_ids causes a section type conflict" (trivial
> workaround: patch kernel so CONFIG_BROKEN_RODATA defaults to y).

I came across your email while searching for a solution to the above
build error.

In addition to setting CONFIG_BROKEN_RODATA=y, Jan Beulich sent a
patch [1] to LKML that also fixes this build problem for me.

[1] https://lkml.org/lkml/2012/11/23/308

It doesn't appear to have hit Linus' tree yet though, but with luck
someone will pick it up before 3.8 final.

Cheers,
Shaun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/