From owner-freebsd-questions Mon Feb 2 06:04:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02325 for questions-outgoing; Mon, 2 Feb 1998 06:04:55 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02308 for ; Mon, 2 Feb 1998 06:04:48 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.8/8.8.3) id JAA05251; Mon, 2 Feb 1998 09:04:27 -0500 (EST) Message-ID: <19980202090426.30730@emu.sourcee.com> Date: Mon, 2 Feb 1998 09:04:26 -0500 From: Norman C Rice To: Frank Griffith Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Sunclock References: <01BD2F9B.4A759C60@fast1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <01BD2F9B.4A759C60@fast1>; from Frank Griffith on Mon, Feb 02, 1998 at 05:27:43AM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" On Mon, Feb 02, 1998 at 05:27:43AM -0600, Frank Griffith wrote: > I have FreeBSD 2.2.5 running on a 486-66 system with 32 meg RAM. > In have the X-Windows program running, but would now like to get the > Sunclock program working. > > Here are the commands I am using to start the setup for Sunclock: > > # cd /usr/ports/astro/sunclock > # make install Have you tried using `make' before the `make install'? -- Regards, Norman C. Rice, Jr. > > I then see the following messages: > > >> Checksum OK for sunclock1.3.tar.Z > ===> Configuring for sunclock-1.3 > mv -f Makefile Makefile.bak > imake -DUseInstalled - I/usr/X11R6/lib/X11/config > Imakefile.c.8: Imake.tmpl: No such file or directory > imake: Exit code 33. > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > I have read the X-Windows docs until I'm blue and read the > how to on installing ports over and over again. But no dice. > Can anyone explain this one?