[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: aRTSd and Glib 2.16.2....
From:       "David Jarvie" <lists () astrojar ! org ! uk>
Date:       2007-03-02 10:36:54
Message-ID: 13926.S0VKQUNDQxA=.1172831814.squirrel () www ! sensical ! net
[Download RAW message or body]

On Fri, March 2, 2007 1:19 am, Gary L. Greene, Jr. wrote:
> On Thursday 01 March 2007 20:36, David Jarvie wrote:
>> On Thursday 01 March 2007 23:51:23 Michael Pyne wrote:
>> > On Thursday 01 March 2007 17:49, David Jarvie wrote:
>> > > Finally, I have found out how to fix this problem. It's explained at
>> > > http://linuxfromscratch.org/pipermail/blfs-support/2006-May/059639.html
>> > > - if kdelibs is built with --enable-fast-malloc=full, it clashes
>> with
>> > > Glib's malloc calls. The solution is either to disable that option
>> when
>> > > building kdelibs, or to alter Glib's allocation handling at runtime
>> by
>> > > setting an environment variable.
>> >
>> > Seems odd that a kdelibs compile switch causes problems with arts.
>> > Wouldn't surprise me that it's related to two libraries both trying to
>> do
>> > a fast malloc though. ;)
>>
>> There isn't actually a problem between kdelibs and arts - it's the
>> interaction with Glib which goes wrong :)
>
> David,
>
> Thank you for saving me from a load of grief with this issue. This likely
> should get put in an FAQ or something somewhere....

I've described it in the KDE 3.5 build FAQ at
http://techbase.kde.org/Getting_Started/Build/FAQ#Some_other_common_problems.
Perhaps it should also be referenced in some run-time oriented page also,
but I'm not sure where would be appropriate.

-- 
David Jarvie.
KAlarm author & maintainer.
http://www.astrojar.org.uk/linux/kalarm.html

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]