From owner-freebsd-current@FreeBSD.ORG  Fri Dec 20 23:46:56 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 509E454E
 for <freebsd-current@freebsd.org>; Fri, 20 Dec 2013 23:46:56 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C29811532
 for <freebsd-current@freebsd.org>; Fri, 20 Dec 2013 23:46:55 +0000 (UTC)
Received: from ASUS ([89.217.96.112]) by mail.gmx.com (mrgmx103) with ESMTPSA
 (Nemesis) id 0M0yaB-1VeHRT2ljz-00vC8c for
 <freebsd-current@freebsd.org>; Sat, 21 Dec 2013 00:41:40 +0100
From: "Stefan Hegnauer" <stefan.hegnauer@gmx.ch>
To: "'Adrian Chadd'" <adrian@freebsd.org>,
	<pjd@freebsd.org>
References: <52b4ac88.e9e4340a.5ce3.22feSMTPIN_ADDED_BROKEN@mx.google.com>
 <CAJ-VmonptCt1J0E9ECjD=PQppJht3sgOjLrR5Pe-x07T=D0R-Q@mail.gmail.com>
In-Reply-To: <CAJ-VmonptCt1J0E9ECjD=PQppJht3sgOjLrR5Pe-x07T=D0R-Q@mail.gmail.com>
Subject: PR bin/185052 filed (was: RE: nanobsd build failure
 'WITHOUT_CASPER=YES' r259661 and earlier)
Date: Sat, 21 Dec 2013 00:41:40 +0100
Message-ID: <000301cefddd$083cb8c0$18b62a40$@hegnauer@gmx.ch>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac79xUPolWbLRNu8SH6c+f9lftFWigAFro8w
Content-Language: de-ch
X-Provags-ID: V03:K0:R3gFQfPvYf8lyCL3mm4I+WDah8evMwOSTZN7lhpOA/dLmkS3VuD
 ksnQC7BrIpg+aldQc0YwA50jrJy8jHW/bv1WJwck4r+NtQWwpqOMsRbIJK4VAy7cOxCECLk
 Rh6P75e5ns8T5x+AUbnHvRcd+fAJzyQPw5iZ8HD3OWnrkdQeMzk2pW8iUi7aroX28v7ovst
 xyQekgiDxTe2sVAsr0x7A==
Cc: 'freebsd-current' <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2013 23:46:56 -0000

Hi there, 

thanks for your support. PR 185052 is filed and should be visible soon -
please let me know if I can help in any way (more info, testing, whatever).

Thanks again
Stefan

> From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf
> Of Adrian Chadd
> Sent: Friday, December 20, 2013 9:52 PM
> To: Stefan Hegnauer
> Cc: freebsd-current
> Subject: Re: nanobsd build failure 'WITHOUT_CASPER=YES' r259661 and
> earlier
> 
> Hi,
> 
> Please file a PR and then ask the developer (pjd@) very nicely to take
> a look at it.
> 
> Thanks,
> 
> 
> -adrian
> 
> 
> On 20 December 2013 12:45, Stefan Hegnauer <stefan.hegnauer@gmx.ch>
> wrote:
> > When using 'WITHOUT_CAPSICUM=YES', 'WITHOUT_CASPER=YES' my nanobsd
> builds in
> > a Virtualbox VM (i386, march=geode, GENERIC without debug+Witness et.
> al.)
> > fail buildworld for any revision from at least r259518-r259661; like
> so
> > (this example is r259661):
> >
> >
> >
> > " ...
> >
> > ===> lib/clang/libllvmsupport (obj,depend,all,install)
> >
> >
> /usr/obj/nanobsd.sstream//usr/src/tmp/usr/src/lib/clang/libllvmsupport
> > created for /usr/src/lib/clang/libllvmsupport
> >


snip - see PR for details ...


> >
> > make: stopped in /usr/src"
> >
> >
> >
> > Note that this is with PMAKE="-j1", i.e. single threaded build (same
> happens
> > with standard PMAKE=-j3 but slightly less intuitive to see where it
> fails)
> >
> >
> >
> > Removing WITHOUT_CASPER=YES in the build instructions cures the
> problem (!),
> > however I fail to see why I should include it for an embedded device
> > (pcengines.ch Alix boards, several different versions).
> >
> > Also, with the error reported above I have the impression it is not
> exactly
> > intuitive that you have to include CASPER (and not CAPSICUM) to
> eliminate
> > the failure?
> >
> > Any pointers/hints/solutions?
> >
> >
> >
> > Sorry for the rant & thanks
> >
> > Stefan
> >
"