From owner-freebsd-questions Fri Jan 18 16:40:59 2002 Delivered-To: freebsd-questions@freebsd.org Received: from Mail6.mgfairfax.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 27FCC37B405 for ; Fri, 18 Jan 2002 16:40:54 -0800 (PST) Received: from there ([24.168.212.227]) by Mail6.mgfairfax.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Fri, 18 Jan 2002 19:40:12 -0500 Content-Type: text/plain; charset="iso-8859-1" From: Ray Kohler To: "Craig Burgess" , Subject: Re: ruby/portupgrade errors + other stuff Date: Fri, 18 Jan 2002 19:43:17 -0500 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <018281240001312FE6@Mail6.mgfairfax.rr.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 18 January 2002 06:19 pm, Craig Burgess wrote: > > from installing portupgrade: > ======================= > ===> portupgrade-20020117 depends on file: > /usr/local/lib/ruby/site_ruby/1.6/a > lpha-freebsd4/fnmatch.so - not found > ===> Verifying install for > /usr/local/lib/ruby/site_ruby/1.6/alpha-freebsd4/fnmatch.so in > /usr/ports/devel/ruby-fnmatch > ===> Returning to build of portupgrade-20020117 > . . . > ===> portupgrade-20020117 depends on file: > /usr/local/lib/ruby/site_ruby/1.6/uri.rb - not found > ===> Verifying install for > /usr/local/lib/ruby/site_ruby/1.6/uri.rb in > /usr/ports/net/ruby-uri > ===> Returning to build of portupgrade-20020117 > ======================= Try installing ruby-fnmatch and ruby-uri ports directly and see what they do when you try to build them. It looks like both think they are installed but really arent. You might want to do 'make -DFORCE_PKG_REGISTER install' on them just for good measure. -- Ray Kohler Parts that positively cannot be assembled in improper order will be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message