Date: Sun, 12 Dec 2004 00:08:14 +0000 From: Jez Hancock <jez.hancock@gmail.com> To: ports@freebsd.org Subject: Fwd: make broken in ports when DATE environment variable set Message-ID: <7b3c7f0b04121116085dcd7f4f@mail.gmail.com> In-Reply-To: <7b3c7f0b0412110035451d776@mail.gmail.com> References: <7b3c7f0b0412110035451d776@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Please cc me in reply. Forwarding this to ports@, no response from questions@. Is anyone interested in this or shall I just skulk off quietly? Thanks. ---------- Forwarded message ---------- From: Jez Hancock <jez.hancock@gmail.com> Date: Sat, 11 Dec 2004 08:35:54 +0000 Subject: make broken in ports when DATE environment variable set To: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> I've just gone to run the weekly 'portupgrade -ari' and found that the make process is failing anywhere in /usr/ports. An example of the output is: [8:28:01] root@users /usr/ports# portupgrade vim ---> Upgrading 'vim-6.3.16' to 'vim-6.3.45' (editors/vim) ---> Building '/usr/ports/editors/vim' with make flags: -DNO_GUI ===> Cleaning for libiconv-1.9.2_1 ===> Cleaning for libtool-1.5.10 ===> Cleaning for vim-6.3.45 20041211: not found *** Error code 127 Stop in /usr/ports/editors/vim. Manually changing to /usr/ports/editors/vim and issuing a 'make clean && make' command fails with the same error message as above. Anyway with some digging about I found this entry in /usr/ports/CHANGES: 20041209: AUTHOR: portmgr@FreeBSD.org The following changes were committed: * Define new macros: DATE, FMT, MKTEMP, OBJDUMP, and use command macro SORT. By coincidence I have a DATE variable set in my shell rc file and it appears to be this that is stopping the make process in the ports tree. Issuing 'unsetenv DATE' prior to running 'make' in the ports tree actually fixes the problem. My question then is whether this is something that is known or whether I should send a problem report or what? I've had a quick search for PRs relating to the problem but couldn't see anything. I can live with having to run 'unsetenv DATE' any time I need to modify the ports, but perhaps there are wider consequences of this problem? Cheers. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://freebsd.munk.nu/ - A FreeBSD Diary http://ipfwstats.sf.net/ - ipfw peruser traffic logging -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://freebsd.munk.nu/ - A FreeBSD Diary http://ipfwstats.sf.net/ - ipfw peruser traffic logging
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7b3c7f0b04121116085dcd7f4f>