From owner-freebsd-ppc@freebsd.org Mon Jun 26 02:34:15 2017 Return-Path: Delivered-To: freebsd-ppc@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 C1F33D9F4A8 for ; Mon, 26 Jun 2017 02:34:15 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9C1CA16D2 for ; Mon, 26 Jun 2017 02:34:15 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9884ED9F4A6; Mon, 26 Jun 2017 02:34:15 +0000 (UTC) Delivered-To: ppc@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 982CBD9F4A5 for ; Mon, 26 Jun 2017 02:34:15 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 535B316CB; Mon, 26 Jun 2017 02:34:15 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qk0-x234.google.com with SMTP id 16so68788081qkg.2; Sun, 25 Jun 2017 19:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=Dv6008c6JNh3k9CqVo0S5JZtlpSGlt7l22AYQOw5/CA=; b=i3IP7wftp63OZcCc4jFLRDlc/xb6ZZIy9W4ZYD/rnE6qboXnkFGyaSDXLI8IHmv2uf boe0nDLU/tdiKqFdtMgcNAJUQwkQJ4TBddK4MHuF3yiIz5XJal0TFQZZ1BRlieychIuo u/qb7P0uJXfn+ZNZVzv+m9GblC0mmMPIA6pJT3XO6SsQFDN8gZsYH8aAoJBX3jeFzlNt pfJZleYWMxh+f0DBEmiloljTJEaEmMteWz6pRcKkrQ3IENwVg7NiAPONa8dhSNXzgiYK fnwdQVzdlPQ3LmOukXEH7gZNWVzRmN36e9suE2W65BlekOPS5iPtDAA/+INzc0ocU3AE NftA== 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:from:date:message-id:subject :to:cc; bh=Dv6008c6JNh3k9CqVo0S5JZtlpSGlt7l22AYQOw5/CA=; b=klBXG6Jb7/Tx/BbpA/sinCk4+4YiXFyHAZeZ2wBvg9BNNLW5QIDdQm99oGP4BjNSUC Hb01vHROim+qkgY2QbSeTv56JZ5b9bj8wgHfciE0mtmxhI1Pbu0lnasPE/ZfkZk3KG9o EgnYxE9JHfEB5vwiir7pz/IMnALVmo7lSdZpC0iNc6hMtvPnS/6jc4alwaDALZbejFaR hc2++RqcCSBgyEmXA8iiBeT0Yz0LvVsOCij+NbV4pklMvBAKbQcSqcrsd7M44nvbs6yB ITl/U54FUoQYOGcjJ/+bTKfQF2TRyaa6VlCmwqzGJf1EtZ2/Eijima3jz5ab1vRMSo81 XEbg== X-Gm-Message-State: AKS2vOxJkceZf2axLI3Xd9yPCy6fEHhQ+SzKITjiLAKLYSHvhzOP0eVC IQzqHeJA1uMYYi+UMsTGiS7bewqEfA== X-Received: by 10.55.95.194 with SMTP id t185mr20819643qkb.119.1498444454202; Sun, 25 Jun 2017 19:34:14 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.183.143 with HTTP; Sun, 25 Jun 2017 19:34:13 -0700 (PDT) From: Justin Hibbits Date: Sun, 25 Jun 2017 21:34:13 -0500 X-Google-Sender-Auth: jqokDxGLFWNn1NTY43ALULR4JBk Message-ID: Subject: r320347: ABI breakage for 32-bit powerpc, introduction of 64-bit time_t To: ppc@freebsd.org Cc: FreeBSD Release Engineering Team Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 02:34:15 -0000 Hi all, Thanks to the testing by Andreas Tobler, and others, 32-bit powerpc targets (powerpc.powerpc, powerpc.powerpcspe) now use a 64-bit time_t. This is a significant ABI breakage, and as such should be handled with care. For one, live in-place updates cannot be done. You must install via an alternate root. Additionally, all ports, and any local binaries, must be recompiled with the new ABI, or bad/strange/bizarre things could happen. The safest route is to perform a clean install. Second to that, the following procedure could be used to perform an upgrade: * Boot to an alternate medium (CD, DVD, memstick, temporary image on swap, or another hard drive, etc) * Mount your runtime filesystems to, e.g., /mnt * pkg remove -a on your runtime system (in chroot) * Install to /mnt * Rebuild all ports * Reboot to new y2038-safe system - Justin