From owner-freebsd-current@FreeBSD.ORG  Tue Aug 28 19:51:32 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 041B1106566B;
	Tue, 28 Aug 2012 19:51:32 +0000 (UTC)
	(envelope-from eirnym@gmail.com)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com
	[209.85.210.182])
	by mx1.freebsd.org (Postfix) with ESMTP id B20C18FC1A;
	Tue, 28 Aug 2012 19:51:31 +0000 (UTC)
Received: by ialo14 with SMTP id o14so14629745ial.13
	for <multiple recipients>; Tue, 28 Aug 2012 12:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	bh=oN8QvmnMpeChRvmP5vUngWS0R6wfZ+8/M5tRO5UBJ+k=;
	b=mGGnlzQwwZFlDSgY7DTbBATPJScglHKql3f2ILlYyp93nYsVwalnDwoWdvgbBXVokc
	z9eBuykvtEffJBktPiZX0O6tOWyNkGPEWYqsdmyYrPXlVbsbFaS3zgLscf5a94P2Lbyp
	vAkDcKu7iHn64FhAAx3k1DXKU5R+ff7k1+4xd9AW8o68sYZLE1qqsabUzOQmdBolphDw
	yeLFTaUJbRPdbVJvHFVDsrVq8Hh22dkzsk7BAh7vBR1DKhC/R77uNoisYX78h0WXNs7F
	93rd3/aegQYJf2L/2BwlEM9uLW3lWoeg1M4s33T+Q8WEyQ5WHLNJiJTohP0cHbefqqZ4
	jrAw==
Received: by 10.50.187.233 with SMTP id fv9mr15192098igc.59.1346183491254;
	Tue, 28 Aug 2012 12:51:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.46.41 with HTTP; Tue, 28 Aug 2012 12:51:10 -0700 (PDT)
In-Reply-To: <503D12CB.4000208@FreeBSD.org>
References: <CAO8GK0pQCqAJ--NkfXm+c7+s-_REGA3b4+Jgao4pmE9gCo_qzA@mail.gmail.com>
	<503D12CB.4000208@FreeBSD.org>
From: Eir Nym <eirnym@gmail.com>
Date: Tue, 28 Aug 2012 23:51:10 +0400
Message-ID: <CAO8GK0qHZPnpCa0zBiXYtghObAmsoe+zkd0tDMQ=2VWdX_8JMg@mail.gmail.com>
To: Dimitry Andric <dim@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD Mail Lists <freebsd-current@freebsd.org>
Subject: Re: Can't build FreeBSD-head with CLANG
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 19:51:32 -0000

-- Eir Nym


On 28 August 2012 22:49, Dimitry Andric <dim@freebsd.org> wrote:
> On 2012-08-28 18:31, Eir Nym wrote:
>>
>> I can't build FreeBSD (GENERIC & custom kernel) with clang. Build
>> finishes for i386 and fails for amd64 for same kernels
>
>
> What is the error you were getting on amd64?
>
>
i386 never failed, amd64 =E2=80=94 always
>
>> I have bsd box with following clang version:
>>>
>>> FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
>>> Target: x86_64-unknown-freebsd10.0
>>> Thread model: posix
>
>
> This is rather old, we went through clang 3.1 some time ago, and
> recently updated it to 3.2.
>
>

I use to be sure I use latest clang
make kernel-toolchain buildkernel ${other_args}

>
>> I try to compile it with /dev/null as make.conf and following src.conf:
>
> ...
>
>> but I constantly get warnings (not long ago they was errors) in kernel
>> like this:
>> /usr/head/src/sys/netgraph/ng_parse.c:1263:14: warning: comparison of
>> unsigned expression < 0 is always false [-Wtautological-compare]
>>                          if (index < 0 || eptr - (s + *off) !=3D len) {
>>                              ~~~~~ ^ ~
>> 1 warning generated.
>>
>> Also I get not initialized warnings and so on.
>
>
> You can safely ignore those.  They are just an incentive for the
> maintainers to fix them eventually.  Those tautological comparison
> warnings specifically are quite harmless: the compiler will optimize the
> unused code away anyhow.

I know about ignorance, but compiler fails at them.