Re: bob v0.8.1

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2026-02-08 at 22:25 GMT, ci4ic4 wrote:

> I am getting again (three separate invocations after updating pkgsrc):
>
> Resolving dependencies...Error: Circular dependencies detected:
>        gcc6-6.5.0nb9
>        gsed-4.9nb1
>        gcc6-6.5.0nb9

Any time you see pkgsrc trying to build gcc6, it's basically a really 
bad error message that actually means "pkgsrc couldn't find a compiler 
it could use".  lang/gcc6 is the oldest GCC now available in pkgsrc, and 
so will be the minimum required to satisfy the basic GCC_REQD 
requirements.

If you do not have a compiler installed for the base system, you'll need 
to provide an additional mountpoint in the sandbox configuration so that 
it can be found in sandboxes, something like:

  { action = "mount", fs = "null", dir = "/opt/local" },

or similar.

> After the second invocation I bult and installed gcc6 (I don't need it 
> for anything, as far as I know it, and it was not installed before).

This shouldn't be necessary.  Note that your pkgsrc prefix will not be 
available inside the sandbox, so any compilers you've built locally on 
your system won't be usable.  bob, pbulk, and other tools that use 
sandboxes ensure all builds are done from scratch with no interference 
from installed packages.

I'd recommend installing and configuring a compiler in the base system, 
at least one that will allow bootstrapping to a newer one if necessary.
Alternatively, and what I have always done for my pkgsrc builds, is to 
build a compiler version that is suitable for all of the packages I am 
going to build, and then use that for everything, as this avoids 
expensive duplicate gcc builds and mixing of GCC libraries.

> Scanned 20169 package paths in 11h 19m 31s (20169 succeeded, 0 failed)

This is really slow.  Unless you are on very slow hardware this should 
complete in a matter of minutes.  It is also performing what looks to be 
a full bulk build.  If that's what you want, fine, but if you only want 
to build the packages you are interested in then set pkgpaths in 
config.lua, e.g.

  pkgpaths = read_pkgpaths("/path/to/pkgchk.conf"),

if you already have a pkgchk.conf that contains lines of the form 
"mail/mutt" etc, or similar.

You may want to take a look at using pkgtools/varcache to pre-populate 
expensive variables, as well as adding any other cached variables to 
mk.conf as this will have a drastic effect on all pkgsrc operations.  
I'm happy to write this up if you need more details.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com