From owner-freebsd-stable@FreeBSD.ORG Wed Mar 14 15:41:29 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D187E1065672 for ; Wed, 14 Mar 2012 15:41:29 +0000 (UTC) (envelope-from garbytrash@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED838FC0A for ; Wed, 14 Mar 2012 15:41:29 +0000 (UTC) Received: by ghrr20 with SMTP id r20so2377497ghr.13 for ; Wed, 14 Mar 2012 08:41:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V5dFqRX/scVWt8ACPeX4yYm6YK2g05JoOv4PR3GPOVw=; b=d5fkBbeudZvZLK1Minl3ajWdNT+xvjfvICalY8oKmbThKOdtPFPIlLxMXb13Xsv7Qq 2zMBTlNAvJAap3x/BXv/8blqQ3CY0cdxl6V6AxbkC+h0kwnPt1rse5jFl/r9KX6qP3R0 kZzUPg8mSgpHaG78SaahMJkInU70BxzdUqPtl7aCZLLHOkFHw1CNHFaDgzae2Je/bMYd BeTqHqYN7oGOm+zO5b7L55uohvZy5BLbGZeFKIwLK3UbC7iKpw/EgN/qSlRDRrec6y47 Vp3JOFlgT16WUfVSCtUWIDoh98GuzK92bnI6/Ht0dLGzscuQ7b4z2f3weBc3IGW04Fcr H51A== MIME-Version: 1.0 Received: by 10.60.4.105 with SMTP id j9mr3979652oej.29.1331739683273; Wed, 14 Mar 2012 08:41:23 -0700 (PDT) Received: by 10.60.17.34 with HTTP; Wed, 14 Mar 2012 08:41:23 -0700 (PDT) In-Reply-To: <8376649595D34EDE8E160990C9FBD8CB@white> References: <7EEACF9CCF91415895F77A26C954F154@white> <8376649595D34EDE8E160990C9FBD8CB@white> Date: Wed, 14 Mar 2012 15:41:23 +0000 Message-ID: From: Zenny To: Dewayne Geraghty Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: NanoBSD compilation problem with 9-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 15:41:29 -0000 On 3/13/12, Dewayne Geraghty wrote: > Thinks aren't looking good. I've had this problem a few years ago when > first using nanobsd. I was chasing the problem until in the end I removed > all exclusions from the build, and then added exclusions (WITHOUT_...) > until something broke, which revealed the problem. This could take awhile. > > To my casual eye, the issue seems to be related to the RC4 algorithm which > might point to a problem with openssl. I don't have access to any freebsd > machines for the next two days (I'm in transit). At a guess you might need > to either: > A) enable the RC4 algorithm in the openssl build, though I think its on by > default or > B) review the src.conf file for anything with WPA_SUPPLICANT* and add that > to your "WITHOUT_" list; at least until you've gotten one complete build > under your belt. Thanks for your input. Yep, that seemed working with a few things that I did: 1) removed all source and ports and csup/portsnap them 2) In the src.conf file, I figured out that disabling WPA_SUPPLICANT (#WITHOUT_WPA_SUPPLICANT=true") is preventing the build world. 3) In the kernel file, I have to change from COMPAT_IA32 to COMPAT_FREEBSD32 (the former is obsoleted in FreeBSD9-RELEASE) to complete the build kernel. BTW, I am just wondering where and how to specify any kernel patches to be applied to a nanobsd image? Could not figure out any documentation. > > It's tricky business getting the build the way that you'd like it, but once > achieved, you'll be knowledgeable with your result. > > Things to note: WITHOUT_ENCRYPTION have undocumented side-effects like not > building geli, nor libarchive - don't use this knob; and WITHOUT_OBJC will > cause problems that took me lot of time to identify. Thank you for the pointers. > > Good luck. > > Kind regards, Dewayne. > > > >