On Sun, Mar 02, 2014 at 07:53:31PM -0800, David Thiel wrote: > On 02/27, Chad J. Milios wrote: > > root@kakashi:~ # dnscache-conf dnscache dnslog /var/service/dnscache > > dnscache-conf: fatal: unable to switch to > > /usr/ports/dns/djbdns/work/stage/usr/local: file does not exist > > root@kakashi:~ # strings `which dnscache-conf` | grep stage > > /usr/ports/dns/djbdns/work/stage/usr/local > > > > HOWEVER the software works properly ONCE it manages to get installed by > > the normal `make clean install` method (where i have to try about 15 > > times with my fingers crossed and by the grace of God it works one of > > the times) and strings reports no 'stage' anywhere in dnscache-conf > > Bapt figured it out. The "it" target included the install target, making > "prog" the more appropriate build target. I'm still rather confused as > to why this made the issues timing-sensitive (and apparently only in > some environments), but it should work now. Similar issues may be > affecting other djb ports; I'll investigate that this week. > I have been able to reproduce this issue everywhere, sorry it was totally my fault as with "DEVELOPER=yes" in my make.conf it was showing the problem during the qa phase which somehow I haven't seen the first time when I staged it.
My bad, I deserve my pointyhat for that one. I have had a look at sysutils/daemontools and it is safe in that area, in fact given how most of djb's Makefile are written 'it' should be the right target, djbdns seems a bit special here. Sorry about the initial breakage regards, Bapt
pgp_b7hwFKnAZ.pgp
Description: PGP signature
