Date: Mon, 17 May 2004 13:01:35 -0700 From: Kent Stewart <kstewart@owt.com> To: "Doug Poland" <doug@polands.org> Cc: freebsd-questions@freebsd.org Subject: Re: Help, GTK and my ports system broke! Message-ID: <200405171301.35705.kstewart@owt.com> In-Reply-To: <49312.69.48.112.138.1084823120.squirrel@email.polands.org> References: <4172.69.48.112.135.1084819160.squirrel@email.polands.org> <200405171232.19922.kstewart@owt.com> <49312.69.48.112.138.1084823120.squirrel@email.polands.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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. 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. Kent Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405171301.35705.kstewart>