Basic starting context:
> # freebsd-version -ku; uname -apKU
> 11.0-CURRENT
> 11.0-CURRENT
> FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11
> 19:23:14 PDT 2015
> root@FBSDG4C0:/usr/obj/powerpc.powerpc64/usr/srcC/sys/GENERIC64vtsc-NODEBUG
> powerpc powerpc64 1100
It looks to me like the space between -m and elf32ppc_fbsd in "-m
elf32ppc_fbsd" is likely not allowed for powerpc64-gcc (gcc 4.9.1):
(shown ignoring binary file matches)
> # pwd
> /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work
> # find . -type f -exec grep elf32ppc_fbsd {} \; -print | mor
Basic context (more details given later):
> # freebsd-version -ku; uname -apKU
> 11.0-CURRENT
> 11.0-CURRENT
> FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11
> 19:23:14 PDT 2015
> root@FBSDG4C0:/usr/obj/powerpc.powerpc64/usr/srcC/sys/GENERIC64vtsc-NODEBUG
> powe
It appears that I added powerpc64 (and several others) to the
devel/llvm* ports version of this patch, but didn't do it for
lang/clang*. I'll sync them up.
-- Brooks
On Tue, Mar 17, 2015 at 08:02:47PM -0700, Mark Millard wrote:
> patch-utils_llvm-build_llvmbuild_main.py is missing a powerpc64 en