Thanks for the replies!

> Did you also add your user to the 'wsrc'[0] and 'wobj'[1] groups?

I was already in the 'wsrc' group, but not in 'wobj'. Adding myself to that group (and logging out) did not change the situation.

> it would be clearer if you showed the output you get too.

I'm attaching the extract log (extract.log).

> I bet it is installing build dependencies, for which it needs root...

I think you're right. The extract logs don't show the authentication prompts, but I can see that they happen once for every dependency.

I guess that, by manually installing the dependencies from `BUILD_DEPENDS` and `LIB_DEPENDS`, I won't be able to use `pkg_delete -a` to automatically remove them when they're no longer needed; but that's manageable.

> Naturally this is not for everyone, can mask build issues (e.g. if a dependency would now pick up conflicting/unintended libs/tools), and packages may be out-of-date in terms of patches or versions.

If installing the pre-built packages for dependencies can be problematic, I'm inclined to try `sudo -E`. It's a shame, because I didn't want to replace doas — it works fine for everything else.






On Sunday, December 21st, 2025 at 12:17, Morgan Aldridge <morgant@makkintosshu.com> wrote:

> On Sat, Dec 20, 2025 at 18:04 Stuart Henderson <stu@spacehopper.org> wrote:
> 
> > On 2025/12/20 19:23, Douglas Silva wrote:
> > > 1. I have privilege separation enabled in /etc/mk.conf:
> > >
> > > PORTS_PRIVSEP=Yes
> > > SUDO=doas
> > >
> > [SNIP]
> > >
> > > 4. cd to a port (e.g. net/tor) and run all the make targets from "fetch" to "extract".
> > >
> > > $ cd /usr/ports/net/tor
> > > $ make fetch
> > > $ make checksum
> > > $ make extract
> > 
> > it would be clearer if you showed the output you get too.
> > 
> > I bet it is installing build dependencies, for which it needs root,
> > and for that yes if you're using doas (even with persist) you'll
> > need to enter the password multiple times. (using sudo rather than
> > doas, with "SUDO=sudo -E", gives a more comfortable experience -
> > some loss of protection, but not as bad as using "nopass").
> > 
> > you can save some time by installing by hand:
> > 
> > $ make show=BUILD_DEPENDS
> > devel/metaauto devel/autoconf/2.69
> > $ make show=LIB_DEPENDS
> > devel/libevent2
> > $ doas pkg_add metaauto autoconf%2.69 libevent2
> 
> 
> You can also configure your /etc/mk.conf to default to installing dependencies from packages, if available See <https://man.openbsd.org/bsd.port.mk#FETCH_PACKAGES>. For example, my /etc/mk.conf:
> 
> 
> SUDO=doas
> PORTS_PRIVSEP=Yes
> FETCH_PACKAGES=-Dsnap
> 
> You'll still have to enter your password, but you'll save a lot of time, output to sift through, and not have to monitor the build as closely (due to doas/sudo prompts) if all/most dependencies are just installed first.
> 
> Naturally this is not for everyone, can mask build issues (e.g. if a dependency would now pick up conflicting/unintended libs/tools), and packages may be out-of-date in terms of patches or versions. I'd follow Stuart's suggestions first, but know that further automation is built in if it's a fit for you.
> 
> Morgan Aldridge
+++ Sat Dec 20 15:47:08 -03 2025
===>  Checking files for tor-0.4.8.21
`/usr/ports/distfiles/tor-0.4.8.21.tar.gz' is up to date.
>> (SHA256) all files: OK
===> tor-0.4.8.21 depends on: metaauto-* - not found
===>  Verifying install for metaauto-* in devel/metaauto
===> Building from scratch metaauto-1.0p4
--- Sat Dec 20 15:47:08 -03 2025
+++ Sat Dec 20 15:47:23 -03 2025
===> Returning to build of tor-0.4.8.21
===> tor-0.4.8.21 depends on: metaauto-* -> metaauto-1.0p4
===> tor-0.4.8.21 depends on: autoconf-2.69 - not found
===>  Verifying install for autoconf-2.69 in devel/autoconf/2.69
===> Building from scratch autoconf-2.69p3
--- Sat Dec 20 15:47:24 -03 2025
+++ Sat Dec 20 15:47:54 -03 2025
===> Returning to build of tor-0.4.8.21
===> tor-0.4.8.21 depends on: autoconf-2.69 -> autoconf-2.69p3
===> tor-0.4.8.21 depends on: libevent-* - not found
===>  Verifying install for libevent-* in devel/libevent2
===> Building from scratch libevent-2.1.12p3
--- Sat Dec 20 15:47:55 -03 2025
+++ Sat Dec 20 15:49:19 -03 2025
===> Returning to build of tor-0.4.8.21
===> tor-0.4.8.21 depends on: libevent-* -> libevent-2.1.12p3
===>  Verifying specs:  c crypto event_core event_extra execinfo m pthread ssl z
===>  found c.102.2 crypto.57.2 event_core.2.1 event_extra.1.0 execinfo.4.0 m.10.1 pthread.28.1 ssl.60.2 z.7.1
===>  Extracting for tor-0.4.8.21
--- Sat Dec 20 15:49:20 -03 2025

• extract.log (1K)