On Wednesday 22 October 2003 05:37 am, ivan georgiev wrote:
> > What versions of ruby do you have installed? I can remember back a
> > few versions, that uninstalling portupgrade and ruby and then
> > making and installing portupgrade was faster than fighting the
> > problems with ruby.
> > Kent
> -su-2.05b# ruby -v
> ruby 1.6.8 (2003-03-26) [i386-freebsd5]
I don't have any idea. It looks like a source/configuration/make error of some
type. My version is the also the following
ruby 1.6.8 (2003-03-26) [i386-freebsd5]
I didn't have any problem re-building portupgrade and the ruby tools using
portupgrade -pufr ruby.
My last cvsup was on 15 Oct, which is a little bit old. So, I recvsuped
ports-all and, as always, re-built INDEX and INDEX.db. I use "make index" to
update INDEX and the only refuse I have is "ports/INDEX-5". Since I rebuild
the INDEXs everytime I cvsup ports-all, there isn't any point in having cvsup
grab a current copy of INDEX-5, which is always out of date. After INDEX.db
was rebuilt, I reran the -pufr update of ruby and didn't have any problems.
My setup is KISS simple. I use the stock gcc that comes with 5-current. I
don't use options for the build flags in /etc/make.conf. My port tree is also
located in /usr/ports. The only thing different on my FreeBSD-5-current
machine is the packages produced by portupgrade are stored on a different fs
called /usr3/All. That shouldn't make any difference to the build process.
The iso images for version 5.1-Release were built on 5 Jun, which is several
months after the last changes to ruby-1.6.8.
A uname -a of my system shows
FreeBSD opal 5.1-CURRENT FreeBSD 5.1-CURRENT #41: Wed Oct 15
You aren't the only one with problems and it may be something simple like a
trashed ruby patch file. I haven't seen them re-roll the tarballs for ruby,
which is only seen when the checksums don't agree. Since I don't have a
5.1-release system, there isn't much else that I can try.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"