David Brownlee <abs%absd.org@localhost> writes: > On 2 July 2018 at 11:36, <maya%netbsd.org@localhost> wrote: >> On Mon, Jul 02, 2018 at 11:32:15AM +0100, David Brownlee wrote: >>> On 29 June 2018 at 18:16, David Brownlee <abs%absd.org@localhost> wrote: >>> > On 29 June 2018 at 17:16, <maya%netbsd.org@localhost> wrote: >>> >> On Fri, Jun 29, 2018 at 11:11:45AM -0400, Greg Troxel wrote: >>> >>> >>> OK, so just following up on this. >>> >>> On gcc 5.5 from NetBSD-8: >>> * --std=c++11 is not sufficient to build firefox61 >>> * --std=c++14 will build and run fine >>> >>> So that leaves the open question on how to handle firefox61 and NetBSD It seems clear firefox needs some --std added, but I don't want to do that in freeze. (And thank you all for discussing and not changing.) >>> a) Set GCC_REQD=6.1 on package to reflect current state >>> Will not build on any NetBSD release (or near release) unless all of >>> pkgsrc install has overridden gcc version Indeed, it fails on netbsd-7 with this. >>> b) Patch package to build with gcc5.5 and set GCC_REQD=5.5 >>> Can now build out of box on netbsd-8, likely to need to revisit in a >>> later release >>> >>> c) Increase min gcc c++ version to 6.1 for NetBSD versions which can build it >>> Can now build out of the box on all appropriate NetBSD versions. Many >>> unhappy people due to needing to build all of gcc6 to install tiny c++ >>> packages I think we are heading that way post branch, not just because of this. >>> d) Handle being able to selectively override GCC_REQD for some packages >>> Did we ever get anywhere with this?. Can we reliably do it between >>> *some* versions - eg 5.5 & 6? >>> >>> I have a preference towards b) now, and d) if it becomes possible at >>> some point in the future... >>> >>> David >> >> Yeah we selectively override with GCC_REQD+=6.1 now. ryo committed this. It turns out that was committed before my message, but I hadn't noticed yet, and nobody mentioned it on the list. > Ah - sorry missed that. > > Woo - happy camper :) Glad to hear you are ok with how things are. I plan to let it be, basically choosing (a) for the branch. Post branch, all options are on the table, but it's not just about firefox. (will defer that to post branch)
Attachment:
signature.asc
Description: PGP signature