From owner-freebsd-stable@freebsd.org Wed Jan 11 22:20:17 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B59C8CABF2F for ; Wed, 11 Jan 2017 22:20:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wj0-x232.google.com (mail-wj0-x232.google.com [IPv6:2a00:1450:400c:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ACCD105B for ; Wed, 11 Jan 2017 22:20:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wj0-x232.google.com with SMTP id ew7so910247wjc.3 for ; Wed, 11 Jan 2017 14:20:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bHUSbFB9yXYKMUZ1qmkwKY8DOPZ+IK0wUqdznXLnTzg=; b=G1q+FUuRGYP2mFdsRQC1WSfvpMO8umAZc5b/SoFlrhno/MDxYsHfaS5KM4ylQ2/sP5 +g5aPfkJ0jCc+3IMHrlJH3r/IaLDLqOxyLdnaWYjhCeIcpe8CJOQk4wAagxf1vU8cRWL IQeUO+kBXBmp+PP0QLJ4eXg2phkZOcOYtkd0kSMZ/zqxtASGa82zBSE1BRwZ7SbOh/nK ggvCR5KBwThh4hrxaKUte568gs0amrR/Hvx+SNl2Bg+JFeLWue2CRtpd2ZOmOVLpwthh yHXrKe+74yIo+6JtK+9c0YHimaeV+wXZuHM5I0gLvoZd0azf96TAXtiwXbb0IloEwOfv 01hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=bHUSbFB9yXYKMUZ1qmkwKY8DOPZ+IK0wUqdznXLnTzg=; b=IvCrnSj3LUqK00wBHkI6bEba04doqpdEZeur0cLwbOBTo7D/gB0PrUXkSgeJiO/QxH v48uiELNAhbpUYsd4wuIJQShrITsgAWUj7CXfNayLlTqTrDUM4SvUZJH9f7UA1xWkiCA yfguMYLzLrmvU4QZwA43djT6+3oju6YePms+tp2q+FeXdg/OkLNX3yu945pSDUd+VKs9 O8+re/eXTnQQsCM1vmpcurQgygKfv+hHV1KkKeKGzwBrSM/eT8MFXplEIw6D3BJY9Kiu dF0qJttVEeTgGSwr7xmcgxtSdWn+8po5TXmSFRjhGDlkbCk+IczxKkERmJXXEyo8RTqz L3PQ== X-Gm-Message-State: AIkVDXKfAOJCjylzY0tJBi/yJrpN+EvsylYVi3rCaPWiHtp4Sr8v1jOJ4KDsLkCTAd3D8alYrT+7UEz4x13Ddg== X-Received: by 10.194.93.37 with SMTP id cr5mr6455867wjb.95.1484173215513; Wed, 11 Jan 2017 14:20:15 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.51.78 with HTTP; Wed, 11 Jan 2017 14:20:14 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Wed, 11 Jan 2017 14:20:14 -0800 X-Google-Sender-Auth: lqhbXz9-txNeno2pETMQUjaPw_U Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: George Mitchell Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jan 2017 22:20:17 -0000 On Wed, Jan 11, 2017 at 12:24 PM, George Mitchell wrote: > After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > *** Error code 1 > > Stop. > make[4]: stopped in /usr/src/lib/libc > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > freebsd-version -ku > 10.3-RELEASE-p13 > 10.3-RELEASE-p15 > > I am using a generic kernel, except for using SCHED_4BSD. If it > weren't for that, I would just use freebsd-update. > > Googling suggests that my build tree is somehow mixing up 32 and 64 > bit files. (I'm running on an amd64 machine.) How do I get this > cleared up? -- George > While I have no suggestions about the error building libc, your statement that you can't use freebsd-update due to your use of a custom kernel is incorrect. This is a common misconception and, in cases of very limited disk space, may be true, it is rare. It is helped by the fact that the man page makes no mention of how to so this. (You do still need to build a new kernel if the update does, indeed, touch the kernel.) All you need is a GENERIC kernel in /boot/GENERIC. You can either build it or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCustom = Kernels with FreeBSD 9.X and Later=E2=80=9D for details on downloading a GENERIC kernel. Before any upgrade, major or minor, you might wat to re-reas that section. Once the GENERIC kernel is in /boot, you may use freebsd-update and, if the GENERIC kernel is not updated, you're good to go. If it is, you will need to build and install a new custom kernel and reboot. Since most security patches don't touch the kernel, this is usually not needed. I believe that the 10.3 kernel was last touched in p11. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683