2010/1/23 Ken Koehler <[email protected]>:
> Hello,
>
> I have recently done some upgrades on a subset of the software I
> installed a couple of years back using LFS/BLFS 6.2. In some cases I
> used BLFS svn-20091209, in others cases I was winging it. I thought that
> perhaps you might be interested in some of the problems I encountered.
> If not, sorry for wasting your time! :)
>
> Ken
>
> version numbers are the ones I used, for what it's worth...
>
> If anyone is interested, I will be happy to send a file with step by
> step commands I used to do the upgrades.
>
> 1) upgraded to kernel 2.6.32
> a) required e2fsprogs upgrade (used 1.41.8)
> b) somewhere around 2.6.26, the new SATA libs came into play and
> necessitated some config changes: CONFIG_IDE_ATAPI=y and
> CONFIG_IDE_GD_ATA=y and CONFIG_ATA=y and NOT CONFIG_BLK_DEV_IDE=y and
> CONFIG_BLK_DEV_IDEDISK=y (etc...)
> c) had to omit QLGE due to compile errors.
> d) needed to upgrade to cdparanoia 10.2 because of sata stuff
Hi Ken,
If you have other users, 2.6.32.4 or later (2.6.32.5 is currently the
latest) would be a good idea.
> 10) If you want gimp built-in help browser, you need: pycairo 1.4.0,
> pygobject 2.12.3, pygtk 2.10.6, libgtkhtml 2.11.1, gperf 3.0.4, icu
> 4.2.1, enchant 1.5.0, sqlite 3.6.16, libsoup 2.28.1, gstreamer 0.10.25,
> liboil 0.3.16, gstreamer base plugins 0.10.25, webkit gtk 1.1.15
Not totally agreed - I assume you are using webkit for epiphany -
the gimp seems to just need a working epiphany (I've reverted to
2.26 on this build, the drawbacks of 2.28 (failure to save password,
excess tendency to open new window instead of new tab) got to
me. I don't have pycairo, pygobject, or pygtk but gimp's help
(2.6.0-html-en) appears to be working.
I'm also puzzled about why you think enchant (I thought it was
primarily for abiword), sqlite (for me, it's for firefox/xulrunner, and
therefore epiphany 2-26 (but *not 2.28*), gstreamer and the plugins
are requirements for "web-browser" (i.e. epiphany). I've certainly
got them installed now (my build is complete), but I didn't think
they were essentials for this. OTOH, it's taken me some months
to realise that most of my gnome apps (*not* epiphany) have
had broken help since 2.26 : I had erroneously thought that
problem arrived in 2.28, so I can probably drop yelp and its
dependencies without worrying - I won't miss what I don't use.
> 11) I installed xscreensaver 5.10, and ended up (as before) setting it
> to just blank the screen because in a matter of minutes to hours it
> locked my system up tight (wouldn't even respond to Alt-SysRq)
>
At the moment, I'm trying to bisect mesa (again), to try
to discover what broke glxgears on my radeon r200 [ first
attempt in the 'stable' releases foundered on a merge,
looks as if they maintain the stable releases in CVS and
backport versions to the main git tree ]. I only looked at
that because xscreensaver-5.10 was locking up my
machine.
Actually, mine *does* respond to Alt-SysRq {S,U,B|O} :
R not useful, E and I not useful on a journalled filesystem.
At the moment, I think there is one problem which causes
glxgears to lock up, and a separate problem somewhere in
direct rendering which is the xscreensaver lockup. I say
that because even if I remove /usr/lib/dri (albeit with a
version of xorg-server built against mesa) so that glx
cannot be loaded, it still eventually locks up.
For me, it seemed ok if I built Mesa-7.5 (and then
build xorg-server against that), but YMMV.
I've had xscreensaver lockups in the past, perhaps with
similar versions to what you used to use, but for me it
has worked well for at least three years.
ĸen
--
After tragedy, and farce, "OMG poneys!"
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
