First fedora install attempt fails

Gene Heskett gene.heskett at
Sun Apr 25 22:24:09 UTC 2004

On Sunday 25 April 2004 15:04, Tom 'Needs A Hat' Mitchell wrote:
>On Sun, Apr 25, 2004 at 02:15:39PM -0400, Gene Heskett wrote:
>> On Sunday 25 April 2004 11:48, Tom 'Needs A Hat' Mitchell wrote:
>> >On Sun, Apr 25, 2004 at 06:34:32AM -0400, Gene Heskett wrote:
>> >> Using k3b in the auto burn mode, I made disks of the 4 iso's of
>> >> FC2-test2....
>> >
>> >      <-- note the Fedora RPM
>> I can wait a few I guess, at least konquerer is running. Will
>> test3 have the advansys driver available?  Not much good if its
>> not there, and the installer won't go on by it.
>It looks as if you have a good chance for advansys.
>[root at xtl2 root]# find / -print | grep advansys | snip&edit
>I also see it included on the oldest 2.6 stuff I still have handy
>(2.6.5-1.308) so it is not new and has a chance of having
>been tested.

Yes, I was one of the testors for the only patch it required to shut 
the compiler up, quite some time back.

>As always remember that test is test... stuff breaks.  But the best
>way to learn the nuts and bolts of things is to work with stuff that
>breaks from time to time.

In that case, I'd really like to figure out whats happened to gtk on 
my system, and why a broken attempt to make the new X managed 
to fsck it up so bad when it didn't actually (that I know of, a make 
install was never executed) install anything.  I've done everything 
but blow away the /usr/src/build dir, which is lndir'd to /usr/src/xc 
as they recommended.  The make was attempted from within 
the /usr/src/build directory, and will eventually bail out.  The 
errors were posted to the list, where they were given only 
token attention to without any suggestions actually bearing fruit.

One of the problems is that I have 3 pkg-config setups here, one 
in /usr/bin, one in /usr/local/bin, and one in the currently 
executing /root/kde3.2 tree.  This is what you get for using 
konstruct to build kde I guess. I would like to know howto combine 
all those pkg-config files into one, and simplify my $PKG_CONFIG_PATH 
env var.  Heck, just finding the actual configs is almost a stumble 
over it thing, and some of them have GOT to be stale.  There doesn't 
seem to be any real organization framework that says if glib-conf is 
in such and such, then it ought to be in a similar location in the 
other trees.  Locate says I've got these:


which is an rsync'd backup of the firewall machine, and


Which is for glib-1.2.8.  But when queried, it returns that glib is 
2.2.3 but 2.4.0-1 was installed by the checkinstall -R method.  And 
this is what keeps gtk+-2.4.0 from completion of its configure.

2 hours later:  I've done a bit of housecleaning in 
the /*/*/lib/pkgconfig dirs, and in the includes, getting rid of 
broken and stale links and files, and I'm getting a bit further with 
the gtk+-2.4.0-1 configure now and this error is not making a whole 
lot of sense to me, pango-1.4.0-1.i386.rpm is installed, and I nuked 
any /usr/local/include/pango-1.0/1.2.0 stuff I found since there was 
now a 1.4.0 in the same dir:
checking Pango flags... -I/usr/local/include/pango-1.0 
-I/usr/include/Xft2 -I/usr/include/freetype2 -I/usr/X11R6/include 
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include   
-Wl,--export-dynamic -L/usr/local/lib -lpangoxft-1.0 -lpangox-1.0 
-lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
configure: error:
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see

I've got a headache, one of the numerous excedrin varieties.  Possibly 
fixable with a shot of green tea.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

More information about the users mailing list