From owner-freebsd-current@freebsd.org Wed Jan 18 23:32:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 875CCCB51B0 for ; Wed, 18 Jan 2017 23:32:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EA4B1C45 for ; Wed, 18 Jan 2017 23:32:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id 203so129143662ith.0 for ; Wed, 18 Jan 2017 15:32:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vcgjKKpbgLOkaZOKJH/mnU/DsVYgVeNbj3skT+f/VJc=; b=Yq6vV00PDljboVP42mwufnbsQVLpenQ3D0KFWG+Tb70n1HhGfwErsA9g5Eq4q3LzsI sX9XPSQ/mGoagDo5muK7zdaqjAeHEk60kb292uCF55YHTWJmCXQRbvPrn5dEUONxZRVr kRinE/aCSvxH5IcomTIp3eiGIQb5R0U4tDCxCHnLjwQqyrPcKqaCWPZGol/bXPdl4Q95 yqMW5ROzxDlC8+aYxptrojHcxIrQ7MYpoceLEvfz+GQgdy/ne8+fQdc8tc4m69Bg1Ldh sYUBx0TR+qWufOdwC3SfoGVmwf+trz3g/EAjx2HVvmH8lnWxT/DJdQ52wwNGHVDrJLCC lqXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vcgjKKpbgLOkaZOKJH/mnU/DsVYgVeNbj3skT+f/VJc=; b=bbm94q+xPQmomPoHGHKoC9gI3CKX7m59WHfeEMtSbMOjiX0MUiev8Ei8X3Ee32u7EG bZRF3liOuMjdxZY6OCKeiLYqvhamTaiHfnRzioR0X95TDEJ4r7Ljb3G885CVVXdNR7oo Kf5mQ1JFauqADsDWLbfDr78IOV93njEKKLLwWeCqoRf7raNAogOof7cku1ioc9fLkepR 5lvlKqFr/BK8ddjD3359McS+S3gfIam5EZyxh7H0zOIczztPPtYNclT2VUKzB/G0Cb0I ZvXVqWLjZP+nmWv6Q+HPJH+KiL6PF2XIi0JS94IHK7SjJiFaJOJ43YCvJ4F96afpeZOH 7CGQ== X-Gm-Message-State: AIkVDXIrUbRYfbn1OW9CCUm2h2l1F2fBo0nN4T2Vbb84dixkDYTTSZ6D0wt8O7w7bj6LRhl1zbKTG7ih+1r/Gw== X-Received: by 10.36.20.66 with SMTP id 63mr5666074itg.103.1484782373627; Wed, 18 Jan 2017 15:32:53 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.145.217 with HTTP; Wed, 18 Jan 2017 15:32:53 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <5b6f9e49-09db-6329-4176-3898886ceb61@selasky.org> <8D312F2F-63D9-4269-9E7B-83978F53C1AE@FreeBSD.org> <11db64df-356e-1005-7fd4-b825bee3ac8f@selasky.org> From: Warner Losh Date: Wed, 18 Jan 2017 16:32:53 -0700 X-Google-Sender-Auth: Br5fs8j6Gf4C-LNm6DXV-135lpU Message-ID: Subject: Re: Build failure 'wmmintrin.h' file not found To: Dimitry Andric Cc: Magnus Ringman , Hans Petter Selasky , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 23:32:54 -0000 On Wed, Jan 18, 2017 at 1:21 PM, Dimitry Andric wrote: > On 18 Jan 2017, at 14:42, Magnus Ringman wrote: >> >> On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky >> wrote: > ... >>> And the error popped out. I'm not observing this error when building a >>> 12-current kernel from an 11-stable install. >> >> >> Isn't it all bets are off if going to -current from anything but most >> recent -stable? Nope. There's a range of supported major branches. This has been the case for at least 15 years. Typically, we've supported 2-4 old branches building current due to the needs of the FreeBSD community and that community making sure it works often enough that we don't just shut the door to it entirely. Each individual developer only needs to test the latest branch, but that's not the same as what's supported. From time to time we bump the minimum system, but it isn't in lock step with the major branches. >> Recommended practice[citation needed] would be >> 10-stable->11-stable->12-current. > > That is the safest way, indeed. But it should not be totally impossible > to build recent versions of -current on 10.x. We support building world on 10.3 and newer for -current today. There were compiler changes to fix bad code generation between 10.2 and 10.3, however, so the usual "any stable-10' is no longer the case. In fact, it's still supported building from the tip of stable/9 for current. However, the same compiler bug is not fixed in the last 9.x release, so there the upgrade is needed. > Normally, buildworld takes care of the heavy lifting by building all the > needed tools first. But if you build only parts of the tree, you might > encounter "interesting" situations. :) Anything less than buildworld is defintely not supported when the host system isn't completely up to date. Well, make kernel-toolchain is sufficient for make buildkernel. Warner