notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
non port: devel/aarch64-gcc/pkg-plist

Number of commits found: 4

Friday, 18 Jun 2021
15:29 John Baldwin (jhb) search for other commits by this committer
devel/*{-xtoolchain,}-gcc: Retire the old GCC external toolchain ports.

These have been supplanted by the devel/freebsd-gcc6 port which uses
separate flavors for each target architecture and bundles the

Feedback from:	jrm
Reviewed by:	lwhsu, bapt
Differential Revision:
commit hash: 39c7b0126e2e8e87a6585be830dce2a5db04e5f6 commit hash: 39c7b0126e2e8e87a6585be830dce2a5db04e5f6 commit hash: 39c7b0126e2e8e87a6585be830dce2a5db04e5f6 commit hash: 39c7b0126e2e8e87a6585be830dce2a5db04e5f6 39c7b01
Friday, 27 Jul 2018
15:57 jhb search for other commits by this committer
Cleanup packing lists for xtoolchain gcc packages.

- Add missing entries for gcov-dump and the gcov-tool manpage to the
  various xtoolchain gcc ports.
- Add gcov-dump to the post-install loops that handle optional renaming
  of tools and manpages.

Reviewed by:	kan
Differential Revision:
Original commitRevision:475446 
Friday, 23 Mar 2018
23:53 jhb search for other commits by this committer
Fix --sysroot for cross-toolchain GCC packages

By default, GCC assumes that a cross compiler should not have any valid
initial include or library paths aside from /usr/local/lib/gcc/<mumble>/.
This means that one cannot use --sysroot to point to a system root for
another architecture and have GCC automatically look for headers in
${sysroot}/usr/include, etc.  Currently we workaround this in FreeBSD's
build system with explicit -isystem, -B, and -L directives.  However,
this is cumbersome compared to clang (where a bare --sysroot DTRT)
especially when using the compiler to build other software (such as test
programs, etc.).

One can override GCC's assumption and force it to assume that it should
honor --sysroot by setting the '--with-sysroot' option to force GCC to
assume a specific system root.  By setting this to '/', this means that
the cross-compiler will attempt to use the host's headers by default
if --sysroot is not specified, but if --sysroot is specified then
it is fully honored including for include paths and library paths.  With
this change I can now cross-compile both C and C++ binaries simply by
using --sysroot without the need for -isystem, -B, or -L directives.  Note
that the base/gcc and devel/riscv64-gcc ports both use --with-sysroot='/'

By default, GCC looks for headers in /usr/local/include (under the
sysroot) before /usr/include.  To disable this and only look for headers
in /usr/include, patch gcc/ to not define LOCAL_INCLUDE_DIR.

Once -nostdinc is no longer required, the headers installed along with the
compiler are now used for compiling worlds and test programs.  The "fixed"
headers in include-fixed are generally not helpful and are also derived
from the host's headers which might not match the target --sysroot, so
just delete them entirely.  Even the stub limits.h headers GCC ships when
using an empty build sysroot are not helpful and need to be removed.

On a related note, I also fixed the name of the C++ include directory
option to configure.  By my reading it is 'with-gxx-include-dir' rather
than 'with-gcc-include-dir'.

Reviewed by:	bapt, brooks, kan
Sponsored by:	DARPA / AFRL
Differential Revision:
Original commitRevision:465416 
Saturday, 8 Apr 2017
00:29 kan search for other commits by this committer
Add external toolchain ports for aarch64

This involves copying patch file from lang/gcc6
and minor plist tweaks.

Reviewed by:	emaste, andreast, brooks
Approved by:	brooks
Differential Revision:
Original commitRevision:437977 

Number of commits found: 4