Re: It looks like USE_GCC=any is broken and leads to system-clang use

Am 3. Juli 2017 13:30:13 GMT+08:00 schrieb Mark Millard : >[More on the behavior: it is more complicated than >previously shown.] It's actually pretty simple (I think). Mk/bsd.gcc.mk only uses lang/gcc* ports that represent releases, not lang/gcc*-devel that represent

Re: It looks like USE_GCC=any is broken and leads to system-clang use

[More on the behavior: it is more complicated than previously shown.] On 2017-Jul-2, at 8:12 PM, Mark Millard wrote: > [Looks like output from "make test-gcc" is appropriate, > so I'm adding such.] > > On 2017-Jul-2, at 7:53 PM, Mark Millard wrote: > >> [It looks like USE_GCC=any is broken

Re: It looks like USE_GCC=any is broken and leads to system-clang use

[Looks like output from "make test-gcc" is appropriate, so I'm adding such.] On 2017-Jul-2, at 7:53 PM, Mark Millard wrote: > [It looks like USE_GCC=any is broken and leads to system-clang use.] > > On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote: > >> Am 29. Juni 2017 18:55:59 GMT+08:00

It looks like USE_GCC=any is broken and leads to system-clang use

[It looks like USE_GCC=any is broken and leads to system-clang use.] On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote: > Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard > : >> I'm not currently set up to run more than head on >> any of amd64, powerpc64, powerpc,