On Fri, Oct 16, 2020 at 11:53:06AM -0500, Kyle Evans wrote: > On Fri, Oct 16, 2020 at 11:47 AM John Baldwin <j...@freebsd.org> 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.
Yes, please keep a reference to the ports origin, and how to specify flavor, for those who runs local poudriere. _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
