The install target, combined with the -j option is totally broken. This is
troublesome, because if a port installs dependencies you cannot use -j to
build the port.
I have tried to find out what happens in bsd.port.mk, but all I can say is,
that with -j defined the port omits all such important targets as do-extract,
do-patch, do-configure or do-build and heads right to do-install, even though
nothing has been built.
The -j flag would be useful for SMP systems or those who use distcc.
How-To-Repeat: Go to a ports folder and run:
# make -j 4 install
Or go to a a ports folder that also installs build dependencies and run:
# make -j 4
bsd.port.mk is port manager territory
This is not the only problem with using -j. The major problem is that
many ports are not, themselves, -j clean.
This has been discussed many times in the past but no one has yet come up
with a comprehensive solution for it.
On further investigation of the bsd.*.mk PRs, this appears to be a duplicate
of ports/95759, so track followups there instead.