Date: Sat, 17 Feb 2018 21:58:19 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 224217] [patch] Fix cross build of base/ ports Message-ID: <bug-224217-32340-7V3qScnRJx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224217-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-224217-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224217 --- Comment #26 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #23) Turns out that a modern devel/powerpc64-binutils uses powerpc64-unknown-freebsd12.0- prefixes, just like base/binutils does. The same goes for devel/powerpc64-gcc and base/gcc . So base/binutils and devel/powerpc64-binutils end up with PATH controlling which directory is used when the path is implicit, just like base/gcc vs. devel/powerpc64-gcc does. The above is stated for a powerpc64 context with both a base/{binutils,gcc} pair installed and a devel/powerpc64-{binutils,gcc} pair built and installed. /usr/bin/ vs. /usr/local/bin/ and the like being involved for PATH use when not explicit. (I need to be careful of this once I get to the point of testing base/{binutils,gcc} use in my powerpc64 context. I normally have devel/powerpc64-{binutils,gcc} installed and so could implicitly use the wrong files.) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224217-32340-7V3qScnRJx>