Date: Thu, 28 Apr 2016 10:13:11 -0700 From: Mark Millard <markmi@dsl-only.net> To: Steve Wills <swills@FreeBSD.org> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: port's svn commit: r413746 - in head "many ports: mark broken on powerpc64": for what toolchains? Message-ID: <1ABC33D7-86DB-4CA7-BA48-A995AB6DEA7C@dsl-only.net> In-Reply-To: <572216FD.9030700@FreeBSD.org> References: <34C0599F-044B-46ED-AF60-0F0E98876E2F@dsl-only.net> <571C0297.3050801@FreeBSD.org> <28FDFFB4-02CC-40CB-ACAC-828BA8E71A37@dsl-only.net> <00621189-D577-4E3F-8BAB-4B315B690209@dsl-only.net> <571CC2F2.2060601@FreeBSD.org> <F7E6ED93-A73D-406D-A7BF-B1B80C61871F@dsl-only.net> <571D0146.5060200@FreeBSD.org> <572216FD.9030700@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-Apr-28, at 6:58 AM, Steve Wills <swills@FreeBSD.org> wrote: >=20 > I did test this, but it failed. The log is here: >=20 > = http://poudriere.mouf.net/karl/poudriere/data/headpowerpc-default/2016-04-= 27_12h19m39s/logs/gcc6-devel-6.0.0.s20160320.log >=20 > Looks like gfortran failed to build? >=20 > Steve The file name gcc6-devel-6.0.0.s20160320.log indicates the s20160320 = version but I used /usr/ports -r413919 which built: > # pkg info 'gcc6*' > gcc6-devel-6.0.1.s20160421 In other words: about a month later for the gcc6 version. I do not know if this makes a difference or not. poudriere.mouf.net is not responding currently: > The server is temporarily unable to service your request due to = maintenance downtime or capacity problems. Please try again later =3D=3D=3D Mark Millard markmi at dsl-only.net On 04/24/16 01:24 PM, Steve Wills wrote: > Hi, >=20 > On 04/24/16 10:16 AM, Mark Millard wrote: >>=20 >> For all the port update activity (including ruby) I used gcc49, = /etc/make.conf being: >>=20 >> # more /etc/make.conf DEFAULT_VERSIONS+=3Dperl5=3D5.22=20 >> WRKDIRPREFIX=3D/usr/obj/portswork >> WITH_DEBUG=3D >> WITH_DEBUG_FILES=3D=20 >> MALLOC_PRODUCTION=3D >> # >> # >> # For trying gcc49... >> #=20 >> CC=3D/usr/local/bin/gcc49 >> CXX=3D/usr/local/bin/g++49=20 >> CPP=3D/usr/local/bin/cpp49 >> . . . (binutils macros omitted here) . . . >>=20 >>=20 >> (I do not know if lang/gcc [or lang/gcc48] would work or not. I >> prefer a tool chain with a more modern C++ available but gcc49 is not >> yet what lang/gcc builds.) >>=20 >>=20 >>=20 >> I've seen notation like: >>=20 >> USE_GCC=3D 4.9+ >>=20 >> in port Makefiles. Also notation like: >>=20 >> .if ${ARCH} =3D=3D powerpc64 >>=20 >> and: >>=20 >> .if ${ARCH} =3D=3D "powerpc" || ${ARCH} =3D=3D "powerpc64" >>=20 >>=20 >> So may be the extra notation in the Makefile(s) in question could be = something like: >>=20 >> # clang 3.8.0 and before is still broken in various ways for powerpc = and powerpc64: >> .if ${ARCH} =3D=3D "powerpc" || ${ARCH} =3D=3D "powerpc64" >> USE_GCC=3D 4.9+ >> .endif >>=20 >=20 > Yep, this sounds right to me. I will test this with at least = lang/ruby22 > and lang/gcc6-devel when my current build finishes, or sooner if I get > impatient. :) >=20 >=20 >> I list both powerpc variants because powerpc and powerpc64 both have >> clang problems making buildworld a no-go by default and if gcc 4.2.1 >> rejects a port for one it would normally also reject for the other. >> There may be other ${ARCH} values that would also be appropriate >> because they are also stuck at gcc 4.2.1 . >=20 > Makes sense. >=20 >> I do not claim to know necessary vs. sufficient status: more might be >> needed for some configurations (rpath issues? mixture of libraries >> compiled by distinct gcc's?). But I expect that the above should be >> better than being marked broken. >=20 > We'll find this out when we test! :) >=20 > Thanks, > Steve >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ABC33D7-86DB-4CA7-BA48-A995AB6DEA7C>