From owner-freebsd-current@freebsd.org  Sat Jul 14 10:15:11 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF1B61049EA8;
 Sat, 14 Jul 2018 10:15:11 +0000 (UTC)
 (envelope-from ronald-lists@klop.ws)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl
 [195.190.28.92])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 84E9073F92;
 Sat, 14 Jul 2018 10:15:09 +0000 (UTC)
 (envelope-from ronald-lists@klop.ws)
Received: from smtp.greenhost.nl ([213.108.110.112])
 by smarthost1.greenhost.nl with esmtps
 (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2)
 (envelope-from <ronald-lists@klop.ws>)
 id 1feHZz-00068w-Rh; Sat, 14 Jul 2018 12:15:08 +0200
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "Dimitry Andric" <dim@freebsd.org>, "Mark Millard" <marklmi@yahoo.com>,
 tech-lists <tech-lists@zyxst.net>
Cc: freebsd-arm <freebsd-arm@freebsd.org>, "FreeBSD Current"
 <freebsd-current@freebsd.org>, "FreeBSD Toolchain"
 <freebsd-toolchain@freebsd.org>
Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3
References: <A7BBACBB-44A1-4F95-B4F6-498B72238FC5@yahoo.com>
 <a8cc68ec-e87d-9133-7ad9-59c5b42ed749@zyxst.net>
 <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com>
 <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org>
 <b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367@zyxst.net>
Date: Sat, 14 Jul 2018 12:15:07 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Ronald Klop" <ronald-lists@klop.ws>
Message-ID: <op.zl4z3hr7kndu52@klop.ws>
In-Reply-To: <b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367@zyxst.net>
User-Agent: Opera Mail/12.16 (FreeBSD)
X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Spam-Level: /
X-Spam-Score: -0.2
X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED,
 BAYES_50 autolearn=disabled version=3.4.0
X-Scan-Signature: 523f42b60907f92a5b98f162865e3e4b
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2018 10:15:11 -0000

On Fri, 13 Jul 2018 12:15:22 +0200, tech-lists <tech-lists@zyxst.net>  
wrote:

> On 12/07/2018 19:32, Dimitry Andric wrote:
>> No, it's because sys/crypto/armv8/armv8_crypto_wrap.c includes
>> <arm_neon.h>, an intrinsics header, which in turn requires <stdint.h>.
>>  This was introduced inhttps://svnweb.freebsd.org/changeset/base/308921,
>> and at the time resulted in similar build failures, specifically when
>> one attempted to build a new kernel, without building world or a new
>> toolchain first.
>
> Hi,
>
> Ok, it's finished building and installing. The command I used was this:
>
> # make -j10 buildworld && make -j10 buildkernel KERNCONF=RPI3

What is RPI3? Mine runs GENERIC and there is no RPI3 config in  
/usr/src/sys/arm64/conf. I can find RPI2 in sys/arm/conf.

Regards,
Ronald.