Date: Wed, 16 Dec 2015 08:15:38 -0800 From: John Baldwin <jhb@freebsd.org> To: "Jonathan T. Looney" <jtl@freebsd.org> Cc: Randall Stewart <rrs@netflix.com>, Ed Maste <emaste@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org> Subject: Re: svn commit: r292309 - in head/sys: modules modules/tcp modules/tcp/fastpath netinet netinet/tcp_stacks Message-ID: <1627913.WATQQLTEnG@ralph.baldwin.cx> In-Reply-To: <D296F3C9.4D82C%jlooney@juniper.net> References: <201512160056.tBG0ujqA067178@repo.freebsd.org> <1A3645F3-3287-4CD8-B69D-AC053507D435@netflix.com> <D296F3C9.4D82C%jlooney@juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, December 16, 2015 10:58:47 AM Jonathan T. Looney wrote: > On Dec 16, 2015, at 10:08 AM, Randall Stewart <rrs@netflix.com> wrote: > > Ahh I think I see this is a difference between our friend > > clang and gcc.. since I bet ppc uses gcc not clang :-o > > This sort of thing seems to happen often enough that it would be nice if > there was an option to automatically build two kernels, one with each > compiler. Is there already such an option? make tinderbox effectively does that, but at a bit more expense. amd64 doesn't build GCC 4.2 by default, so the simplest way is to build a kernel for a non-clang platform, e.g.: make TARGET=sparc64 kernel-toolchain make TARGET=sparc64 buildkernel (Note you only need to do the kernel-toolchain step once or after toolchain changes like compiler upgrades.) -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1627913.WATQQLTEnG>