Can't install ruby-bdb on RELEASE-6.1
Donald J. O'Neill
donaldjoneill at gmail.com
Fri Jul 21 16:12:26 UTC 2006
On Friday 21 July 2006 09:45, Jim Trigg wrote:
> On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote:
> > Jim Trigg wrote:
> >> I'm setting up a new system with 6.1-RELEASE, and I forgot to install
> >> portupgrade from a package during the OS install. ruby-bdb fails to
> >> build, complaining that it doesn't know how to make 'all' (it doesn't
> >> specify which directory it's in, but it's right after it runs
> >> extconf.rb). Any clues?
> >> (Note: when I posted this earlier I mentioned changing LOCALBASE.
> >> Further
> >> testing has shown that it fails regardless of LOCALBASE setting.)
> > Make sure you have a fresh ports tree.
> > May be you should reinstall ruby.
> I did have a fresh ports tree, and I've tried that.
> Full list of what I've done:
> - Installed 6.1-RELEASE from CD
> - Installed cvsup
> - Ran cvsup ports-all
Please explain this a little more. What's ports-all? Is that the name of a
sup-file you're using? If so, what's in it?
> - Attempted to install portupgrade with BDB4; ruby-bdb failed to build
What is the failure message. The failure could have occurred at the beginning
of ruby-bdb. Do you have /usr/ports/databases/db(what version?) installed?
> - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to
Are you saying you uninstalled the ports-tree and reinstalled it using cvsup,
or are you saying you uninstalled the installed ports?
Is there a reason you are messing with LOCALBASE? Is this a linux thing you're
> - Attempted to install portupgrade with BDB4; ruby-bdb failed to
> build - Uninstalled all ports, changed LOCALBASE back to /usr/local
> - Installed ruby18, attempted to install ruby-bdb; ruby-bdb failed to build
> - Uninstalled all ports, changed LOCALBASE back to /opt
> - Installed portupgrade with BDB1.
Jim - I would suggest that you use portsnap rather than cvsup for the ports
tree. Cvsup will work, and it will work fine, but portsnap will work better
and faster and with less problems.
I suggest you do it this way: actually the way I do it is:
perf500# script /home/script/portsnap/20060721 (that's today's date)
Script started, output file is /home/script/portsnap/20060721
perf500# portsnap fetch extract
You don't have to run 'script', but in case there's a failure, I like to have
something to look at to see if I can find what went wrong. You could just
run 'portsnap fetch extract'.
NOTE: unless you blow the ports-tree off, you only run 'portsnap fetch
extract' once. After that you use: 'portsnap fetch update'.
The first time you do this, it takes a bit of time to complete. After that, on
my systems anyway, it takes about 2 minutes as compared to 15 to 20 using
cvsup. If you're blowing off the ports-tree and rerunning cvsup to install
it, portsnap is going to be way faster.
What is the output from 'df -m'?
Do you have anything in /etc/make.conf?
I would suggest installing /usr/ports/databases/db43 before trying to install
portupgrade. It might work out a little better for you.
More information about the freebsd-ports