Re: 4.8-release, unable to build any port

2010-12-31 Thread Dan Harnett
On Fri, Dec 31, 2010 at 01:19:26PM -0500, Chad M Stewart wrote: > > From root's .profile > > if [ -x /usr/bin/tset ]; then >if [ X"$XTERM_VERSION" = X"" ]; then >eval `/usr/bin/tset -sQ '-munknown:?vt220' $TERM` >else >eval `/usr/bin/tset -IsQ '-mun

Re: 4.8-release, unable to build any port

2010-12-31 Thread Chad M Stewart
On Dec 31, 2010, at 1:00 PM, Chad M Stewart wrote: > > Off list someone suggested using 'env -i make package' and that worked. That > solves my immediate problem. I'm using ESXi so I can easily create new > systems for testing, etc.. I did a fresh install from install48.iso and a > downl

Re: 4.8-release, unable to build any port

2010-12-31 Thread Chad M Stewart
Off list someone suggested using 'env -i make package' and that worked. That solves my immediate problem. I'm using ESXi so I can easily create new systems for testing, etc.. I did a fresh install from install48.iso and a downloaded ports.tar.gz file. I then 'ssh r...@host' to connect and

Re: 4.8-release, unable to build any port

2010-12-31 Thread Ian McWilliam
On 1/01/2011 2:46 AM, Chad M Stewart wrote: On Dec 31, 2010, at 5:52 AM, Marc Espie wrote: Have you looked for $< around the place in bsd.port.mk where it says it sees it ? A grep reveals no such combination in the file. :( The only thing left is to try removing part of that line until th

Re: 4.8-release, unable to build any port

2010-12-31 Thread Chad M Stewart
On Dec 31, 2010, at 5:52 AM, Marc Espie wrote: > Have you looked for $< around the place in bsd.port.mk where it says it sees > it ? A grep reveals no such combination in the file. :( > > The only thing left is to try removing part of that line until the error > goes away, and then figure ou

Re: 4.8-release, unable to build any port

2010-12-31 Thread Marc Espie
Have you looked for $< around the place in bsd.port.mk where it says it sees it ? The only thing left is to try removing part of that line until the error goes away, and then figure out where it comes from.

Re: 4.8-release, unable to build any port

2010-12-30 Thread Chad M Stewart
On Dec 30, 2010, at 8:33 PM, Edd Barrett wrote: > On Thu, Dec 30, 2010 at 08:09:54PM -0500, Chad M Stewart wrote: >> Various reasons, but your right using packages would be faster. This really >> gets me as I've built many ports before, usually very easy to do. >> > > Have you aliased 'make

Re: 4.8-release, unable to build any port

2010-12-30 Thread Edd Barrett
On Thu, Dec 30, 2010 at 08:09:54PM -0500, Chad M Stewart wrote: > Various reasons, but your right using packages would be faster. This really > gets me as I've built many ports before, usually very easy to do. > Have you aliased 'make' to anything? Checked mk.conf? Where did you get ports f

Re: 4.8-release, unable to build any port

2010-12-30 Thread Chad M Stewart
On Dec 30, 2010, at 7:42 PM, Jacob Meuser wrote: > why aren't you using packages? I bet you'd be done setting up your > system already. Various reasons, but your right using packages would be faster. This really gets me as I've built many ports before, usually very easy to do. -Chad

Re: 4.8-release, unable to build any port

2010-12-30 Thread Jacob Meuser
why aren't you using packages? I bet you'd be done setting up your system already. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org

Re: 4.8-release, unable to build any port

2010-12-30 Thread Mark Solocinski
Do you have anything in /etc/mk.conf? Just a thought. On Thu, 30 Dec 2010 17:48:04 -0500, Chad M Stewart wrote: > Fresh install of 4.8, all sets installed, from install48.iso plus the > ports.tar.gz from ftp site. At first I thought this was a problem with a > specific port, but alas my testing

4.8-release, unable to build any port

2010-12-30 Thread Chad M Stewart
Fresh install of 4.8, all sets installed, from install48.iso plus the ports.tar.gz from ftp site. At first I thought this was a problem with a specific port, but alas my testing is showing that no ports will work. I'm not new to working with ports, but I have not come across this error before