| View previous topic :: View next topic |
| Author |
Message |
2dimm
n00b
Joined: 10 Jun 2005
Posts: 52
Location: Brussels, Belgium
|
 Posted: Tue Mar 18, 2008 9:49 am Post subject: |
 |
|
| lazx888 wrote: | anyone else having a problem installing gtk-qt-engine (aka gtk-engines-qt) from svn?
|
see protomans post on 16/03 : http://www.kde-look.org/content/show.php?content=9714&forumpage=25
If using 1.1 halt install as soon as source is unpacked (ctl z) add #include <stdlib.h> to gtk-qt-engine/src/qt_theme_draw.c & restart (fg)
However it now fails later :
Building CXX object kcm_gtk/CMakeFiles/kcm_gtk4.dir/kcm_gtk4_automoc.o
In file included from /var/tmp/portage/x11-themes/gtk-engines-qt-1.1/work/gtk-engines-qt_build/kcm_gtk/moc_kcmgtk.cpp:10,
from /var/tmp/portage/x11-themes/gtk-engines-qt-1.1/work/gtk-engines-qt_build/kcm_gtk/kcm_gtk4_automoc.cpp:2:
/var/tmp/portage/x11-themes/gtk-engines-qt-1.1/work/gtk-engines-qt_build/kcm_gtk/../../gtk-qt-engine/kcm_gtk/kcmgtk.h:27:29: error: ui_kcmgtkwidget.h: No such file or directory
Looking in moc_kcmgtk.cpp I find
#include "../../gtk-qt-engine/kcm_gtk/kcmgtk.h"
#if !defined(Q_MOC_OUTPUT_REVISION)
#error "The header file 'kcmgtk.h' doesn't include <QObject>."
#elif Q_MOC_OUTPUT_REVISION != 59
#error "This file was generated using the moc from 4.4.0-snapshot-20080316. It"
#error "cannot be used with the include files from this version of Qt."
#error "(The moc has changed too much.)"
#endif
I get an identical result with SVN - is anyone else getting it to compile?
If so, with what version of qt-4.4? |
|
| Back to top |
|
 |
Rion
Guru
Joined: 12 Oct 2006
Posts: 359
Location: Ekaterinburg, Russia
|
| Posted: Tue Mar 18, 2008 9:57 am Post subject: |
|
|
qt overlay update
http://filebin.ca/jyhwtm/qt.tar.bz2
New:
* synced with portage (sqlite bug, gcc3 workaround)
* phonon use flag added to qt-qt3support
* ebuilds digested for 20080317
_________________
~amd64
rion-overlay |
|
| Back to top |
|
|
jniklast
n00b
Joined: 12 Mar 2005
Posts: 42
|
| Posted: Tue Mar 18, 2008 10:12 am Post subject: |
|
|
| ok i think i found the solution: you have to emerge qca-ossl which includes all the ssl based plugins for qca-2. Now i just wonder why there is no use flag in the qca base ebuild to trigger automatic installation of qca-ossl... |
|
| Back to top |
|
|
mikkoc
Apprentice
Joined: 24 May 2007
Posts: 229
|
| Posted: Tue Mar 18, 2008 10:36 am Post subject: |
|
|
| Stefano Crocco wrote: | | Since last week, I'm having troubles using yakuake-9999.4: it seems the global shortcut to show/hide it isn't being read on startup: it's correctly displayed in KSystemSettings, but yakuake doesn't recognize it. To make it work, I have to manually change the file .kdesvn/share/config/yakuakerc |
I have the exact same problem.
This is my "workaround" for now: create an autostart file in ~.kdesvn/Autostart/ (make sure it's executable).
| Code: | killall yakuake
cp ~/yakuakerc ~/.kdesvn/share/config/
yakuake |
Where yakuakerc, is a file with the option:
| Code: | [Dialogs]
FirstRun=true |
This way every time it starts it will ask you to set the shortcut.
If you have a better workaround plz let me know  |
|
| Back to top |
|
|
cerebro84
n00b
Joined: 20 Aug 2005
Posts: 64
|
| Posted: Tue Mar 18, 2008 12:19 pm Post subject: |
|
|
I can't compile kdebase since two days.
| Code: | -- Build files have been written to: /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase_build
[ 0%] Generating kuiserversettings.h, kuiserversettings.cpp
[ 0%] Generating ui_uiserverConfigDialog.h
make[2]: *** No rule to make target `/usr/kde/svn/share/dbus-1/interfaces/org.kde.JobView.xml', needed by `runtime/kuiserver/jobviewadaptor.cpp'. Stop.
make[1]: *** [runtime/kuiserver/CMakeFiles/kdeinit_kuiserver.dir/all] Error 2
make: *** [all] Error 2 |
|
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 5314
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 5314
Location: Vienna, Austria; Germany; hello world :)
|
| Posted: Tue Mar 18, 2008 1:05 pm Post subject: |
|
|
| Quote: | moc codecs/qtextcodecplugin.h
compiling ../3rdparty/harfbuzz/src/harfbuzz.c
cc1: warning: ./.pch/release-shared/QtCore.gch/c++: too short to be a PCH file
cc1: warning: ./.pch/release-shared/QtCore.gch/c++: too short to be a PCH file
cc1: error: .pch/release-shared/QtCore: No such file or directory
cc1: error: one or more PCH files were found, but they were invalid
cc1: error: use -Winvalid-pch for more information
make: *** [.obj/release-shared/harfbuzz.o] Error 1
make: *** Waiting for unfinished jobs....
*
* ERROR: x11-libs/qt-core-4.4.0_pre20080317 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2813: Called qt4-build_src_compile
* environment, line 2583: Called build_target_directories
* environment, line 391: Called build_directories 'src_compile'
* environment, line 386: Called die
* The specific snippet of code:
* emake || die "emake failed";
* The die message:
* emake failed
|
(using gcc 4.2.3)
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 |
|
| Back to top |
|
|
Stefano Crocco
Tux's lil' helper
Joined: 28 Sep 2006
Posts: 143
|
| Posted: Tue Mar 18, 2008 1:25 pm Post subject: |
|
|
| mikkoc wrote: | | Stefano Crocco wrote: | | Since last week, I'm having troubles using yakuake-9999.4: it seems the global shortcut to show/hide it isn't being read on startup: it's correctly displayed in KSystemSettings, but yakuake doesn't recognize it. To make it work, I have to manually change the file .kdesvn/share/config/yakuakerc |
I have the exact same problem.
This is my "workaround" for now: create an autostart file in ~.kdesvn/Autostart/ (make sure it's executable).
| Code: | killall yakuake
cp ~/yakuakerc ~/.kdesvn/share/config/
yakuake |
Where yakuakerc, is a file with the option:
| Code: | [Dialogs]
FirstRun=true |
This way every time it starts it will ask you to set the shortcut.
If you have a better workaround plz let me know |
I just finished recompiling yakuake, and now it seems to work.
_________________
Stefano |
|
| Back to top |
|
|
mikedee
Apprentice
Joined: 05 Jul 2006
Posts: 158
|
| Posted: Tue Mar 18, 2008 1:36 pm Post subject: |
|
|
| Is anyone able to get proper backtraces, mine always say that the backtrace is not available. I have the debug use flag set for all the ebuilds, do I need anything else? |
|
| Back to top |
|
|
Stefano Crocco
Tux's lil' helper
Joined: 28 Sep 2006
Posts: 143
|
| Posted: Tue Mar 18, 2008 1:45 pm Post subject: |
|
|
| mikedee wrote: | | Is anyone able to get proper backtraces, mine always say that the backtrace is not available. I have the debug use flag set for all the ebuilds, do I need anything else? |
I think you need to add at least the '-g' flag to CFLAGS and CXXFLAGS and either nosplit or splitdebug to FEATURES (see http://www.gentoo.org/proj/en/qa/backtraces.xml for a more complete explanation).
_________________
Stefano |
|
| Back to top |
|
|
mikkoc
Apprentice
Joined: 24 May 2007
Posts: 229
|
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 4:44 pm Post subject: |
|
|
kernelOFTruth,
PCH files appear to be "pre compiled header" files. Found some info here about invalid pch files..
Here at the bottom, they talk about a pch USE flag helping http://bugs.gentoo.org/show_bug.cgi?id=167428
On the Gentoo Use Variable Descriptions page, they do show a pch flag for several packages, which
"Enables precompiled header support for faster compilation times (gcc >3.4 only)"
Other interesting info:
http://lists.apple.com/archives/Xcode-users/2005/Jul//msg00591.html
http://lists.trolltech.com/qt4-preview-feedback/2004-11/thread00076-0.html
Maybe getting rid of any related cache or source files and trying again would help, or try 20080318?
Please post on how you resolve this- I'll be trying 20080318 later today on Gentoo, after my Arch Linux partition kde svn update completes. Hope I don't run into the same problem.. BTW, on Arch, qt-copy r787067 just compiled OK.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 5314
Location: Vienna, Austria; Germany; hello world :)
|
| Posted: Tue Mar 18, 2008 5:01 pm Post subject: |
|
|
thanks for all the references, wrc1944 
I just saw:
| Quote: | I was also flipping through the gcc mailing list archives relating to
precompiled headers, and found mentions of there being potential problems with
PAX and or PAX like features.
After booting with a non-pax kernel, it would seem the error has been resolved.
Seems that pax when forcing random memory addresses on et_exec and et_dyn's was
causing the invalid relocation errors in the precompiled headers. Makes sense,
and REALLY wish I had thought of that earlier! |
so just go ahead, I don't think you'll run into the same problems (I'm running zen-sources + pax-patch  )
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 5:10 pm Post subject: |
|
|
Hmmm...
I'm running 2.6.24-zen1- Not sure if it included the PAX patch, or not- I'll have to check. Thanks for the tip- I'll have to remember this.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
mikedee
Apprentice
Joined: 05 Jul 2006
Posts: 158
|
| Posted: Tue Mar 18, 2008 6:30 pm Post subject: |
|
|
Here is a patch for kdebase which adds the latest version of wobblywindows to kwin. Put it into the files directory and then add the patch to the ebuild.
http://pastebin.ca/947771 |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 7:22 pm Post subject: |
|
|
I brought up using the -no-exceptions flag with qt here a few days ago (page 24), but nobody has commented so far. I don't know why I didn't notice before, but on my Arch Linux install, I'm using the kdesvn-build script, and in it's config file on qt-copy, it does indeed have that flag set: | Code: | module qt-copy
# Configure flags. If you use Qt 3, then uncomment the lines
# below the Qt 3 option line (by removing the # at the beginning) and
# comment the Qt 4 lines which follow.
configure-flags -qt-gif -no-exceptions -fast -qdbus \
-nomake examples -nomake demos |
I think I'll try it on Gentoo- any comments, pro or con? Having compiled qt-copy on Arch and Gentoo many times now, I can say qt does seem to compile a bit faster (same hardware, different partition). Kde svn does in general also seem a bit snappier on Arch, but that might be due to other factors, such as my Arch testing install being really pretty minimalist.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 5314
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 8:37 pm Post subject: |
|
|
20080318 just failed early in compile: | Code: | NOTICE: Qt will not be built with XShape support.
As a result, drag-and-drop in the Qt Designer will NOT
work. We recommend that you enable XShape support by passing
the -xshape switch to ./configure.
NOTICE: Atomic operations are not yet supported for this
architecture.
Qt will use the 'generic' architecture instead, which uses a
single pthread_mutex_t to protect all atomic operations. This
implementation is the slow (but safe) fallback implementation
for architectures Qt does not yet support.
Qt is now configured for building. Just run 'gmake'.
SNIPPED OUT 200+ LINES
compiling ../3rdparty/harfbuzz/src/harfbuzz.c
compiling arch/generic/qatomic_generic_unix.cpp
compiling concurrent/qfuture.cpp
compiling concurrent/qfutureinterface.cpp
compiling concurrent/qfuturesynchronizer.cpp
compiling concurrent/qfuturewatcher.cpp
compiling concurrent/qrunnable.cpp
compiling concurrent/qtconcurrentfilter.cpp
compiling concurrent/qtconcurrentmap.cpp
compiling concurrent/qtconcurrentresultstore.cpp
compiling concurrent/qtconcurrentthreadengine.cpp
concurrent/qtconcurrentthreadengine.cpp: In member function 'void QtConcurrent::ThreadEngineBase::startBlocking()':
concurrent/qtconcurrentthreadengine.cpp:86: error: 'e' was not declared in this scope
concurrent/qtconcurrentthreadengine.cpp: In member function 'virtual void QtConcurrent::ThreadEngineBase::run()':
concurrent/qtconcurrentthreadengine.cpp:191: error: 'e' was not declared in this scope
make: *** [.obj/release-shared/qtconcurrentthreadengine.o] Error 1
make: *** Waiting for unfinished jobs....
*
* ERROR: x11-libs/qt-core-4.4.0_pre20080318 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2751: Called qt4-build_src_compile
* environment, line 2530: Called build_target_directories
* environment, line 375: Called build_directories 'src_compile'
* environment, line 370: Called die
* The specific snippet of code:
* emake || die "emake failed";
* The die message:
* emake failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/x11-libs/qt-core-4.4.0_pre20080318/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/qt-core-4.4.0_pre20080318/temp/environment'.
|
EDIT: Remove -fno-exceptions from CXXFLAGS, and qt-core compiled.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups
Last edited by wrc1944 on Tue Mar 18, 2008 8:54 pm; edited 1 time in total |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 8:52 pm Post subject: |
|
|
Rion,
If I wanted to add -no-exceptions, how would I go about it.
Put -no-exceptions in the myconf line in all the ebuilds, and redigest?
Or is there a global method? I tried -no-exceptions in CXXFLAGS= in make.conf, but it then said "unrecognized option." I then tried -fno-exceptions, and it showed up in the gcc output, but I still got the same message I got a few days ago, saying: | Code: | This target is using the GNU C++ compiler (linux-g++).
Recent versions of this compiler automatically include code for
exceptions, which increase both the size of the Qt libraries and
the amount of memory taken by your applications.
You may choose to re-run configure with the -no-exceptions
option to compile Qt without exceptions. This is completely binary
compatible, and existing applications will continue to work. |
So apparently, -fno-exceptions doesn't work, and it needs -no-exceptions in the ebuild- at least that's my understanding. Any advice?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
Berniyh
l33t
Joined: 07 Jun 2006
Posts: 677
|
| Posted: Tue Mar 18, 2008 9:13 pm Post subject: |
|
|
*cough*
May I remind you, that this thread is not about prereleases of Qt.
If you want to use those (they are totally unsupported by the KDE team, keep that in mind!), please
open up a new thread.
Keep the talk in this thread about KDE4.1.
Thx. |
|
| Back to top |
|
|
enzobelmont
Guru
Joined: 06 Apr 2004
Posts: 345
Location: Chiapas, Mexico
|
| Posted: Tue Mar 18, 2008 9:33 pm Post subject: |
|
|
| Berniyh wrote: | *cough*
May I remind you, that this thread is not about prereleases of Qt.
If you want to use those (they are totally unsupported by the KDE team, keep that in mind!), please
open up a new thread.
Keep the talk in this thread about KDE4.1.
Thx. |
let me remind you that KDE is completely bonded to QT, any minor change impacts on kde, we here are trying address as many bugs as possible, to make a more robust kde release.
let me put this in a simple way:
talk about kde with no qt reference.
is like to make a sandwich with no ham
sorry my english...
_________________
Mens sana in corpore sano... Gentoo laetificat cor hominis |
|
| Back to top |
|
|
Berniyh
l33t
Joined: 07 Jun 2006
Posts: 677
|
| Posted: Tue Mar 18, 2008 10:32 pm Post subject: |
|
|
| enzobelmont wrote: | | Berniyh wrote: | *cough*
May I remind you, that this thread is not about prereleases of Qt.
If you want to use those (they are totally unsupported by the KDE team, keep that in mind!), please
open up a new thread.
Keep the talk in this thread about KDE4.1.
Thx. |
let me remind you that KDE is completely bonded to QT, any minor change impacts on kde, we here are trying address as many bugs as possible, to make a more robust kde release.
let me put this in a simple way:
talk about kde with no qt reference.
is like to make a sandwich with no ham
sorry my english... |
Yes, and no.
This thread is about the KDE overlay.
There are qt ebuilds supported by this overlay and those are in portage.
You're talking about totally unsupported qt ebuilds here, which have no relation to the overlay (since you can use the overlay with the portage ebuilds).
Of course, if you feel like that use snapshot Qt ebuilds (or Qt-Copy) and talk about them, but create a separate thread for that.
If there are newer snapshots needed to use the overlay report a bug to the overlay's bugzilla.
So please keep snapshots of Qt, that are not in portage, out of this thread. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Tue Mar 18, 2008 10:32 pm Post subject: |
|
|
Berniyh,
Sorry if I'm posting in the wrong place- I was referring to a message in the gcc output produced by the qt overlay being used here, kindly posted and maintained by Rion on this thread. This message (I assume to be from trolltech- correct me if that's wrong) seems completely relevant to building kde svn, or kde-4.4.0-x.
If this thread is supposed to be only qt and kde-4.4.x release related, I can see your point, however most of it seems kde svn related, which surely involves the pre releases of qt. There's really no other thread where us svn users can post.
That was one reason I suggested a separate kde svn thread sometime back, to clarify things a bit. I would have started one myself, but I'm not a qt4/kde4 dev- just a user/kde fan who likes to keep up and learn about all the latest stuff. I re-submit this suggestion, in hopes it will be started by one of the kde4 team devs who really know what they are talking about, instead of an average joe user like myself.
So- just to clarify: Are all of us posting here about qt pre and/or kde svn no longer supposed to do so?
enzobelmont,
Thanks for backing be up- since building kde requires qt, I must agree that any discussion about building kde assumes qt is already functional.
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
Berniyh
l33t
Joined: 07 Jun 2006
Posts: 677
|
| Posted: Wed Mar 19, 2008 1:35 am Post subject: |
|
|
| wrc1944 wrote: | Berniyh,
Sorry if I'm posting in the wrong place- I was referring to a message in the gcc output produced by the qt overlay being used here, kindly posted and maintained by Rion on this thread. This message (I assume to be from trolltech- correct me if that's wrong) seems completely relevant to building kde svn, or kde-4.4.0-x.
If this thread is supposed to be only qt and kde-4.4.x release related, I can see your point, however most of it seems kde svn related, which surely involves the pre releases of qt. There's really no other thread where us svn users can post.
That was one reason I suggested a separate kde svn thread sometime back, to clarify things a bit. I would have started one myself, but I'm not a qt4/kde4 dev- just a user/kde fan who likes to keep up and learn about all the latest stuff. I re-submit this suggestion, in hopes it will be started by one of the kde4 team devs who really know what they are talking about, instead of an average joe user like myself.
So- just to clarify: Are all of us posting here about qt pre and/or kde svn no longer supposed to do so?
enzobelmont,
Thanks for backing be up- since building kde requires qt, I must agree that any discussion about building kde assumes qt is already functional. |
No, you got that wrong.
KDE svn discussion belongs to this thread. The discussion about KDE-4.0.x ebuilds, that are in portage, is somewhere else (they've got their own thread).
Of course you can discuss about KDE-related issues with Qt. All I'm saying is, that you should keep the discussion about Qt snapshots out of this thread.
For those just create your own thread (just like it has been done for Qt-Copy).
Note, that there is (afaik) no need to use a newer version of Qt-4.4 than the one, that is in portage (_beta1).
If there would be a need for that, it will be bumped by the KDE/Qt team. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 2612
Location: Gainesville, Florida
|
| Posted: Wed Mar 19, 2008 2:07 am Post subject: |
|
|
Berniyh,
Thanks for the clarification. Sounds reasonable to me. Guess those of us using qt snapshots should start a new thread dedicated only to that subject. It would make it easier to keep track of things.
EDIT: I started a new qt-4.4.0 snapshot thread at http://forums.gentoo.org/viewtopic-p-4975949.html#4975949
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.14-r2, gcc-4.6.2, kernels 3.1.9, 3.2.1 w/auto-cgroups |
|
| Back to top |
|
|
|
|
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
|
|
Unsupported Software
)