Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!classic.iinet.com.au!news.uoknor.edu!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!uunet!tandem!pacbell.com!ico.net!usenet From: Paul Stith <pauls@sum.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Ports confuse me... Date: 17 May 1995 19:55:05 GMT Organization: sum.com Lines: 31 Message-ID: <3pdkap$lkh@kane.ico.net> References: <3pd31k$ebd@hq.hq.af.mil> NNTP-Posting-Host: arthur.sum.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (Windows; I; 16bit) lpeters@scratchy.hq.af.mil (Leslie Peters) wrote: >I am a two-year veteran of Net- and now FreeBSD (currently at 2.0-950210), >yet I am baffled by ports. How does it work? I have looked at >the info that is in any particular program port and I can't make heads > Here's my low tech thoughts on them... Grab and recreate the entire tree for a particular port from the release or current directory (current is appropriate if your using a SNAP version). Change to the base directory that has the Makefile. Type "make" and pray it works. :) If your net connected, it will go out and grab the appropriate tar file... if it can't, browsing through the Makefile will let you know what the file _and_ expected extention are so you can grab it manually. The "pray" option will turn into the typical quest for what system options might work like netbsd, bsd or others. My understanding was that the ports on cdrom.com were supposed to be a bit more idiot proof. Of course they didn't as *me* to test them :). Adding -lcrypt as an additional library seems to make several programs like NCSA's httpd happier. Good luck. -ps Recent "victory" for us Apache is running on our PPP connected 2.0R system... www.sum.com