1 |
> |
2 |
> The only reason is because I don't think it is a good idea to run an |
3 |
> emerge inside and emerge. And it takes more than a few minutes for me |
4 |
> to re-compile all my modules/libraries/programs. |
5 |
> |
6 |
|
7 |
something strange about python updater : When I run it on my girl's |
8 |
friend gentoo box (yes, she gave up windows :p), it shuts down the PC ! |
9 |
|
10 |
I have on my xterm : |
11 |
|
12 |
* Starting Python Updater from 2.2 to 2.3 : |
13 |
* Searching for packages with files in /usr/lib/python2.2 .. |
14 |
Adding to list: dev-python/wxPython-2.4.1.2 |
15 |
Adding to list: dev-python/pykde-3.7.4-r2 |
16 |
* Calculating Upgrade Package List .. |
17 |
* Re-ordering packages to merge .. |
18 |
* Preparing to merge these packages in this order: |
19 |
dev-python/pykde-3.7.4-r2 |
20 |
dev-python/wxPython-2.4.1.2 |
21 |
* Starting to merge (1/2) dev-python/pykde-3.7.4-r2 .. |
22 |
Calculating dependencies ...done! |
23 |
>>> emerge (1 of 1) dev-python/pykde-3.7.4-r2 to / |
24 |
>>> md5 src_uri ;-) PyKDE-3.7-4.tar.gz |
25 |
>>> Unpacking source... |
26 |
>>> Unpacking PyKDE-3.7-4.tar.gz to /var/tmp/portage/pykde-3.7.4-r2/work |
27 |
PyQt 3.8 detected. |
28 |
Running sed on /var/tmp/portage/pykde-3.7.4-r2/work/PyKDE-3.7-4/build.py |
29 |
>>> Source unpacked. |
30 |
Building PyKDE 3.8 for Python 2.3.3 on linux2. |
31 |
/var/tmp/portage/pykde-3.7.4-r2/image//usr/lib/python2.3/site-packages |
32 |
is the |
33 |
PyKDE installation directory. |
34 |
/usr/include/python2.3 contains Python.h. |
35 |
/usr/bin/sip will be used as the SIP code generator. |
36 |
/usr/include/python2.3 contains sipQt.h. |
37 |
/usr/lib/python2.3/site-packages contains the SIP module. |
38 |
/usr/qt/3 is the Qt base directory. |
39 |
/usr/qt/3/include contains qglobal.h. |
40 |
Qt 3.2.3 is being used. |
41 |
/usr/kde/3.1 is the KDE base directory. |
42 |
/usr/kde/3.1/include contains kdeversion.h. |
43 |
KDE 3.1.3 is being used. |
44 |
/usr/qt/3/bin/qmake will be used to generate Makefiles. |
45 |
The libqt-mt.so.3.2.3 Qt library was found. |
46 |
Qt thread support is enabled. |
47 |
Qt and KDE use compatible libs (threading) |
48 |
|
49 |
found libs for modules: |
50 |
dcop kdecore kdesu kdefx kdeui kio kfile (kio) kparts khtml kjs |
51 |
kspell kdeprint |
52 |
PyQt/sip directory found at /usr/share/sip/qt |
53 |
PyQt sip file version is compatible with PyKDE (3.8) |
54 |
sip version is compatible with PyKDE-3.8 |
55 |
/usr/bin/make will be used as the make program. |
56 |
Checking to see if the C++ compiler supports -fno-exceptions. |
57 |
g++ -c -pipe -w -O2 -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT |
58 |
-fno-exceptions -I/usr/qt/3/mkspecs/linux-g++ -I. -I. |
59 |
-I/usr/include/python2.3 -I/usr/kde/3.1/include -I/usr/qt/3/include -o |
60 |
qttest.o qttest.cpp |
61 |
g++ -Wl,-rpath,/usr/qt/3/lib -o qttest qttest.o -L/usr/qt/3/lib |
62 |
-L/usr/X11R6/lib -lqt-mt -lXext -lX11 -lm -lpthread |
63 |
The C++ compiler supports -fno-exceptions. |
64 |
Using existing features file. |
65 |
Generating the C++ source for the dcop module. |
66 |
Generating the Makefile for the dcop module. |
67 |
Concatenating the C++ files for the dcop module. |
68 |
Compiling dcop.py. |
69 |
Generating the C++ source for the kdecore module. |
70 |
Generating the Makefile for the kdecore module. |
71 |
Concatenating the C++ files for the kdecore module. |
72 |
|
73 |
|
74 |
AND THEN ......... shut down (4 times, and exactly same result) ! |
75 |
|
76 |
I've alsa posted this to forums. |
77 |
|
78 |
-- |
79 |
gentoo-dev@g.o mailing list |