Riccardo Mottola <[email protected]> writes: > Hi, > > Greg Troxel wrote: >> 1) Perhaps there is an installed package that depends on meson. grep for >> meson in/usr/pkg/pkgdb/*/*, more or less. > > /usr/pkg/pkgdb/glib2-2.82.2/+CONTENTS:@blddep meson-1.6.0nb1 > /usr/pkg/pkgdb/p11-kit-0.25.5/+CONTENTS:@blddep meson-1.6.0nb1 > > this twells me that two packages have it as a build dependency? that > explains maybe me not having it if everything was installed with > binary packages, but I'd expect make replace to pull it in, shouldn't > it?
yes, it's ok not to have build deps installed. >> 2) run pkg_rolling-replace with 'sh -x' and figure out what happened. >> It's not that complicated. > > explain me more 'sh -x' ? For a shell script, you can sh -x /path/to/script and it prints a trace of what it is doing. Reading the man page, it's more complicated, and you might want to add "set -x" as an early extra line in the script. The problem is that pkg_rr is somehow finding meson as a dependency, btu not finding it installed. That may be a pkg_rr bug and it may be a messed up database. You are the first report. Just do 'make replace clean' in glib2, and that will likely build and install meson, and then you can run again.
