From owner-freebsd-questions@freebsd.org  Wed Mar 16 17:35:04 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@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 053C7AD3B8A
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Wed, 16 Mar 2016 17:35:04 +0000 (UTC)
 (envelope-from freebsd-questions@m.gmane.org)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BDBF9FB8
 for <freebsd-questions@freebsd.org>; Wed, 16 Mar 2016 17:35:03 +0000 (UTC)
 (envelope-from freebsd-questions@m.gmane.org)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <freebsd-questions@m.gmane.org>) id 1agFLP-0006ts-T7
 for freebsd-questions@freebsd.org; Wed, 16 Mar 2016 18:34:52 +0100
Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <freebsd-questions@freebsd.org>; Wed, 16 Mar 2016 18:34:51 +0100
Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with
 local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <freebsd-questions@freebsd.org>; Wed, 16 Mar 2016 18:34:51 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-questions@freebsd.org
From: Michael Powell <nightrecon@hotmail.com>
Subject: Re: CURRENT does not compile on i386
Date: Wed, 16 Mar 2016 13:32:43 -0400
Lines: 21
Message-ID: <ncc5fj$g6m$1@ger.gmane.org>
References: <56E2E06D.9060003@lirmm.fr>
 <20160311170731.a00a652c.freebsd@edvax.de> <56E2F181.1070600@lirmm.fr>
 <nbv5hc$vsg$1@ger.gmane.org> <56E99053.4030102@lirmm.fr>
Reply-To: nightrecon@hotmail.com
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2016 17:35:04 -0000

Pierre-Yves Péneau wrote:
[snip]
>> 
>> If you are not a kernel-hacking developer might I respectfully suggest
>> beginning with RELEASE and NOT -CURRENT?
> 
> OK I'll try with RELEASE. Thank you Mike.
> 

I believe the build may have been fixed since you experienced this. You may 
be able to refresh your source code and the trouble has passed.  This is the 
so-called "bleeding edge", so to speak.

The -CURRENT branch is where the developers 'play' with brand new code. It 
is never guaranteed to always build or even work at all. They will break 
things and they will fix things; it is an up and down roller coaster ride. 

Cordialement,

-Mike