Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-24 Thread Mark Millard
On 2016-Dec-12, at 12:59 PM, Mark Millard wrote: > [Top post asking if you (Gerald) think portmaster is in > error and so if a bugzilla report should be made.] > > Do you expect that portmaster should instead/also(first) > be checking (using the gcc6:lang/gcc6 related example > from USE_GCC=any

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-12 Thread Mark Millard
[Top post asking if you (Gerald) think portmaster is in error and so if a bugzilla report should be made.] Do you expect that portmaster should instead/also(first) be checking (using the gcc6:lang/gcc6 related example from USE_GCC=any): "pkg query %n-%v gcc6" instead of checking "pkg query %n-%v l

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Mark Millard
On 2016-Dec-11, at 3:11 PM, Mark Linimon wrote: > On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: >> I tend to have powerpc64 and powerpc patches because of my >> experimenting with clang targeting them and that the standard >> powerpc64 build does not boot PowerMac G5's reliably. >

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Mark Linimon
On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: > I tend to have powerpc64 and powerpc patches because of my > experimenting with clang targeting them and that the standard > powerpc64 build does not boot PowerMac G5's reliably. Is that on 10, 11 or -current? On 10 I remember being

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Mark Millard
[After "BUILD_DEPENDS+= gcc6:lang/gcc6" below shows that portmaster does not do what you indicate the build environment should do. The beginning is not essential material.] On 2016-Dec-11, at 4:40 AM, Gerald Pfeifer wrote: > On Sun, 11 Dec 2016, Mark Millard wrote: >> I reported already that dev

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Gerald Pfeifer
On Sun, 11 Dec 2016, Mark Millard wrote: > I reported already that devel/kBuild/Makefile has in its > Makefile: > > USE_GCC= any > > and devel/kBuild is what causes the lang/gcc* build. (I > reported more than that but it is the part relevant here.) I had read that, and I di investigate. USE_G

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Mark Millard
On 2016-Dec-11, at 1:39 AM, Gerald Pfeifer wrote: > Hi Mark, > > On Sat, 10 Dec 2016, Mark Millard wrote: >> [Top post of example lack of lang/gcc6-devel vs. lan/gcc6 >> substitutability. Context /usr/ports/ at -r428325 (other >> than a few specially controlled items.] > > I had another look,

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-11 Thread Gerald Pfeifer
Hi Mark, On Sat, 10 Dec 2016, Mark Millard wrote: > [Top post of example lack of lang/gcc6-devel vs. lan/gcc6 > substitutability. Context /usr/ports/ at -r428325 (other > than a few specially controlled items.] I had another look, and lang/gcc6 and lang/gcc6-devel really are substitutable in what

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-12-10 Thread Mark Millard
[Top post of example lack of lang/gcc6-devel vs. lan/gcc6 substitutability. Context /usr/ports/ at -r428325 (other than a few specially controlled items.] After installing lang/gcc6-devel something else indirectly forced lang/gcc6 to try to build. The attempt failed with: Installing gcc6-6.2.0...

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-11-26 Thread Mark Millard
On 2016-Nov-25, at 11:47 PM, Gerald Pfeifer wrote: > On Fri, 25 Nov 2016, Mark Millard wrote: >> I wonder if that leaves lang/gcc and lang/gcc49 as conflicting. > > Yes, these two ports conflict for the time being, and are properly > marked as such. > > (And I am looking for a more elegant appr

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-11-25 Thread Gerald Pfeifer
On Fri, 25 Nov 2016, Mark Millard wrote: > I wonder if that leaves lang/gcc and lang/gcc49 as conflicting. Yes, these two ports conflict for the time being, and are properly marked as such. (And I am looking for a more elegant approach going forward, in particular when we move into GCC 5 territo

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-11-25 Thread Mark Millard
On 2016-Nov-25, at 5:00 PM, Dimitry Andric wrote: > On 26 Nov 2016, at 01:13, Mark Millard wrote: >> >>> Author: dim (src committer) >>> Date: Fri Nov 25 12:54:01 2016 >>> New Revision: 427110 >>> URL: >>> https://svnweb.freebsd.org/changeset/ports/427110 >>> >>> >>> Log: >>> Fix build of lan

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-11-25 Thread Dimitry Andric
On 26 Nov 2016, at 01:13, Mark Millard wrote: > >> Author: dim (src committer) >> Date: Fri Nov 25 12:54:01 2016 >> New Revision: 427110 >> URL: >> https://svnweb.freebsd.org/changeset/ports/427110 >> >> >> Log: >> Fix build of lang/gcc with libc++ 3.9.0, similar to r421625: >> . . . >> What

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

2016-11-25 Thread Mark Millard
> Author: dim (src committer) > Date: Fri Nov 25 12:54:01 2016 > New Revision: 427110 > URL: > https://svnweb.freebsd.org/changeset/ports/427110 > > > Log: > Fix build of lang/gcc with libc++ 3.9.0, similar to r421625: > . . . > What is happening here, is that the source file includes gcc/sy