Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
Dan Mahoney, System Admin wrote: > On Wed, 29 Jul 2009, Doug Barton wrote: > >> Dan Mahoney, System Admin wrote: >>> The fact that the error occurs AT ALL is the bug and what is >>> counterintuitive, and many people would not think to try typing "make" >>> again, and instead would just assume the thing's broken. >> >> Ok, I actually misunderstood the problem that you were reporting. I >> thought that the reference to .build_done.bind96._usr_local indicated >> that the port had already been built once, but that is not the case. >> To reproduce the bug, you need to do the following: >> >> 1. Make sure there is nothing in /var/db/ports/bind96 >> 2. cd /usr/ports/dns/bind96 >> 3. make >> 4. Enable the "replace base" option >> 5. Save the config >> >> You will then see the following error: >> >> make: don't know how to make >> /usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local. >> >> Stop >> *** Error code 2 >> >> I think Mel is right that the problem is changing PREFIX, but that's >> the whole purpose of the option. >> >> Could you please open a PR about this with a subject something to the >> effect of "OPTIONS that change PREFIX cause an error after 'make >> config'" and describe how to reproduce this? > > Done, just got the mail from gnats: 137250. Looks good, thanks! Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wed, 29 Jul 2009, Doug Barton wrote: Dan Mahoney, System Admin wrote: The fact that the error occurs AT ALL is the bug and what is counterintuitive, and many people would not think to try typing "make" again, and instead would just assume the thing's broken. Ok, I actually misunderstood the problem that you were reporting. I thought that the reference to .build_done.bind96._usr_local indicated that the port had already been built once, but that is not the case. To reproduce the bug, you need to do the following: 1. Make sure there is nothing in /var/db/ports/bind96 2. cd /usr/ports/dns/bind96 3. make 4. Enable the "replace base" option 5. Save the config You will then see the following error: make: don't know how to make /usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 I think Mel is right that the problem is changing PREFIX, but that's the whole purpose of the option. Could you please open a PR about this with a subject something to the effect of "OPTIONS that change PREFIX cause an error after 'make config'" and describe how to reproduce this? Done, just got the mail from gnats: 137250. -Dan -- Pika Pika Pika! -Pikachu, of Pokemon fame. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
Dan Mahoney, System Admin wrote: > The fact that the error occurs AT ALL is the bug and what is > counterintuitive, and many people would not think to try typing "make" > again, and instead would just assume the thing's broken. Ok, I actually misunderstood the problem that you were reporting. I thought that the reference to .build_done.bind96._usr_local indicated that the port had already been built once, but that is not the case. To reproduce the bug, you need to do the following: 1. Make sure there is nothing in /var/db/ports/bind96 2. cd /usr/ports/dns/bind96 3. make 4. Enable the "replace base" option 5. Save the config You will then see the following error: make: don't know how to make /usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 I think Mel is right that the problem is changing PREFIX, but that's the whole purpose of the option. Could you please open a PR about this with a subject something to the effect of "OPTIONS that change PREFIX cause an error after 'make config'" and describe how to reproduce this? Thanks, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wed, 29 Jul 2009, Doug Barton wrote: Mel Flynn wrote: On Wednesday 29 July 2009 10:57:05 Doug Barton wrote: Dan Mahoney, System Admin wrote: I believe Mel is right here. 'make clean ; make config ; make' worked for me. As does a second make after getting this error, but it's nonintuitive, and probably a ports bug. I'm not sure why 'make clean' is nonintuitive in the context of changing OPTIONS. What is your expectation of how it should work? What he means is that make without arguments or make install as per handbook, will build the build target which will invoke the config target if OPTIONS changed or no options file is found. In the original post the build was already done, but it had been done with a different set of OPTIONS choices. My question is, why is running 'make clean' in the scenario of: 1. build 2. change options [make clean should happen here] 3. install not intuitive? Because in my case, the thing was already "clean" beforehand? Two systems, one 6.4-PRERELEASE (6.4 release, really, it missed the release date by hours), the other 6.4-STABLE. Both exhibit this with a ports tree cvsupped hours before this report. make clean (or even make distclean), make rmconfig, then make still gives me this issue. "run clean after changing options" is intuitive and is common sense, yes. "run clean after running config and before building code that you haven't built before" does not make sense. On a virgin port, you are thrown into the options screen by default unless you have BATCH set. That's the counterintuitive part. -Dan -- "Happy, Sad, Happy, Sad, Happy, Sad, Happy, Intruiged! I've never been so in touch with my emotions!" -AndrAIa as Hexadecimal, Reboot Episode 3.2.3 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wed, 29 Jul 2009, Doug Barton wrote: Dan Mahoney, System Admin wrote: I believe Mel is right here. 'make clean ; make config ; make' worked for me. As does a second make after getting this error, but it's nonintuitive, and probably a ports bug. I'm not sure why 'make clean' is nonintuitive in the context of changing OPTIONS. What is your expectation of how it should work? The fact that the error occurs AT ALL is the bug and what is counterintuitive, and many people would not think to try typing "make" again, and instead would just assume the thing's broken. (See previously referenced email) Make clean isn't solving the problem, but I can see how you're getting that thought. The problem only occurs on a virgin, untouched, un-configged port. The solution to the problem in this case is to just re-run make. There's nothing to CLEAN, since you haven't made yet. The reason it seems like make clean fixes it may also because make clean does not do a make rmconfig: when I do an rmconfig I can successfully duplicate this problem, however: Running make config then make: fine Running just make, with no config: this error. Thoughts? -- "If you aren't going to try something, then we might as well just be friends." "We can't have that now, can we?" -SK & Dan Mahoney, December 9, 1998 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
Mel Flynn wrote: > On Wednesday 29 July 2009 10:57:05 Doug Barton wrote: >> Dan Mahoney, System Admin wrote: I believe Mel is right here. 'make clean ; make config ; make' worked for me. >>> As does a second make after getting this error, but it's nonintuitive, >>> and probably a ports bug. >> I'm not sure why 'make clean' is nonintuitive in the context of >> changing OPTIONS. What is your expectation of how it should work? > > What he means is that make without arguments or make install as per handbook, > will build the build target which will invoke the config target if OPTIONS > changed or no options file is found. In the original post the build was already done, but it had been done with a different set of OPTIONS choices. My question is, why is running 'make clean' in the scenario of: 1. build 2. change options [make clean should happen here] 3. install not intuitive? > However, this is a corner case, as it applies to: > - Ports that change PREFIX using OPTIONS > - For which no options file is available or the OPTIONS list has changed > - When the PREFIX is actually changed through toggling the appropriate option. > > This applies surely to less then 100 (probably more like a dozen) ports on > the > 18k that are in the tree and only affects people who do not use ports-mgmt > software. As such it is not worth fixing, IMHO. Forget this particular problem, you're right that the fact that the ports system doesn't know how to deal with an obsoleted build-cookie actually is a corner case. My concern is the general user expectation of what should happen in this scenario. If it's generally expected that magic should happen if a users changes OPTIONS after building the port we need to make that magic happen. Otherwise people will be installing things that are not built the way that they think they are. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wednesday 29 July 2009 10:57:05 Doug Barton wrote: > Dan Mahoney, System Admin wrote: > >> I believe Mel is right here. 'make clean ; make config ; make' worked > >> for me. > > > > As does a second make after getting this error, but it's nonintuitive, > > and probably a ports bug. > > I'm not sure why 'make clean' is nonintuitive in the context of > changing OPTIONS. What is your expectation of how it should work? What he means is that make without arguments or make install as per handbook, will build the build target which will invoke the config target if OPTIONS changed or no options file is found. However, this is a corner case, as it applies to: - Ports that change PREFIX using OPTIONS - For which no options file is available or the OPTIONS list has changed - When the PREFIX is actually changed through toggling the appropriate option. This applies surely to less then 100 (probably more like a dozen) ports on the 18k that are in the tree and only affects people who do not use ports-mgmt software. As such it is not worth fixing, IMHO. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
Dan Mahoney, System Admin wrote: >> I believe Mel is right here. 'make clean ; make config ; make' worked >> for me. > > As does a second make after getting this error, but it's nonintuitive, > and probably a ports bug. I'm not sure why 'make clean' is nonintuitive in the context of changing OPTIONS. What is your expectation of how it should work? Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wed, 29 Jul 2009, Doug Barton wrote: Mel Flynn wrote: On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote: make: don't know how to make /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 Someone else had the same problem, and they also chose overwrite-base: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035. html But it was dismissed because he was using "sudo", however the real reason is because this problem goes away a second time. Most likely because that option changes PREFIX, so the BUILD_COOKIE changed, but the target was already in make's list of targets to make. After options are stored in /var/db/ports, BUILD_COOKIE will end in ._usr. I believe Mel is right here. 'make clean ; make config ; make' worked for me. As does a second make after getting this error, but it's nonintuitive, and probably a ports bug. -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
Mel Flynn wrote: > On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote: > >> make: don't know how to make >> /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop >> *** Error code 2 > >> Someone else had the same problem, and they also chose overwrite-base: >> >> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035. >> html >> >> But it was dismissed because he was using "sudo", however the real reason >> is because this problem goes away a second time. > > Most likely because that option changes PREFIX, so the BUILD_COOKIE changed, > but the target was already in make's list of targets to make. After options > are stored in /var/db/ports, BUILD_COOKIE will end in ._usr. I believe Mel is right here. 'make clean ; make config ; make' worked for me. Please let me know if it doesn't work for you. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote: > make: don't know how to make > /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop > *** Error code 2 > Someone else had the same problem, and they also chose overwrite-base: > > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035. >html > > But it was dismissed because he was using "sudo", however the real reason > is because this problem goes away a second time. Most likely because that option changes PREFIX, so the BUILD_COOKIE changed, but the target was already in make's list of targets to make. After options are stored in /var/db/ports, BUILD_COOKIE will end in ._usr. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Don't know how to make /usr/ports/dns/bind96/work/.build....
Hey all, I'm having a problem on multiple systems: With a clean port, in dns/bind96: I get the options screen, I select only "overwrite base" in addition to the defaults:, and after, I get this: make: don't know how to make /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 Stop in /usr/ports/dns/bind96. s1# Additional builds go fine. Someone else had the same problem, and they also chose overwrite-base: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035.html But it was dismissed because he was using "sudo", however the real reason is because this problem goes away a second time. -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
