Date: Thu, 14 Feb 2002 17:32:58 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: <fenner@FreeBSD.ORG>, ports@FreeBSD.ORG Subject: Re: Possibly unbuildable ports reminder Message-ID: <p05101409b891eaf14fec@[128.113.24.47]> In-Reply-To: <200202141800.g1EI02r63383@freefall.freebsd.org> References: <200202141800.g1EI02r63383@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:00 AM -0800 2/14/02, <fenner@FreeBSD.ORG> wrote: >so you can easily check the status of ports that you maintain. In >addition, the list of ports with no MAINTAINER with build problems is > >http://people.freebsd.org/~fenner/errorlogs/ports@freebsd.org.html > >Since no one is responsible for these ports, the problem won't get >fixed unless someone on this list takes the initiative. For amusement value, I thought I'd check a few of these no-maintainer ports. For print/lout: ============================================================= ====================<phase 1: make checksum>================= 1765746 bytes transferred in 2.3 seconds (747.11 kBps) >> Checksum OK for lout-3.24.tar.gz. ====================<phase 2: make package>================== cat: stdout: No space left on device ============================================================= I glanced at one or two other ports, and they also seemed to be running out of diskspace somewhere... print/lout compiled OK on my freebsd-current system. (I have no idea what the port does, I just checked to see if it would compile) -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101409b891eaf14fec>