Date: Mon, 12 Dec 2016 23:26:13 -0600 From: Kyle Evans <kevans91@ksu.edu> To: Baptiste Daroussin <bapt@freebsd.org> Cc: <ports-committers@freebsd.org>, <svn-ports-all@freebsd.org>, <svn-ports-head@freebsd.org> Subject: Re: svn commit: r428312 - in head/devel: aarch64-none-elf-gcc amd64-gcc arm-none-eabi-gcc mips-gcc mips64-gcc powerpc64-gcc powerpc64-gcc/files sparc64-gcc Message-ID: <CACNAnaF5DyLhpfEDt9tZrGrj0ohBdhr%2B8rmrZBhs1G=SqgU5rg@mail.gmail.com> In-Reply-To: <201612101844.uBAIia2u094366@repo.freebsd.org> References: <201612101844.uBAIia2u094366@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sat, Dec 10, 2016 at 12:44 PM, Baptiste Daroussin <bapt@freebsd.org> wrote: > Author: bapt > Date: Sat Dec 10 18:44:36 2016 > New Revision: 428312 > URL: https://svnweb.freebsd.org/changeset/ports/428312 > > Log: > Update cross toolchain gcc to 6.2.0 > Remove the powerpc64 patch which has been upstreamed After this update, I seem to no longer have any issues with libstdcxx enabled for devel/arm-none-eabi-gcc. Would you consider dropping the flag to disable libstdcxx? As far as I can tell, it's the only remaining blocker for Arduino 1.6 SAMD board compilation support. > Modified: head/devel/powerpc64-gcc/Makefile > ============================================================================== > --- head/devel/powerpc64-gcc/Makefile Sat Dec 10 18:38:34 2016 (r428311) > +++ head/devel/powerpc64-gcc/Makefile Sat Dec 10 18:44:36 2016 (r428312) > @@ -29,7 +28,7 @@ RUN_DEPENDS= ${BU_PREFIX}-as:devel/${PKG > > .if empty(GCC_TARGET) > # We are building for a FreeBSD target > -GCC_TARGET?= ${PKGNAMEPREFIX}portbld-${OPSYS:tl}${OSREL} > +GCC_TARGET?= ${PKGNAMEPREFIX}unknown-${OPSYS:tl}${OSREL} > BU_PREFIX?= ${PKGNAMEPREFIX}${OPSYS:tl} > EXTRA_PATCHES+= ${FILESDIR}/freebsd-format-extensions > .else > @@ -48,6 +47,7 @@ CONFIGURE_ARGS+=--target=${GCC_TARGET} - > --with-gmp=${LOCALBASE} \ > --with-pkgversion="FreeBSD Ports Collection for ${PKGNAMEPREFIX:C/-//g}" \ > --with-system-zlib \ > + --with-gcc-include-dir=/usr/include/c++/v1/ \ > --with-as=${LOCALBASE}/bin/${BU_PREFIX}-as \ > --with-ld=${LOCALBASE}/bin/${BU_PREFIX}-ld > > @@ -62,9 +62,9 @@ post-patch: > ${WRKSRC}//gcc/cp/g++spec.c > > .if ${ARCH} == "amd64" > -CONFIGURE_TARGET= x86_64-portbld-${OPSYS:tl}${OSREL} > +CONFIGURE_TARGET= x86_64-unknown-${OPSYS:tl}${OSREL} > .else > -CONFIGURE_TARGET= ${ARCH}-portbld-${OPSYS:tl}${OSREL} > +CONFIGURE_TARGET= ${ARCH}-unknown-${OPSYS:tl}${OSREL} > .endif > > post-install: The s/portbld/unknown of {GCC,CONFIGURE} in these two sections seems to break all of the *-xtoolchain-gcc ports, as they're expecting 'portbld' still. Was this intentional, or a change that has yet to be reflected in these other ports? Thank you for your time! =) Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaF5DyLhpfEDt9tZrGrj0ohBdhr%2B8rmrZBhs1G=SqgU5rg>