From owner-freebsd-sparc64@FreeBSD.ORG Wed May 28 19:34:17 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDA9A37B401 for ; Wed, 28 May 2003 19:34:17 -0700 (PDT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F06E843F93 for ; Wed, 28 May 2003 19:34:16 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.9/8.12.9) with ESMTP id h4T2YFPx009235; Wed, 28 May 2003 22:34:15 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20030528234914.GA1987@crow.dom2ip.de> References: <20030528214711.GA94049@rot13.obsecurity.org> <20030528220215.GA94270@rot13.obsecurity.org> <20030528222144.GA667@crow.dom2ip.de> <20030528222244.GA94418@rot13.obsecurity.org> <20030528234914.GA1987@crow.dom2ip.de> Date: Wed, 28 May 2003 22:34:14 -0400 To: Thomas Moestl , Kris Kennaway From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 cc: freebsd-sparc64@freebsd.org Subject: Re: portversion/portupgrade X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2003 02:34:18 -0000 At 1:49 AM +0200 5/29/03, Thomas Moestl wrote: >On Wed, 2003/05/28, Kris Kennaway wrote: > > > > Hmm, I thought knu made a change to bsd.ruby.mk some time > > ago that switched sparc64 over to using ruby-devel, but the > > problem persists with freshly-built ports. > >Hmmm, yes, I must have misremebered that. >The bug really seems to be in ruby-bdb1, which is also marked >NOT_FOR_ARCHS=sparc64. > >I just got portupgrade to work on my box, however by changing >the dependency in the Makefile from ruby-bdb1 to ruby-bdb >(as already hinted in a comment) and dropping the attached >patch into files/ to make it use ruby-bdb instead of ruby-bdb1 >by default. I haven't upgraded portupgrade and ruby on my sparc64 box for awhile. It was working when I started to investigate this. I rebuilt ruby, and after that I started having problems with portupgrade. Note that in my case ruby-bdb1 was already installed, so the dependency-checking did not fail, although I was getting errors from portupgrade commands. One portupgrade problem led to another, and eventually I just moved aside /var/db/pkg and /usr/local, and started over. I do not have many ports installed, so that was a simple solution. I followed the suggestions from Thomas, and it seems to be going OK for me. There were a few oddities in building things though, which I should figure out. Initially I somehow managed to build portupgrade without building ruby-bdb. It was even working fine, until I did tried 'portversion' and that complained about a stale-dependency (the missing ruby-bdb). However I'm doing this on a rather slow machine, and at this point I need to leave for the day. I'll try to look into it some more tomorrow. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu