Date: Sun, 19 Apr 2009 00:00:20 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Takahashi Yoshihiro <nyan@jp.FreeBSD.org> Cc: current@freebsd.org Subject: Re: Making release is broken Message-ID: <49EACC04.7030101@freebsd.org> In-Reply-To: <20090419.134137.229119706.nyan@jp.FreeBSD.org> References: <20090419.121350.258482423.nyan@jp.FreeBSD.org> <49EA9DDF.5040500@freebsd.org> <20090419.134137.229119706.nyan@jp.FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Takahashi Yoshihiro wrote: > In article <49EA9DDF.5040500@freebsd.org> > Tim Kientzle <kientzle@freebsd.org> 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, Timhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49EACC04.7030101>