On Sun, Oct 07, 2012 at 07:57:54AM +0100, lux-integ wrote:
> Greetings,
>
> I just built clfs (amd64) on a computer. I installed glib-2.32.4 in the
> process. I now stated on a post CLFS build with python-2.7.3 et al. After
> installing python and libiconv glib-2-32.4 will not (re)compile. Glib-2.34
> compiles though.
>
> So to my question(s): Is it advisable or indeed necessary to yank out the
> problematic glib-2.32.4 before upgrading to glib-2.34 or is installing
> glib-2.34 over glib-2.32.4 recommended?
>
I won't ask why you installed libiconv, because I'm not really
interested in the answer (in LFS we point out that it isn't needed
with glibc, don't we ?), but I do wonder why you needed to recompile
glib. For me, 2.32.4 built ok after Python-2.7.3.
Whatever, using the current release of glib will be fine - except
for any cases where it breaks ;) I know that people *have* upgraded
glib, so I think it is unlikely to cause a problem. But looking at
the whole desktop, almost any change to a graphics toolkit can cause
a problem somewhere. Typically, you might need to use the latest
atk, pango, gdk-pixbuf, gtk+-{2,3}, and if you are using old
versions of applications that use gtk2/3 some might be upset by the
newer versions - in the past year, BLFS had to use a development
version of pango because of a change in, ISTR, glib : what is
currently in the book for gnome should be reasonably-well tested with
the versions of glib etc that are in the book, other packages which
date from before gnome-3.6 might have issues.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
