From owner-freebsd-arch@freebsd.org Mon Oct 9 19:57:01 2017 Return-Path: Delivered-To: freebsd-arch@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 3653DE3A83B for ; Mon, 9 Oct 2017 19:57:01 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 199F17D34F; Mon, 9 Oct 2017 19:57:00 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id D6571AF1; Mon, 9 Oct 2017 14:56:53 -0500 (CDT) Date: Mon, 9 Oct 2017 14:56:52 -0500 From: Mark Linimon To: Nathan Whitehorn Cc: Warner Losh , "freebsd-arch@freebsd.org" , swills@FreeBSD.org Subject: status of powerpc64 (was: Making C++11 a hard requirement for FreeBSD) Message-ID: <20171009195652.GA28957@lonesome.com> References: <2116882.XEKuxOb729@ralph.baldwin.cx> <20171006072010.ygq3k5ygwxykk4nb@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 19:57:01 -0000 On Mon, Oct 09, 2017 at 10:47:13AM -0700, Nathan Whitehorn wrote: > - There are no binary packages built for PPC64, because of project policy > preventing the use of native build systems I don't think this is 100% correct. Although I am no longer on portmgr and thus don't work on the details, my understanding is that: - "official" FreeBSD packages can only be issued from machines that are under the exclusive control of FreeBSD.org - the powerpc64 machine that falls under that category is not yet reliable enough The first is a security concern. The odds of that policy changing are about the same as Elvis doing another concert. IIUC the second is because we run package builds under virtualization on freebsd.org's powerpc64 machine, and hit memory contstraints often enough to make it "not quite ready for production". You would have to ask swills@ whether the latter is still true. My own powerpc64 builds are constrained for other reasons[*]. When I get back from my current road trip I am willing to build and make available a subset of powerpc64 packages on the same basis I currently do for sparc64, if that will help the situation. > - You cannot cross-compile packages for PPC64, because of limitations > in QEMU s/limitations/a bug/ qemu/powerpc64 simply hangs when you start it up (as does qemu/sparc64). Otherwise qemu is usable for cross-builds and is, in fact, how armv6, mips, and mips64 package builds are currently done. I know less about your other points, but, there needs to be some kind of script or wrapper around the "do a base cross-build". I had had one set up for amd64 to sparc64 as a test but got distracted before I finished. I recall it being non-trivial. mcl [*] a couple of kernel bugs which I think I know how to fix; not being able to run diskful, and power consumption