Re: Avoiding cycles in the dependency tree

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

* On 2013-02-24 at 21:44 GMT, Thomas Cort wrote:

> Issue #2: pbulk doesn't really work because it blows away /usr/pkg
> (where the compilers live) when it tries to build packages. We've
> tried installing the toolchain into another directory (/usr/pkg.sav/),
> but libtool and other tools sometimes pick up stuff in that directory.
> Any advice on this front? Maybe add gcc to the binary bootstrap kit
> for Minix?

Sorry, one more thing to note in regards to this, if you choose our
method of using an external toolchain, GCCBASE will ensure you don't
run into libtool issues, but you will see problems with depending upon
the gcc runtime (libgcc et al) from the external toolchain.

Firstly, you should use gcc47, where we have split it into the main
compiler and separate 'libs' package, and then with
USE_PKGSRC_GCC_RUNTIME=yes you can add a dependency upon the
gcc47-libs package and ensure the correct RPATH is used in packages
rather than linking against the gcc libraries from the external
toolchain.

Finally, this only works for packages which use USE_LIBTOOL at
present.  For packages which do their own method of creating shared
libraries, I am slowly adding USE_GCC_RUNTIME support to them in our
'gccruntime' branch:

  https://github.com/joyent/pkgsrc/tree/joyent/feature/gccruntime/trunk

so you may want to merge from there to at least handle some of the
more common packages (perl, for example).

Regards,

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