Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Kicker on Ultra 10 SPARC
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on Sparc
View previous topic :: View next topic  
Author Message
tunkaflux
Tux's lil' helper
Tux's lil' helper


Joined: 20 Aug 2003
Posts: 76

PostPosted: Sat Apr 02, 2005 8:36 pm    Post subject: Reply with quote

Hey chance2105, thanks for the tips! I recompiled kdelibs, qt and kdebase with debug and kdeenable and kicker works!

Btw, if I remove "-mcpu=ultrasparc" what exactly does that imply?
Back to top
View user's profile Send private message
chance2105
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 112
Location: Norman, OK USA

PostPosted: Sun Apr 03, 2005 2:46 am    Post subject: Reply with quote

Weeve: compiling qt with -mtune=ultrasparc yields a still-working kicker. C(XX)FLAGS then total are "-O2 -mtune=ultrasparc -pipe"

tunkaflux: Removing -mcpu=ultrasparc from C(XX)FLAGS changes how gcc optimises code when compiled (with packages that heed them). There's all kinds of good into on the gcc man page.
Back to top
View user's profile Send private message
chance2105
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 112
Location: Norman, OK USA

PostPosted: Mon Apr 04, 2005 10:15 am    Post subject: Reply with quote

ibtim13 wrote:
I'd also like to get openoffice to work one of these days, it always
fails during compiling saying that the java VM detected an error in the external
code.



There is an easy fix for that. Compile openoffice with USE="-java". Java on sparc is .. evil ATM.
Back to top
View user's profile Send private message
chance2105
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 112
Location: Norman, OK USA

PostPosted: Mon Apr 04, 2005 10:22 am    Post subject: Reply with quote

retroman wrote:

Is there anyone out there with an Ultra60 that can run kde 3.3 or kde 3.4? What kernel do you use? If its 2.6, how did you get the mouse to work.

im so annoyed

Jordan



To get a sun mouse to work on a U60 with a 2.6 kernel, you have to include not only the sun mouse input driver .. But also the appropriate serial drivers. Yes, it seems a gimme .. But in 2.4, the code is automatically compiled in, and in 2.6 it isn't.
Back to top
View user's profile Send private message
huseyin
n00b
n00b


Joined: 15 Mar 2005
Posts: 12

PostPosted: Thu Apr 07, 2005 9:35 pm    Post subject: Reply with quote

I had the exact kicker problem on an ultra 60 / kde 3.4 .
As change2105 said, adding "use debug kdeenablefinal" and recompiling qt solved my problem. And I still keep the -O3 -mcpu=ultrasparc -mtune=ultrasparc.

While having problems with kicker, I also had crash problems with kontact. The program opens fines, but whenever I wanted to do something, say add something to the calendar or to do list, the whole program complained about "fatal error KDirWatch" and crashed. I guess compiling with "debug kdeenablefinal" solved that too.

Now I dont want to compile all my programs with debug and kdeenablefinal. Is there a way to only compile qt with this setting and the rest without it and make it stay that way even after emerge -sync and update world?

thanks,

huseyin
Back to top
View user's profile Send private message
retroman
Apprentice
Apprentice


Joined: 18 Nov 2004
Posts: 207
Location: Stuttgart

PostPosted: Mon Apr 11, 2005 2:23 pm    Post subject: This is a waste of time. Reply with quote

Everyone has their own idea about why they believe kicker to be broken. Nobody has yet to provide an actual reason.
Once again 2 more re emerges of QT with different configuration combinations as recommended from this thread yeilded nothing. Nor has anyone updated the bug ticket on this since myself a month ago.

At this point, Im going to wait on a real answer as to why it doesnt work. multiple combinations of use flags and cflags for endless re-compiles are a waste of time.

jordan
Back to top
View user's profile Send private message
ThorstenHirsch
Tux's lil' helper
Tux's lil' helper


Joined: 25 Sep 2003
Posts: 111

PostPosted: Mon Apr 18, 2005 1:20 pm    Post subject: Reply with quote

The same problem here.
Using kdeenablefinal and recompiling qt, kdelibs, kdebase did not solve the problem. So my next try will be to add USE="debug" when recompiling qt. However, a better solution would be fine - so are there any new ideas, anyone?
Back to top
View user's profile Send private message
retroman
Apprentice
Apprentice


Joined: 18 Nov 2004
Posts: 207
Location: Stuttgart

PostPosted: Mon Apr 18, 2005 6:31 pm    Post subject: Reply with quote

Heres a good solution



emerge perlpanel



a working replacment for kicker


jordan
Back to top
View user's profile Send private message
i-right-i
Tux's lil' helper
Tux's lil' helper


Joined: 08 Nov 2004
Posts: 118
Location: Chandler, AZ USA

PostPosted: Mon Apr 18, 2005 7:07 pm    Post subject: KDE Kicker = Crapola Reply with quote

I ended up ditching KDE all together. I keep it installed and then emerge XFCE. You can use all the KDE apps through it. It even builds most of the menus for you. And thier kicker works good.

i-right-i
_________________
Gentoo on x86
Gentoo on SPARC
Back to top
View user's profile Send private message
ThorstenHirsch
Tux's lil' helper
Tux's lil' helper


Joined: 25 Sep 2003
Posts: 111

PostPosted: Tue Apr 19, 2005 9:36 am    Post subject: Reply with quote

None of the workarounds worked for me. :(
I re-compiled qt, kdelibs and kdebase with these 2 USE flags and I also tried it with the different C(XX)FLAGS.
Back to top
View user's profile Send private message
i-right-i
Tux's lil' helper
Tux's lil' helper


Joined: 08 Nov 2004
Posts: 118
Location: Chandler, AZ USA

PostPosted: Fri Jun 03, 2005 5:00 pm    Post subject: Anything yet on a fix? Reply with quote

Still waiting to see this thing get resolved, any progress?

i-right-i
_________________
Gentoo on x86
Gentoo on SPARC
Back to top
View user's profile Send private message
gust4voz
Retired Dev
Retired Dev


Joined: 09 Sep 2003
Posts: 373
Location: Buenos Aires, Argentina

PostPosted: Fri Jun 03, 2005 5:34 pm    Post subject: Reply with quote

Using qt-3.3.2* gets kicker working for me and a couple other people.
At the moment i'm trying to make a patch to fix qt-3.3.4* but it's proving elusive, specially since qt takes quite some time to build and i lack serious horsepower to do so.
I can't officially recommend using qt-3.3.2 since it has some other problems (including security), and you'll have to pull the necessary files off the attic since it's no longer in portage.
_________________
Gustavo Zacarias
Gentoo/SPARC monkey
Back to top
View user's profile Send private message
elec8070
n00b
n00b


Joined: 07 Jun 2005
Posts: 2

PostPosted: Tue Jun 07, 2005 10:39 am    Post subject: Reply with quote

Weeve wrote:
What if you try -mtune=ultrasparc instead of -mcpu=ultrasparc?


Jusr recompiling QT with -mtune instead of mpcu got kicker working for me :-)

Thanks
Back to top
View user's profile Send private message
i-right-i
Tux's lil' helper
Tux's lil' helper


Joined: 08 Nov 2004
Posts: 118
Location: Chandler, AZ USA

PostPosted: Tue Jun 07, 2005 3:42 pm    Post subject: KDE Kicker on Sparc Reply with quote

I had already tried using mtune instead of mcpu but that didn't do anything for me.

I have broken down, and decided to shelf my Ultra 10 for now until this gets resolved. I have resurected an older p3 500 x86 box that I will turn into a desktop workstation. In fact KDE is compiling now =)

I will be sure to frequent these boards hoping that this one day gets fixed and I can go back to my Ultra 10.

i-right-i
_________________
Gentoo on x86
Gentoo on SPARC
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Tue Jun 07, 2005 5:01 pm    Post subject: Reply with quote

gust4voz, since we've pretty much zeroed in on the problem to the clock routine of the QT, can you post the diff for those files? Thanks :)
Back to top
View user's profile Send private message
gust4voz
Retired Dev
Retired Dev


Joined: 09 Sep 2003
Posts: 373
Location: Buenos Aires, Argentina

PostPosted: Tue Jun 07, 2005 6:20 pm    Post subject: Reply with quote

There's no patch yet because i haven't zeroed in what's wrong between qt-3.3.2 and qt-3.3.3+
Since it's not where i think it is it's basically trying different solutions many times (and rebuilding qt that many times) which is quite slow for me.
I know qt-3.3.2 works but it's no longer in portage and has security bugs (among other bugs).
_________________
Gustavo Zacarias
Gentoo/SPARC monkey
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Wed Jun 08, 2005 1:56 am    Post subject: Reply with quote

gust4voz, are you sure that qt-3.3.2 works? Some people earlier in the thread said it didn't work for them. Since from the crash trail, the function in question is QTime::addMSec, which is in ./src/tools/qdatetime.cpp. I found no practical differences between 3.3.2 and 3.3.4. But this is in libqt-mt, the multithreaded library, so the errors might be caused by interference between threads. I might miss something. Here's the diff between the two qdatetime.cpp:

Code:
$ diff qt-x11-free-3.3.2/src/tools/qdatetime.cpp qt-x11-free-3.3.4/src/tools/qdatetime.cpp
2c2
< ** $Id: qt/qdatetime.cpp   3.3.2   edited Jan 20 15:04 $
---
> ** $Id: qt/qdatetime.cpp   3.3.4   edited Sep 6 17:17 $
2328c2328
<     return t.secsTo(dt.t) + d.daysTo(dt.d)*SECS_PER_DAY;
---
>     return dt.toTime_t() - toTime_t();


Also, I have questions:
a) How could I "force" kde to temporarily link to my patched qt instead of the actual version. I just want to patch qt in my home dir and have KDE link to it rather than to do a full-blown install.
b) How could I dump something in the console (like debugging message)? Would cout be good enough? Or is there any other way?

And for others, can all of you post your debug traces to see whether it's identical with mine (click here). If all traces end at QTime::addMSecs, then we can be pretty sure that it's not due to multi-thread interference.
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Wed Jun 08, 2005 2:39 am    Post subject: Reply with quote

Posting my updates on cracking down the bug...

I looked up the kdebase-3.4.1/kicker/applets/clock.cpp file. The culprit seems at line 1522-1524:
Code:
QTime ClockApplet::clockGetTime()
{
    return QTime::currentTime().addSecs(TZoffset);
}


It failed at addSecs(TZoffset). TZoffset is an integer field variable.
At qt-3.3.4/src/tools/qdatetime.cpp, line 1522-1524 (serendipitously the same as above):
Code:
QTime QTime::addSecs( int nsecs ) const
{
    return addMSecs( nsecs * 1000 );
}


which calls addMSecs at line 1552-1564:
Code:
QTime QTime::addMSecs( int ms ) const
{
    QTime t;
    if ( ms < 0 ) {
   // % not well-defined for -ve, but / is.
   int negdays = (MSECS_PER_DAY-ms) / MSECS_PER_DAY;
   t.ds = ((int)ds + ms + negdays*MSECS_PER_DAY)
      % MSECS_PER_DAY;
    } else {
   t.ds = ((int)ds + ms) % MSECS_PER_DAY;
    }
    return t;
}


Unfortunately, the debug trace stops here. I need to dissect it a bit further. I think it should be fine, but why it crashed kicker? Hmm... Any help is appreciated.

Edit: For reference, MSECS_PER_DAY= 86400000.
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Sat Jun 11, 2005 6:52 pm    Post subject: Reply with quote

Since Qt 4.0 is to be released by the end of the month, I guess I'll wait to see the differences. I'm inclined to think that this is more of multi-threading problem.
Back to top
View user's profile Send private message
gust4voz
Retired Dev
Retired Dev


Joined: 09 Sep 2003
Posts: 373
Location: Buenos Aires, Argentina

PostPosted: Sun Jun 12, 2005 3:40 pm    Post subject: Reply with quote

Building kde against qt4 requires code changes, kde 3.4 is known not to build against it, kde developers are considering that for 3.5.
Anyway don't hold your breath over that, there's a ton of other stuff qt-related that has to build too in order to go stable (and it's not even released yet).
On a side note, if it were time/date functions just removing the time/alarm applets from kicker should fix it right? (it doesn't) :)
I've already tried moving the QThreads changes from 3.3.2 to 3.3.4 and it doesn't help.
It's known that qt-3.3.3 doesn't work right either, so it's better to diff between those two to see what's wrong instead of doing a bigger diff against 3.3.4, at least to track it down.
I know i sound pessimistic, but i kinda lack time (and cpu time) to test what's wrong, and i'm also a gnome user to get this into a high priority.
_________________
Gustavo Zacarias
Gentoo/SPARC monkey
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Mon Jun 13, 2005 5:09 am    Post subject: Reply with quote

Yet some folks over here claims that QT 3.3.2 doesn't work either. I have both 3.3.2 and 3.3.4 QT sources over my HDD. Perhaps I can take v3.3.3 and diff it. But it's gonna be humongous. No doubt. I don't have much time.
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Fri Jun 24, 2005 6:47 pm    Post subject: Reply with quote

For documentation, another crash log:

Code:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#3  0x712b856c in QTime::addMSecs () from /usr/qt/3/lib/libqt-mt.so.3
#4  0x712b84d0 in QTime::addSecs () from /usr/qt/3/lib/libqt-mt.so.3
#5  0x71effebc in ClockApplet::clockGetTime ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#6  0x71ef4e3c in DigitalClock::updateClock ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#7  0x71ef4b00 in DigitalClock::DigitalClock ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#8  0x71efd640 in ClockApplet::reconfigure ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#9  0x71efc3a8 in ClockApplet::ClockApplet ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#10 0x71ef3500 in init () from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#11 0x700a0348 in PluginManager::loadApplet ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#12 0x7009417c in AppletContainer::AppletContainer ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#13 0x700a1754 in PluginManager::createAppletContainer ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#14 0x70088e18 in ContainerArea::loadContainers ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#15 0x70087c04 in ContainerArea::initialize ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#16 0x700a6a7c in PanelExtension::populateContainerArea ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#17 0x700a60c0 in PanelExtension::qt_invoke ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#18 0x70ff86d8 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#19 0x713505c8 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#20 0x71011dd8 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x7101a820 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#22 0x70f951d0 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#23 0x70f94644 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#24 0x70a48300 in KApplication::notify () from /usr/kde/3.4/lib/libkdecore.so.4
#25 0x70f819c4 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#26 0x70f3804c in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#27 0x70fa9050 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#28 0x7009b5e4 in ExtensionManager::initialize ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#29 0x7009e1f8 in ExtensionManager::qt_invoke ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#30 0x70ff86d8 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#31 0x713505c8 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#32 0x71011dd8 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#33 0x7101a820 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#34 0x70f951d0 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#35 0x70f94644 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#36 0x70a48300 in KApplication::notify () from /usr/kde/3.4/lib/libkdecore.so.4
#37 0x70f819c4 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#38 0x70f3804c in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3
#39 0x70fa8e98 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#40 0x70fa8d6c in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#41 0x70f9549c in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#42 0x70083f80 in kdemain () from /usr/kde/3.4/lib/libkdeinit_kicker.so
#43 0x71af848c in __libc_start_main () from /lib/libc.so.6
#44 0x000107f4 in ?? ()
#45 0x000107f4 in ?? ()


Edit: Another crash log:
Code:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#3  0x7108056c in QTime::addMSecs () from /usr/qt/3/lib/libqt-mt.so.3
#4  0x710804d0 in QTime::addSecs () from /usr/qt/3/lib/libqt-mt.so.3
#5  0x71f33ebc in ClockApplet::clockGetTime ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#6  0x71f28e3c in DigitalClock::updateClock ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#7  0x71f32370 in ClockApplet::slotUpdate ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#8  0x71f33ff0 in ClockApplet::showZone ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#9  0x71f303b8 in ClockApplet::ClockApplet ()
   from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#10 0x71f27500 in init () from /usr/kde/3.4/lib/kde3/clock_panelapplet.so
#11 0x71b2c348 in PluginManager::loadApplet ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#12 0x71b2017c in AppletContainer::AppletContainer ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#13 0x71b2d754 in PluginManager::createAppletContainer ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#14 0x71b14e18 in ContainerArea::loadContainers ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#15 0x71b13c04 in ContainerArea::initialize ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#16 0x71b32a7c in PanelExtension::populateContainerArea ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#17 0x71b320c0 in PanelExtension::qt_invoke ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#18 0x70dc06d8 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#19 0x711185c8 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#20 0x70dd9dd8 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x70de2820 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#22 0x70d5d1d0 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#23 0x70d5c644 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#24 0x70814300 in KApplication::notify ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#25 0x70d499c4 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#26 0x70d0004c in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#27 0x70d71050 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#28 0x71b275e4 in ExtensionManager::initialize ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#29 0x71b2a1f8 in ExtensionManager::qt_invoke ()
   from /usr/kde/3.4/lib/libkdeinit_kicker.so
#30 0x70dc06d8 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#31 0x711185c8 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#32 0x70dd9dd8 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#33 0x70de2820 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#34 0x70d5d1d0 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#35 0x70d5c644 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#36 0x70814300 in KApplication::notify ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#37 0x70d499c4 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#38 0x70d0004c in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#39 0x70d70e98 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#40 0x70d70d6c in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#41 0x70d5d49c in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#42 0x71b0ff80 in kdemain () from /usr/kde/3.4/lib/libkdeinit_kicker.so
#43 0x000150b4 in ?? ()
#44 0x000150b4 in ?? ()
Back to top
View user's profile Send private message
gust4voz
Retired Dev
Retired Dev


Joined: 09 Sep 2003
Posts: 373
Location: Buenos Aires, Argentina

PostPosted: Thu Jul 07, 2005 2:01 pm    Post subject: Reply with quote

Checked in a workaround in the qt ebuilds.
Works for me and a couple of other people with kde 3.4.1 (soon to be stable).
Basically filters down CFLAGS/CXXFLAGS to just "-O1". There's probably some ugly thing going on with g++ building bad code.
Please test.
_________________
Gustavo Zacarias
Gentoo/SPARC monkey
Back to top
View user's profile Send private message
robbyjo
Guru
Guru


Joined: 06 Apr 2003
Posts: 462

PostPosted: Mon Jul 11, 2005 8:02 pm    Post subject: Reply with quote

Confirmed gust4voz solution. It works. I compiled QT with -O1 and recompile KDE 3.4.1.
Back to top
View user's profile Send private message
i-right-i
Tux's lil' helper
Tux's lil' helper


Joined: 08 Nov 2004
Posts: 118
Location: Chandler, AZ USA

PostPosted: Mon Jul 11, 2005 8:07 pm    Post subject: Reply with quote

robbyjo wrote:
Confirmed gust4voz solution. It works. I compiled QT with -O1 and recompile KDE 3.4.1.


So change the CFLAGS = "-02" to "-01" and then recompile QT.

Can we change it back to -02 before the recompile of KDE, or is the -01 option needed for that too?

Thanks,

i-right-i
_________________
Gentoo on x86
Gentoo on SPARC
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on Sparc All times are GMT
Goto page Previous  1, 2, 3, 4  Next
Page 3 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum