Use the freebsd-gcc6 toolchains instead of powerpc64-xtoolchain-gcc.
ClosedPublic
Actions

Authored by jhb on Jan 3 2020, 9:31 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Mon, Nov 3, 4:09 AM

	Unknown Object (File)
	Oct 13 2025, 11:19 PM

	Unknown Object (File)
	Oct 13 2025, 11:19 PM

	Unknown Object (File)
	Oct 13 2025, 11:19 PM

	Unknown Object (File)
	Oct 13 2025, 9:42 AM

	Unknown Object (File)
	Sep 29 2025, 11:32 PM

	Unknown Object (File)
	Sep 22 2025, 8:06 AM

	Unknown Object (File)
	Sep 14 2025, 1:50 PM

View All 86 Files

Subscribers

None

Details

Reviewers

emaste
brooks
imp

Commits

rS356344: Use the freebsd-gcc6 toolchains instead of powerpc64-xtoolchain-gcc.

Test Plan

make tinderbox uses these and gives the mostly-meaningful error if they aren't listed. The error for riscv lists the wrong package name now, but I plan to bump it to gcc9 soon anyway which will resolve that.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

jhb created this revision.Jan 3 2020, 9:31 PM

Harbormaster completed remote builds in B28470: Diff 66323.Jan 3 2020, 9:31 PM

I plan to test GCC 9 after this, but it would also be good to just remove the weird OBSOLETE bits to try to build with 4.2.1 at all. I can take a stab at that.

brooks accepted this revision.Jan 4 2020, 12:34 AM

This revision is now accepted and ready to land.Jan 4 2020, 12:34 AM

Closed by commit rS356344: Use the freebsd-gcc6 toolchains instead of powerpc64-xtoolchain-gcc. (authored by jhb). · Explain WhyJan 4 2020, 1:00 AM

This revision was automatically updated to reflect the committed changes.

jhb added a commit: rS356344: Use the freebsd-gcc6 toolchains instead of powerpc64-xtoolchain-gcc..