Date: Wed, 31 Dec 2003 17:41:58 -0600 (CST) From: Paul Seniura <pdseniura@techie.com> To: freebsd-gnome@freebsd.org, freebsd-perl@freebsd.org, freebsd-ports@freebsd.org Cc: Paul Seniura <pdseniura@techie.com> Subject: I'm having an awful time updating gdm2 and other ports Message-ID: <20031231234158.8EF1C5C29@techpc04.okladot.state.ok.us>
next in thread | raw e-mail | index | archive | help
The root of this whole problem is that starting-up Gnome2 gets stuck after it shows the splash screen. Or if I have it bring up the Login Panel first, it won't go past you entering your id & password. I have no tell-tale signs in the logs that show what the problem actually is.
I'm now trying to 'portupgrade gdm2' to get it updated with yesterday's CVS changes (I'm actually using CTM to track -Current).
Talk about "when it rains, it pours..."
The Makefile for gdm2 does no checking whatsoever for perl itself and perl macros in its BUILD_DEPENDS, as some other ports properly do.
Earlier this week I had done a 'use.perl port' and have had no problems with configure/installing new ports or updating them.
Not until yesterday's gdm2 changes came thru, that is.
This is what 'portupgrade gdm2' shows today:
[...]
===> Configuring for gdm2-2.4.4.6
checking for intltool >= 0.21... 0.28 found
checking for perl... /usr/bin/perl
configure: error: XML::Parser perl module is required for intltool
===> Script "configure" failed unexpectedly.
Please report the problem to gnome@FreeBSD.org [maintainer] and attach
the "/src/ports/x11/gdm2/work/gdm-2.4.4.6/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
Stop in /src/ports/x11/gdm2.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade1357.57 make
** Fix the problem and try again.
[...]
So I did 'use.port system' and 'rehash' and checked to see that /etc/make.conf was updated properly and the symlinks -- and even rebooted -- to no avail, because 'perl -v' is still showing 5.8.2 and will still cause the above problem.
Yes I have seen PR/55760 but what good will it do if the maintainer won't commit that huge patch to make it 'official'? Will 55760 fix _this_ problem with gdm2 anyway? I don't see how, because gdm2 itself has no logic to check for perl and co.
I have no idea what other perl modules are required by gdm2 and in which p5-* collection.
So I thought to try installing a meta-port such as print/p5-GnomePrint to get a bunch of p5-* parts installed which would include the XML::Parser module among others, and hopefully enough of them to make gdm2 happy.
"When it rains, it pours..."
...because now doing a portupgrade --new for p5-GnomePrint is griping thusly:
[...]
install -C -o root -g wheel -m 444 /src/ports/www/gtkhtml/work/gtkhtml-1.1.10/gtkhtmlConf.sh /usr/X11R6/etc/gtkhtmlConf.sh
===> Running ldconfig
/sbin/ldconfig -m /usr/X11R6/lib
===> Registering installation for gtkhtml-1.1.10_2
===> Returning to build of p5-GnomePrint-0.7009
===> Configuring for p5-GnomePrint-0.7009
Cannot load Gtk::Install::Files: Can't locate Gtk/Install/Files.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.8.2/mach
/usr/local/lib/perl5/site_perl/5.8.2 /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.8.2
/BSDPAN /usr/local/lib/perl5/5.8.2/mach /usr/local/lib/perl5/5.8.2 .) at ../Depends.pm line 93.
*** Error code 2
Stop in /src/ports/print/p5-GnomePrint.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade44917.47 make
** Fix the problem and try again.
[...]
The portupgrade run above had already installed a ton of prerequisite ports, and was "returning" to finish p5-GnomePrint.
Something got missed somewhere, but I can't see where (I do the 2>&1 thing and 'tee' the output to a file for later review).
I need help, please!
I'm having similar trouble with KDE taking forever to start up, and once it is ready, it again takes forever to bring up a simple "Open File" dialog, no matter what app.
If I keep getting into this much trouble with FreeBSD, I won't be able to show how free software can be used in our agency! 'They' will tell me to drop this project, and we'll forever be stuck with M$!
Thank you,
-- Paul Seniura
System Specialist
State of Okla. D.O.T.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031231234158.8EF1C5C29>