Date: Sun, 20 Apr 2003 15:34:27 +0700 From: "Michael O. Boev" <mike@tric.tomsk.gov.ru> To: <freebsd-gnats-submit@FreeBSD.org>, "Michael O. Boev" <mike@tric.tomsk.gov.ru> Cc: freebsd-ports@freebsd.org Subject: Re: ports/51177: [PATCH] mail/p5-Mail-SpamAssassin fails to install Message-ID: <00a001c30717$a8a0ab50$ec01a8c0@draco>
next in thread | raw e-mail | index | archive | help
Hello everyone! I've made some further investigations on this subject... There's some weird makefile logic about setting .OBJDIR for ports... Here's my setup. 1) I have a nightly checkout of ports in /srv/FreeBSD/ports to which I used to symlink /usr/ports (for ease of typing) 2) To reflect this, I add PORTSDIR=/srv/FreeBSD/ports to /etc/make.conf I believe it's a legal setup according to ports(7). Here's what I've done. isrv# cd /srv/FreeBSD/ports/mail/p5-Mail-SpamAssassin isrv# make -V .OBJDIR /usr/obj/srv/FreeBSD/ports/mail/p5-Mail-SpamAssassin See the .OBJDIR above? Now I comment out the PORTSDIR=blablabla from /etc/make.conf. And look what happens... isrv# mkdir /usr/ports isrv# mount -t null /srv/FreeBSD/ports /usr/ports isrv# cd /usr/ports/mail/p5-Mail-SpamAssassin isrv# make -V .OBJDIR /usr/ports/mail/p5-Mail-SpamAssassin See what happens to .OBJDIR? I conclude this what triggers the installation failure. As most people (I believe) have ports in /usr/ports, the bug like this never happens. But, I've no idea (yet) where this magic logic happens. Hope this helps...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00a001c30717$a8a0ab50$ec01a8c0>