Sie sind nicht angemeldet.

[gelöst] vmware-player unter 2.6.30 installieren

Lieber Besucher, herzlich willkommen bei: GentooForum.de. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

1

02.09.2009, 17:56

vmware-player unter 2.6.30 installieren

Hallo zusammen,

meine vmware-player installation mit emerge bricht immer ab. Hat jemand eine Idee, wie man das behebt? Hier die Ausgabe von emerge:

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

 make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4'
make: *** [vmmon.ko] Error 2
* 
 * ERROR: app-emulation/vmware-modules-1.0.0.23 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_compile
 *         	environment, line 3760:  Called linux-mod_src_compile
 *         	environment, line 2874:  Called die
 * The specific snippet of code:
 *           	eval "emake HOSTCC="$(tc-getBUILD_CC)"                                           	CROSS_COMPILE=${CHOST}-                                             	LDFLAGS="$(get_abi_LDFLAGS)"                                      	${BUILD_FIXES}            	$
{BUILD_PARAMS}                                      	${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build
 * 
 * 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/app-emulation/vmware-modules-1.0.0.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/environment'.
 * 

>>> Failed to emerge app-emulation/vmware-modules-1.0.0.23, Log file:

>>>  '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/build.log'

 * Messages for package app-emulation/vmware-modules-1.0.0.23:

 * 
 * ERROR: app-emulation/vmware-modules-1.0.0.23 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_compile
 *         	environment, line 3760:  Called linux-mod_src_compile
 *         	environment, line 2874:  Called die
 * The specific snippet of code:
 *           	eval "emake HOSTCC="$(tc-getBUILD_CC)"                                           	CROSS_COMPILE=${CHOST}-                                             	LDFLAGS="$(get_abi_LDFLAGS)"                                      	${BUILD_FIXES}            	$
{BUILD_PARAMS}                                      	${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build
 * 
 * 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/app-emulation/vmware-modules-1.0.0.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/environment'.
Gruß, TRIAGE

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »TRIAGE« (05.09.2009, 10:00)

dyle

Erleuchteter

  • »dyle« ist männlich

Beiträge: 4 869

  • Nachricht senden

2

02.09.2009, 18:07

Poste uns doch, was die Fehlermeldung ist. Was du da durchgegeben hast, ist die Meldung, dass es einen Fehler gab.

Der eiegntliche Fehler passiert knapp darüber.

Alternativ: stelle die in dieser Meldung erstellte build.log hier als Attachment rein.
http://www.dyle.org
IM-Account (Jabber!) sind auf meiner HP ...
There is no place like /home

http://www.gentooforum.de
http://www.gentoofreunde.org

<div>how to annoy a web developer?</span>

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

3

04.09.2009, 15:10

Okay, hier kommt die gesamte Ausgabe der Konsole inkl. Fehlermeldung. Hoffe ihr könnt etwas damit anfangen.

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133

triage@gentoo ~ $ su
Password: 
gentoo triage # emerge -av vmware-player

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N	] app-emulation/vmware-modules-1.0.0.23  0 kB
[ebuild  N	] app-text/iso-codes-3.8  0 kB
[ebuild  N	] gnome-base/gail-1000  0 kB
[ebuild  N	] dev-python/cython-0.11.2  USE="-doc -examples" 0 kB
[ebuild  N	] dev-python/lxml-2.2.1  USE="threads -doc -examples" 0 kB
[ebuild  N	] x11-libs/libsexy-0.1.11  USE="-debug -doc" 0 kB
[ebuild  N	] gnome-base/libgnomecanvas-2.20.1.1  USE="X -debug -doc" 0 kB
[ebuild  N	] dev-cpp/libgnomecanvasmm-2.22.0  USE="-debug -doc -examples" 0 kB
[ebuild  N	] dev-cpp/libsexymm-0.1.9  USE="-debug -doc" 0 kB
[ebuild  N	] app-emulation/vmware-player-2.5.2.156735  0 kB

Total: 10 packages (10 new), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] y

>>> Verifying ebuild manifests

>>> Starting parallel fetch

>>> Emerging (1 of 10) app-emulation/vmware-modules-1.0.0.23
 * vmware-modules-1.0.0.23.amd64.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                                                                                                                    	[ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                                                                                                                        	[ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                                                                                                                       	[ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                                                                                                                      	[ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 * 	/usr/src/linux
 * Found kernel object directory:
 * 	/lib/modules/2.6.30-gentoo-r4/build
 * Found sources for kernel version:
 * 	2.6.30-gentoo-r4
>>> Unpacking source...
>>> Unpacking vmware-modules-1.0.0.23.amd64.tar.bz2 to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
>>> Unpacking ./vmware-modules-1.0.0.23/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
 * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ...                                                                                                                                                                                                          	[ ok ]
>>> Unpacking ./vmware-modules-1.0.0.23/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
 * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ...                                                                                                                                                                                                          	[ ok ]
>>> Unpacking ./vmware-modules-1.0.0.23/vmblock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
 * Converting vmblock-only/Makefile to use M= instead of SUBDIRS= ...                                                                                                                                                                                                        	[ ok ]
>>> Unpacking ./vmware-modules-1.0.0.23/vmci.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
 * Converting vmci-only/Makefile to use M= instead of SUBDIRS= ...                                                                                                                                                                                                           	[ ok ]
>>> Unpacking ./vmware-modules-1.0.0.23/vsock.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
 * Converting vsock-only/Makefile to use M= instead of SUBDIRS= ...                                                                                                                                                                                                          	[ ok ]
 * Applying 1.0.0.23-makefile-kernel-dir.patch ...                                                                                                                                                                                                                           	[ ok ]
>>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work
>>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work ...
 * Preparing vmmon module
make -j2 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build 
Using 2.6.x kernel build system.
make -C /lib/modules/2.6.30-gentoo-r4/build M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo-r4'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.o
In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/./common/vmx86.h:31,
             	from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.h:29,
             	from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:101:
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined
In file included from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/apic.h:11,
             	from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/smp.h:13,
             	from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/mmzone_64.h:12,
             	from /usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/mmzone.h:4,
             	from include/linux/mmzone.h:775,
             	from include/linux/gfp.h:4,
             	from include/linux/kmod.h:22,
             	from include/linux/module.h:13,
             	from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/./include/compat_module.h:27,
             	from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:26:
/usr/src/linux-2.6.30-gentoo-r4/arch/x86/include/asm/apicdef.h:133:1: warning: this is the location of the previous definition
In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:32:
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait'
include/linux/poll.h:67: error: previous declaration of 'poll_initwait' was here
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU':
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1423: error: too many arguments to function 'smp_call_function'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid'
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.c:2007: error: too many arguments to function 'smp_call_function'
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only/linux/driver.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/work/vmmon-only] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4'
make: *** [vmmon.ko] Error 2
 * 
 * ERROR: app-emulation/vmware-modules-1.0.0.23 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_compile
 *         	environment, line 3783:  Called linux-mod_src_compile
 *         	environment, line 2897:  Called die
 * The specific snippet of code:
 *           	eval "emake HOSTCC="$(tc-getBUILD_CC)"                                           	CROSS_COMPILE=${CHOST}-                                             	LDFLAGS="$(get_abi_LDFLAGS)"                                      	${BUILD_FIXES}            	${BUILD_PARAMS}                                      	${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build
 * 
 * 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/app-emulation/vmware-modules-1.0.0.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/environment'.
 * 

>>> Failed to emerge app-emulation/vmware-modules-1.0.0.23, Log file:

>>>  '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/build.log'

 * Messages for package app-emulation/vmware-modules-1.0.0.23:

 * 
 * ERROR: app-emulation/vmware-modules-1.0.0.23 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_compile
 *         	environment, line 3783:  Called linux-mod_src_compile
 *         	environment, line 2897:  Called die
 * The specific snippet of code:
 *           	eval "emake HOSTCC="$(tc-getBUILD_CC)"                                           	CROSS_COMPILE=${CHOST}-                                             	LDFLAGS="$(get_abi_LDFLAGS)"                                      	${BUILD_FIXES}            	${BUILD_PARAMS}                                      	${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_V65 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r4/build
 * 
 * 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/app-emulation/vmware-modules-1.0.0.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.23/temp/environment'.
 * 
gentoo triage #
Gruß, TRIAGE

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

4

04.09.2009, 15:41

Hi
das Problem ist das Version
vmware-player-2.5.2.156735
die Version vmware-modules-1.0.0.23
benötigt
vmware-modules-1.0.0.23 gehen aber nur bis kernel-2.6.28 oder evtl 29

Du solltest also eine aktuellere vmware-player Version verwenden
mach doch bitte mal ein "emerge --sync" evtl. gibt es da schon eine aktuellere Version.
Unter 32bit (i686) ist zZt schon Version vmware-player-2.5.3.185404 stable

Für dein 30er Kernel wird nur >=vmware-modules-1.0.0.24 funktionieren.

/edit: siehe zb auch http://bugs.gentoo.org/show_bug.cgi?id=263635

Viel Erfolg

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »josef.95« (04.09.2009, 15:46)

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

5

04.09.2009, 15:56

Ein "emerge --sync" brachte leider keine aktuellere Version von vmware-modules-1.0.0.23 zum Vorschein.

Gibt es eine andere Möglichkeit an eine aktuellere version der vmware-modules zu kommen? Möchte meinen Kernel eigentlich in der 30er Version weiterlaufen lassen.
Gruß, TRIAGE

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

6

04.09.2009, 16:15

Poste bitte mal die Ausgabe von

Quellcode

 
1

eix vmware-player

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

7

04.09.2009, 16:48

Die Ausgabe sieht so aus:

Quellcode

 
1
2
3
4

* app-emulation/vmware-player
 	Available versions:  1.0.9.126128!s 2.5.1.126130!s 2.5.2.156735!b!s ~2.5.2.156735-r1!b!s ~2.5.3.185404!b!s
 	Homepage:        	http://www.vmware.com/products/desktop/ws_features.html
 	Description:     	Emulate a complete PC on your PC without the usual performance overhead of most emulators
Gruß, TRIAGE

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

8

04.09.2009, 17:00

Hm.., du könntest die Version
app-emulation/vmware-player-2.5.2.156735-r1
demaskieren, also etwa

Quellcode

 
1

# echo "=app-emulation/vmware-player-2.5.2.156735-r1" >> /etc/portage/package.keywords
Diese Version sollte dann vmware-modules-1.0.0.24 als Abhängigkeit mitziehen.
Eventuell wirst du noch weitere Abhängigkeiten demaskieren müssen.

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

9

04.09.2009, 18:20

Okay, wir kommen der Sache schon näher.

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11

gentoo triage # emerge -av vmware-player

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds built with USE flags to satisfy ">=dev-lang/python-2.5[sqlite,ncurses]".
!!! One of the following packages is required to complete your request:
- dev-lang/python-2.6.2-r1 (Change USE: +sqlite)
(dependency required by "app-emulation/vmware-player-2.5.2.156735-r1" [ebuild])
(dependency required by "vmware-player" [argument])


Wenn ich jetzt
dev-lang/python
in /etc/portage/package.keywords und dann zusätzlich
dev-lang/python sqlite
in /etc/portage/package.use eintrage, kommt nach einer Installation verschiedener Packete diese Meldung

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

>>> Emerging (1 of 1) app-emulation/vmware-player-2.5.2.156735-r1
 * VMware-Player-2.5.2-156735.x86_64.bundle RMD160 SHA1 SHA256 size ;-) ...                                                                                           	[ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                  	[ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                 	[ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                	[ ok ]
>>> Unpacking source...
Unbundling /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/distdir/VMware-Player-2.5.2-156735.x86_64.bundle
>>> Source unpacked in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work
>>> Preparing source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
 * Applying vmware-player-2.5.2.156735-installer.patch ...                                                                                                             	[ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-emulation/vmware-player-2.5.2.156735-r1

>>> Install vmware-player-2.5.2.156735-r1 into /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/image/ category app-emulation
Traceback (most recent call last):
  File "/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/payload/install/vmware-installer/vmware-installer.py", line 16, in <module>
	from vmis.db import DatabaseError, MultipleInstallersError, Load
  File "/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/payload/install/vmware-installer/vmis/db.py", line 11, in <module>
	import sqlite3 as sqlite
  File "/usr/lib64/python2.6/sqlite3/__init__.py", line 24, in <module>
	from dbapi2 import *
  File "/usr/lib64/python2.6/sqlite3/dbapi2.py", line 27, in <module>
	from _sqlite3 import *
ImportError: No module named _sqlite3
 * VMware installation seems to have rolled back.
 * Please include the contents of /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/vmware-installer.log
 * in any bug reports you file.
 * 
 * ERROR: app-emulation/vmware-player-2.5.2.156735-r1 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_install
 *         	environment, line 2753:  Called die
 * The specific snippet of code:
 *       	die "VMware installation rolled back.";
 *  The die message:
 *   VMware installation rolled back.
 * 
 * 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/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/environment'.
 * 

>>> Failed to emerge app-emulation/vmware-player-2.5.2.156735-r1, Log file:

>>>  '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'

 * Messages for package app-emulation/vmware-player-2.5.2.156735-r1:

 * VMware installation seems to have rolled back.
 * Please include the contents of /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/vmware-installer.log
 * in any bug reports you file.
 * 
 * ERROR: app-emulation/vmware-player-2.5.2.156735-r1 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_install
 *         	environment, line 2753:  Called die
 * The specific snippet of code:
 *       	die "VMware installation rolled back.";
 *  The die message:
 *   VMware installation rolled back.
 * 
 * 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/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/environment'.
 *
Gruß, TRIAGE

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »TRIAGE« (04.09.2009, 18:48)

schade

Profi

Beiträge: 1 228

  • Nachricht senden

10

04.09.2009, 18:39

das liegt daran dass man in der /etc/portage/package.use keine versions angaben macht:


der eintrag müsste so aussehen :

Quellcode

 
1

dev-lang/python sqlite



die 2 falsch einträge in package.keywords und package.use würde ich auch rausnehmen.
Intel core 2 duo E6600
XFX Geforce 7950 gt
4096 MB DDR2
Intel DP35DP

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

11

04.09.2009, 19:24

Okay, dass habe ich angepasst. Kann jemand was mit der Fehlermeldung aus meinem letzten Post anfangen?
Gruß, TRIAGE

schade

Profi

Beiträge: 1 228

  • Nachricht senden

12

04.09.2009, 19:44

ich nehm mal an du hast nach dem du den eintrag gemacht hast, dev-lang/python noch nicht neuemerged oder?
Intel core 2 duo E6600
XFX Geforce 7950 gt
4096 MB DDR2
Intel DP35DP

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

13

04.09.2009, 20:12

Doch hab ich. Hab quasi erst den Eintrag geändert und dann neuemerged. Hab wohl während Du Deinen Eintrag geändert hast, meinen alten editiert.

Dies ist letztendlich die Fehlermeldung bei der ich nicht weiterkomme:

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

[ebuild  N	] app-emulation/vmware-player-2.5.2.156735-r1  0 kB

Total: 1 package (1 new), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] y

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-emulation/vmware-player-2.5.2.156735-r1
 * VMware-Player-2.5.2-156735.x86_64.bundle RMD160 SHA1 SHA256 size ;-) ...                                                                                                                                                                                                	[ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                                                                                                                       	[ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                                                                                                                      	[ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                                                                                                                     	[ ok ]
>>> Unpacking source...
Unbundling /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/distdir/VMware-Player-2.5.2-156735.x86_64.bundle
>>> Source unpacked in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work
>>> Preparing source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
 * Applying vmware-player-2.5.2.156735-installer.patch ...                                                                                                                                                                                                                  	[ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-emulation/vmware-player-2.5.2.156735-r1

>>> Install vmware-player-2.5.2.156735-r1 into /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/image/ category app-emulation
Traceback (most recent call last):
  File "/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/payload/install/vmware-installer/vmware-installer.py", line 16, in <module>
	from vmis.db import DatabaseError, MultipleInstallersError, Load
  File "/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/payload/install/vmware-installer/vmis/db.py", line 11, in <module>
	import sqlite3 as sqlite
  File "/usr/lib64/python2.6/sqlite3/__init__.py", line 24, in <module>
	from dbapi2 import *
  File "/usr/lib64/python2.6/sqlite3/dbapi2.py", line 27, in <module>
	from _sqlite3 import *
ImportError: No module named _sqlite3
 * VMware installation seems to have rolled back.
 * Please include the contents of /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/vmware-installer.log
 * in any bug reports you file.
 * 
 * ERROR: app-emulation/vmware-player-2.5.2.156735-r1 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_install
 *         	environment, line 2753:  Called die
 * The specific snippet of code:
 *       	die "VMware installation rolled back.";
 *  The die message:
 *   VMware installation rolled back.
 * 
 * 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/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/environment'.
 * 

>>> Failed to emerge app-emulation/vmware-player-2.5.2.156735-r1, Log file:

>>>  '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'

 * Messages for package app-emulation/vmware-player-2.5.2.156735-r1:

 * VMware installation seems to have rolled back.
 * Please include the contents of /var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/work/vmware-installer.log
 * in any bug reports you file.
 * 
 * ERROR: app-emulation/vmware-player-2.5.2.156735-r1 failed.
 * Call stack:
 *           	ebuild.sh, line   49:  Called src_install
 *         	environment, line 2753:  Called die
 * The specific snippet of code:
 *       	die "VMware installation rolled back.";
 *  The die message:
 *   VMware installation rolled back.
 * 
 * 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/app-emulation/vmware-player-2.5.2.156735-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-player-2.5.2.156735-r1/temp/environment'.
 * 
gentoo bin #
Gruß, TRIAGE

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

14

04.09.2009, 20:26

Der aktuelle Fehler ist hier anscheinend

Quellcode

 
1
2
3

  File "/usr/lib64/python2.6/sqlite3/dbapi2.py", line 27, in <module>
	from _sqlite3 import *
ImportError: No module named _sqlite3

Zeig doch bitte mal die Ausgabe von

Quellcode

 
1

eselect python list

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

15

04.09.2009, 20:40

Das ist die Ausgabe von
# eselect python list

Quellcode

 
1
2
3
4
5

Available python interpreters:
  [1]   python2.4
  [2]   python2.5
  [3]   python2.6 *
  [4]   python3.1
Gruß, TRIAGE

josef.95

OSI Layer 8

Beiträge: 7 674

  • Nachricht senden

16

04.09.2009, 21:09

Oje, du hast da python3.1 installiert, ist das Absicht?
wenn nein,
dann nimm den Eintrag "dev-lang/python" aus der /etc/portage/package.keywords raus, und deinstalliere dann mit

Quellcode

 
1

# emerge -avC python:3.1

Hattest du wie python:2.6 installiert wurde, schon mal "python-updater" durchlaufen lassen? , vermutlich sind noch nicht alle Pakete gegen python:2.6 gebaut worden.
Lasse doch bitte mal

Quellcode

 
1

# python-updater
durchlaufen, da werden dann vermutlich einige Pakete neugebaut, wenn die durch sind probiere es noch mal mit vmware-player

TRIAGE

Anfänger

  • »TRIAGE« ist männlich
  • »TRIAGE« ist der Autor dieses Themas

Beiträge: 36

  • Nachricht senden

17

05.09.2009, 02:56

Dass war es! Jetzt läuft der vmware-player. Vielen Dank :-)
Gruß, TRIAGE

Häufig verwendete Suchbegriffe:

www.my-echo.de mobile-parts-discount.net Andere Architekturen Lob & Kritik Gentoo Linux bka trojaner finden Emerge Probleme softwaregarage.de Drucker Linux Computer und Notebooks