Help, GTK and my ports system broke!

[Doug Poland]

Kent Stewart said:
> On Monday 17 May 2004 12:45 pm, Doug Poland wrote:
>> Kent Stewart said:
>> > On Monday 17 May 2004 12:27 pm, Doug Poland wrote:
>> >> > Kent Stewart said:
>> >> >> On Monday 17 May 2004 11:58 am, Doug Poland wrote:
>> >> >>> Kent Stewart said:
>> >> >>> > On Monday 17 May 2004 11:39 am, Doug Poland wrote:
>> >> >>> >> Greetings,
>> >> >>> >>
>> >> >>> >> I was running a portupgrade -a this morning on my
>> >> >>> >> 5.2.1-RELEASE system on a freshly cvsup'd ports tree.  The
>> >> >>> >> first hint of trouble was gtk-2.4.1 failed to upgrade from
>> >> >>> >> 2.4.0...
>> >> >>> >
>> >> >>> > You need to visit
>> >> >>> > http://www.freebsd.org/gnome/docs/faq26.html
>> >> >>> >
>> >> >>> > They had an update script that is supposed to take you from
>> >> >>> > 2.4 to 2.6 and you need to do that upgrade. You also have a
>> >> >>> > lot of cpu time usage ahead of you.
>> >> >>>
>> >> >>> I'm on may way over there but, I'm not running Gnome on this
>> >> >>> system.
>> >> >>
>> >> >> You may not be. I run KDE but you still have pieces such as
>> >> >> glib and gtk.
>> >> >
>> >> > Thanks Kent.  I too have glib and gtk running, or not :(   I'll
>> >> > start the script upgrade now.  Thanks for the tip.
>> >>
>> >> Well, that was too quick.  Python2.3 core dumped in stage 2 of 5
>> >> and everything failed. My world is looking pretty bleak right
>> >> about now.
>> >
>> > Look at what is out of date. You may have to update ruby,
>> > portupgrade, and python before you try glib.
>>
>> I cannot run portupgrade or make on any port, up-to-date or not.  For
>> example, lang/ruby18 yields...
>>
>> ===>   ruby-1.8.1.2004.05.02 depends on file:
>> /usr/local/lib/libcrypto.so.3 - found ===>  Configuring for
>> ruby-1.8.1.2004.05.02
>> /usr/bin/touch
>> /usr/ports/lang/ruby18/work/ruby-1.8.1-2004.05.02/configure
>> configure: WARNING: you should use --build, --host, --target checking
>> build system type... i386-portbld-freebsd5
>> checking host system type... i386-portbld-freebsd5
>> checking target system type... i386-portbld-freebsd5
>> checking for i386-portbld-freebsd5-gcc... cc
>> checking for C compiler default output... configure: error: C
>> compiler cannot create executables
>> ===>  Script "configure" failed unexpectedly.
>> Please report the problem to knu at FreeBSD.org [maintainer] and attach
>> the "/usr/ports/lang/ruby18/work/ruby-1.8.1-2004.05.02/config.log"
>> including the output of the failure of your make command. Also, it
>> might be a good idea to provide an overview of all packages installed
>> on your system (e.g. an `ls /var/db/pkg`).
>> *** Error code 1
>
> Did you run portsdb -uU after you cvsup'ed ports-all. I have never seen
> a message like what your are seeing on the lists.
>
Yes, I ran portsdb -uU.  However, portsdb will not run now, python2.3
core dumps.

> FWIW, your upgrade is old enough that you may have problems with ruby
> and portupgrade.  I deleted ruby-* and portupgrade and then did a make
> install in portupgrades directory.
>
My system was reasonably up-to-date (about two weeks) before this
disaster.  IIRC, my list of ports to upgrade included the latest changes
to XFree86-4.3-libs, gtk, glib, python, ruby, and a few others.  I may just
blow away all ports, and start from scratch.

-- 
Regards,
Doug