From owner-svn-src-head@freebsd.org Fri Oct 16 16:53:18 2020 Return-Path: Delivered-To: svn-src-head@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2D0E643A7F6; Fri, 16 Oct 2020 16:53:18 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CCXKB0Nc0z3gPL; Fri, 16 Oct 2020 16:53:18 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id E48FB18FF4; Fri, 16 Oct 2020 16:53:17 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f173.google.com with SMTP id m9so1986118qth.7; Fri, 16 Oct 2020 09:53:17 -0700 (PDT) X-Gm-Message-State: AOAM533UKb02iO4s8dbDAR5fm5B3o1+3sYZ7seYVHPtHO7YAUh3z9xjd Ol9K7Nw9ol6WWHOyMCqXyNmQISYh4/O3PL/Rjac= X-Google-Smtp-Source: ABdhPJwE/a/xZUiQ/22jjgDNXj8i4Y79XOf+n/fbCKOOSj++sfg1uP5/QAoE7iConP0iBPEo4XOsZsNSu4SFwbysE4Y= X-Received: by 2002:ac8:6047:: with SMTP id k7mr4204724qtm.60.1602867197305; Fri, 16 Oct 2020 09:53:17 -0700 (PDT) MIME-Version: 1.0 References: <202010161516.09GFGNUI015980@repo.freebsd.org> <5475d244-b507-d369-46c1-2b75c02a8645@FreeBSD.org> In-Reply-To: <5475d244-b507-d369-46c1-2b75c02a8645@FreeBSD.org> From: Kyle Evans Date: Fri, 16 Oct 2020 11:53:06 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: svn commit: r366766 - head To: John Baldwin Cc: src-committers , svn-src-all , svn-src-head Content-Type: text/plain; charset="UTF-8" X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2020 16:53:18 -0000 On Fri, Oct 16, 2020 at 11:47 AM John Baldwin wrote: > > On 10/16/20 8:16 AM, Kyle Evans wrote: > > Author: kevans > > Date: Fri Oct 16 15:16:23 2020 > > New Revision: 366766 > > URL: https://svnweb.freebsd.org/changeset/base/366766 > > > > Log: > > Makefile: add a small blurb about building with gcc xtoolchain > > > > The key details are to install the appropriate flavor of devel/freebsd-gcc9 > > and pass CROSS_TOOLCHAIN while building. > > > > Suggested by: kib > > > > Modified: > > head/Makefile > > > > Modified: head/Makefile > > ============================================================================== > > --- head/Makefile Fri Oct 16 14:28:13 2020 (r366765) > > +++ head/Makefile Fri Oct 16 15:16:23 2020 (r366766) > > @@ -89,6 +89,15 @@ > > # 10. `reboot' > > # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) > > # > > +# For individuals wanting to build from source with GCC from ports, first build > > +# or install an appropriate flavor of devel/freebsd-gcc9. The packages produced > > +# by this port are named "${TARGET_ARCH}-gcc9" -- note that not all > > +# architectures supported by FreeBSD have an external gcc toolchain available. > > +# > > +# Once the appropriate freebsd-gcc package is installed, simply pass > > +# CROSS_TOOLCHAIN=${TARGET_ARCH}-gcc9 while building with the above steps, > > +# e.g., `make buildworld CROSS_TOOLCHAIN=amd64-gcc9`. > > gcc9 is probably still a bit premature. 'make USE_GCC_TOOLCHAINS=yes tinderbox' > still uses gcc6 as I still have several open reviews for gcc9 fixes, though > OpenZFS regressed the build for both gcc6 and gcc9 as Adrian is finding. > > I think I would also just suggest 'pkg install ${TARGET_ARCH}-gcc6' rather than > building the port. That is what 'make tinderbox' suggests. > Sure, I'll wordsmith it again and throw something up for review. The key point I want to nail down is the package naming and how to easily locate in the ports tree where that's built from in case that becomes a relevant detail while you're cross-building.