Date: Tue, 31 Mar 2015 19:28:17 -0700 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: John-Mark Gurny <jmg@freebsd.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: Kernel compilation failures with gcc 4.9 Message-ID: <CAG=rPVfH6hvH9OSf4nM5fk-q0yqVUs8aRfxLEu20F1ikXYd06g@mail.gmail.com> In-Reply-To: <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> References: <CAG=rPVfA3fVQ__XoBewKh0u0buO9NNt6uB4Yv9EUy2Rn8H%2B2Yw@mail.gmail.com> <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 31, 2015 at 4:55 PM, Warner Losh <imp@bsdimp.com> wrote: > > > > > It shouldn't be using the stdlib when it's built with -ffreestanding or > -nostdlib. Can you make sure? > > The AES stuff breaks the rules, and this is a consequence of it :( That > stuff should be fixed. > > John-Mark, Do you have time to help fix compilation with gcc 4.9 of AESNI in the kernel? It currently does not compile with gcc 4.9. See my original bug report here: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001577.html We are trying to fix the kernel build enough with gcc 4.9 so that we can at least set up a Jenkins continuous build (with -Werror turned off initially). Thanks. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVfH6hvH9OSf4nM5fk-q0yqVUs8aRfxLEu20F1ikXYd06g>