From owner-freebsd-ports Tue Feb 29 18: 9:57 2000 Delivered-To: freebsd-ports@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 9CF4837BCCA; Tue, 29 Feb 2000 18:09:52 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA92045; Tue, 29 Feb 2000 21:09:48 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 29 Feb 2000 21:09:48 -0500 (EST) From: Chuck Robey To: Kenneth W Cochran Cc: freebsd-ports@freebsd.org, chuckr@freebsd.org Subject: Re: Trouble installing xpdf port in 3.4-stable In-Reply-To: <200002291503.KAA27702@world.std.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 29 Feb 2000, Kenneth W Cochran wrote: > Hi... > > I'm having trouble building & installing xpdf on FreeBSD > 3.4-stable, as of 2000/02/28, installed from 3.4-release CDs (& > cvsup'ed every week or two since). I've never updated ports. > > Xpdf does not exist on the CDs, but there is no notation of > this. I tried the make while online, so it could download > things & it stopped in config. So I tried the make again, this > time using "make >& make.log" and am attaching that log. > > IIRC I had the same problem with the "fresh" 3.4-release CD > install (no distfile). > > Ideas? Take a closer look at the printout, it's not a xpdf problem, it dies while making t1lib, a dependency. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message