From owner-freebsd-questions Fri May 15 04:52:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07935 for freebsd-questions-outgoing; Fri, 15 May 1998 04:52:42 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dove.peace.com.my (peace.com.my [202.184.153.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07911 for ; Fri, 15 May 1998 04:52:31 -0700 (PDT) (envelope-from panda@peace.com.my) Received: from lovebox (love.com.my [202.184.153.17]) by dove.peace.com.my (8.8.5/8.8.5) with SMTP id TAA01118; Fri, 15 May 1998 19:32:54 +0800 (SGT) Date: Fri, 15 May 1998 19:32:54 +0800 (SGT) Message-Id: <3.0.32.19980515195504.00976e40@peace.com.my> X-Sender: panda@peace.com.my X-Mailer: Windows Eudora Pro Version 3.0 (32) To: Ruslan Ermilov , questions@FreeBSD.ORG From: chas Subject: Re: gmake : is the port ok ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Ruslan, Although I did get gmake to install somehow, I guess I'd better upgrade to 2.2.6 for a cleaner install of gcc2.8.1 and its partners in crime; this seems to be a recurring problem with 2.2.1 and error messages like : timestamp.h:33: hash_set.h: No such file or directory *** Error code 1 when hash_set.h does indeed exist : /usr/local/lib/gcc-lib/i386-unknown-freebsd2.2.6/2.8.1/ include/g++/hash_set.h Onward 2.2.6 :) cheers again, chas >On Fri, May 15, 1998 at 04:59:48PM +0800, chas wrote: >> Installing gmake from the ports collection on FBSD 2.2.1, I >> ran into the following error : > >Builds and installs ok without any problems on -stable. > >-- >Ruslan Ermilov System Administrator >ru@ucb.crimea.ua United Commercial Bank >+380-652-247647 Simferopol, Crimea >2426679 ICQ Network, UIN > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message