Well they almost have all P1 regressions then need to drop the 161 count down below 100 before they officially release it. I can't wait for the bad boy ;), I know it's too early to even consider it. But I wonder what will be in 4.5.0. I'll probably switch to GCC-4.4.0 when it gets in RC stage for me ...

well then I guess your choice is wxWidgets or Gtkmm

you don't need to purchase a license unless you want to sell it. =\

Gtkmm is a little pain to set up on Windows if you want it really to be updated. But its a great library but just lacks networking. Which is a paint to find a good library.
Qt is the best imho. I use it but I'm giving unbiased. The signal and slots are great and fairly easy to use. wxWidgets is and ...

I'm having trouble with compiz-fusion. When I use it. And if I try to change the theme with emerald, it doesn't change at all

did you forget to switch from nv to nvidia?

I have something like this in my code

#ifdef Q_CC_MSVC
#ifdef BUILD_DLL
#define DECL_EXPORT __declspec(dllexport)
#else
#define DECL_EXPORT __declspec(dllimport)
#endif
#elif Q_CC_UNIX
#define DECL_EXPORT
#endif

I'm having so much of a difficult time to use KDevelop3 to develop KDE4 programs. The KDE4 headers are in /usr/include and there are so many that it cause code-complete to buckle and break. Is there a way to work around this and have auto-complete for KDE4?

Okay I fixed it I think. Haven't gotten no errors so far.

I had to recompile qt-core with debug useflags. But then soprano complained about qt-core using the debug which i have no idea why? Maybe wrong writing in ebuild? But I fixed it by installing raptor by itself, then compiled soprano with ...

I get this error.

/usr/lib64/qt4/libQtGui.so: undefined reference to 'QCoreApplicationPrivate::checkReceiverThread(QObject*);

I've tried recompiling it multiply times and it keeps failing on any package it uses. But it compiles successfully.

wim-x wrote:I don't know if portage can do that, I don't think so.

I would first compile virtualbox with gcc-4.2.4 using gcc-config, and then switch back to gcc-4.3.1 and emerge world.

But then it would fail if I did a emerge -e world

Is there a way to keep --nodeps from removing a gcc version from there when I have multiple versions? Even if I accently forget to set the option?

I have virtualbox and it won't work with gcc-4.3.1 and was wondering how can I make portage when I do a -e world it would compile it with 4.2.4 and not ...

I wouldn't advise people to use glibc-2.8. It's too buggy right now.

Michal. wrote:Hello,

I get:

Code: Select all

Checking for working mktime... no

during emerging bash with GCC-4.3.1

GCC-4.2.3: http://pastebin.com/m62061722 GCC-4.3.1: http://pastebin.com/d2f25c523

Did you emerge -C mktemp? If you did, emerge coreutils. Then try again.

unK wrote:

Eckos wrote:I wonder now will gcc-4.3.1 come close to being marked stable in a month or two?

it hit ~arch already.

I know. marked STABLE not marked arch.

Can you bump the compiler up to 4.3.1 since it's in portage now?

I wonder now will gcc-4.3.1 come close to being marked stable in a month or two?

Edit: Now we need a 4.4.0 testing thread

i use -march=native -msse3 and I have a AMD Athlon 64 X2 3800+.

sweet!!!!!!!!!!!!!!!!!

I am using Qt4 with OpenGL. And I was wonderinf if anyone has/know any tutorials on calculating the frames per second or have source code of it. Because I can't find anything on it.

huh?

I hope they fix the ugly menu because theres like no borders at all and its unattractive. And Fix the bug about how the clock and the notification area just flickers and sometimes just go black and disappear.

Which revision did you tried? 4.0.80? Which graphic card? Did you already filled a ...

I hope they fix the ugly menu because theres like no borders at all and its unattractive. And Fix the bug about how the clock and the notification area just flickers and sometimes just go black and disappear.

you can do

I don't have "=" in mine. So that won't be the problem but glad it works for you =)