Date: Sat, 17 Feb 2018 05:41:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214400] ports/head/base/binutils (r421584) targeting powerpc64: cross build failed for lack of finding a "gcc" command Message-ID: <bug-214400-13-gGzVOpHReI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214400-13@https.bugs.freebsd.org/bugzilla/> References: <bug-214400-13@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=3D214400 --- Comment #13 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Steve Wills from comment #12) I did not have the specific gcc problem when I tried to build based on the newer material. So the specifics have been taken care of. Points of note . . . I did have to first have installed (not via base/binutils): devel/bison and devel/gmake and a lang/perl5.* (I had 5.24 installed.) The README did not indicate such a requirement. (base/binutils did not build them sufficiently on its own.) There are what may be odd relationships for some file names produced for to-be-installed files for: base/binutils vs. devel/powerpc64-binutils vs. base/gcc vs. devel/powerpc64-gcc 3 of the 4 use powerpc64-unknown-freebsd12.0- prefixes but devel/powerpc64-binutils uses powerpc64-freebsd- prefixes. (Or did last I built it on a powerpc64.) There are the /usr/bin/ vs. /usr/local/bin/ sorts of path differences as well so the matching names for devel/powerpc64-gcc and base/gcc make for ties to path order. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214400-13-gGzVOpHReI>