Re: Once more, C++11 and older 'base' compilers

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2017-08-12 at 15:14 BST, Joerg Sonnenberger wrote:

> On Sat, Aug 12, 2017 at 08:38:50AM -0500, Jason Bacon wrote:
> > On 08/09/17 17:27, coypu%sdf.org@localhost wrote:
> > > On Wed, Aug 09, 2017 at 01:11:38PM -0500, Jason Bacon wrote:
> > > > Can you clarify how _TARGET_HAS_PKGSRC_GCC gets set?  Is this built into the
> > > > bootstrap scripts and set globally for selected OSs and ARCHs?  Can users
> > > > add it to mk.conf for other platforms?
> > > I wanted to whitelist platforms. linux is diverse, but often very well supported.
> > > For all others we can say yes/no with certainty after testing.
> > > 
> > > > How do gcc48 and dependencies get exempted so they can build with the system
> > > > compiler?
> > > With this exception (should possibly be a wildcard for 5,6,7?)
> > > 
> > > #  Special case packages which are themselves a dependency of gcc runtime.
> > > .  if empty(PKGPATH:Mdevel/libtool-base) && empty(PKGPATH:Mdevel/binutils) && empty(PKGPATH:Mlang/gcc??)
> > 
> > FYI, this is the minimum I had to do on CentOS 6 to avoid a circular
> > dependency:
> 
> Please use the gcc-inplace-math option. That should cut out most of that
> list.

You'll also save a bunch by using an external perl and makeinfo if
available, which will also help avoid issues with how they are to link
against a GCC runtime, for example:

  https://github.com/joyent/pkgbuild/blob/master/include/exttools.mk#L28..L35

Cheers,

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com