On Mon, 13 Oct 2014 10:14:45 +0200 Antoine Jacoutot <[email protected]> wrote: > On Mon, Oct 13, 2014 at 04:59:42AM -0400, [email protected] wrote: > > this probably would have been noticed anyway, unless there is something very > > strange on my system, and i did everything by the book (manual). > > > > ports(7) leads me to believe this should work, particularly /etc/mk.conf > > > > In the following list, each target will run the preceding targets in > > order automatically. That is, build will be run (if necessary) by > > install, and so on all the way to fetch. In typical use, one will only > > run install explicitly (as normal user, with SUDO defined in > > /etc/mk.conf), or build (as user), then install (as root). > > > > if SUDO is unset, or set but not exported, 'make' works, 'make install' > > fails. > > if SUDO is exported, or set in mk.conf, 'make' fails, but 'make install' > > works. > > running everything as root breaks other things (see end), though that is > > probably intended. > > > > everything has to be installed manually, which is a PITA for most ports, or > > run as root, which has its obvious problems, and still breaks on some things > > (groff). as it is i cannot chain build dependences (except as root, mostly). > > Make sure you are in the wsrc group. > Or you can set 'SUDO=sudo -E' in mk.conf instead.
thanks, this was it. my /etc/sudoers was fine (clean install from -current), but i was not in the wsrc group. there is no mention of wsrc in the ports(7) page however, so that may need updating.
