From owner-freebsd-current@FreeBSD.ORG Sun Apr 19 07:00:26 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0DE3106566C for ; Sun, 19 Apr 2009 07:00:26 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 964F28FC08 for ; Sun, 19 Apr 2009 07:00:26 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n3J70LBE048726; Sun, 19 Apr 2009 00:00:21 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id yjwqdzcte9zgwk8xn6k8pxh9f6; Sun, 19 Apr 2009 00:00:20 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49EACC04.7030101@freebsd.org> Date: Sun, 19 Apr 2009 00:00:20 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Takahashi Yoshihiro References: <20090419.121350.258482423.nyan@jp.FreeBSD.org> <49EA9DDF.5040500@freebsd.org> <20090419.134137.229119706.nyan@jp.FreeBSD.org> In-Reply-To: <20090419.134137.229119706.nyan@jp.FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Making release is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 07:00:27 -0000 Takahashi Yoshihiro wrote: > In article <49EA9DDF.5040500@freebsd.org> > Tim Kientzle writes: > >> Easiest fix is to add -lcrypto to the boot_crunch.conf. >> That would satisfy libarchive's new requirements. >> >> Alternatively, I could put conditionals on RELEASE_CRUNCH >> into cpio so that it didn't use any of the new libarchive >> features that are causing this. >> >> With a little more work, I could put together a minicpio that >> provided just the bare minimum of features required by the >> boot_crunch. >> >> Any strong preference? > > I prefer to add RELEASE_CRUNCH condition or add a minicpio to avoid > increasing a binary size. Done. r191262 adds a RELEASE_CRUNCH condition that reduces the number of libarchive features used by cpio. It should fix the problem you're seeing. Cheers, Tim