Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12552 comp.os.386bsd.misc:3335 comp.infosystems.gopher:10669 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!agate!alanc From: alanc@OCF.Berkeley.EDU (Alan Coopersmith) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc,comp.infosystems.gopher Subject: Re: Porting Gopher to FreeBSD Date: 21 Aug 1994 08:52:52 GMT Organization: U.C. Berkeley Open Computing Facility Lines: 22 Message-ID: <3374l4$3bm@agate.berkeley.edu> References: <32ralr$6sr@xanth.cs.odu.edu> Reply-To: alanc@ocf.berkeley.edu NNTP-Posting-Host: maelstrom-ether.berkeley.edu sturges@dustdevil.cs.odu.edu (Jonathan Sturges) writes in comp.os.386bsd.misc: |I FTP'd Gopher from UMN this week, and I'm having trouble compiling it. |I know, I know, the exact same Gopher client comes on the FreeBSD CD, but |I want to do some fine-tuning for my system. | |Anyhow, I can't get it to compile! With some playing around, I got it |up to the point where it tries to link all the object files, and it |bombs with the error: "ld: No such file or directory for gopher." | |From what I can tell, the error is caused by "-lgopher" being tacked on |to the end of the command line at link time. Therefore, I think it's |looking for a file called "libgopher.a", which I don't have anywhere on |my system or CD. libgopher.a should have been built in the object/ subdirectory before the client is built using it in the gopher/ subdirectory. -- ------------------------------------------------------------------------ Alan Coopersmith Internet: alanc@OCF.Berkeley.EDU Open Computing Facility or: alanc@CSUA.Berkeley.EDU University of California, Berkeley Bitnet: alanc@ucbocf