Sabayon Community

by **BigPapaJ** » Sat Feb 10, 2007 12:15

Einen wunderschÃ¶nen guten Vormittag!

Ich benutze ein gentoo.amd64 und wollte das portage-Overlay fÃ¼r sabayon benutzen: Allerdings kam es da zu einem problem beim kompilieren des xorg-servers:

Code: Select all: >>> Emerging (98 of 101) x11-base/xorg-server-1.1.99.903-r2 to / * xorg-server-1.1.99.903.tar.bz2 MD5 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 RMD160 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 SHA1 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 SHA256 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 size ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 MD5 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 RMD160 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 SHA1 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 SHA256 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xorg-server-1.1.99.903.tar.bz2 ;-) ... [ ok ] * checking MesaLib-6.5.2.tar.bz2 ;-) ... [ ok ] * Forcing on xorg-x11 for new enough glxtokens.h... Switching to xorg-x11 OpenGL interface... done >>> Unpacking source... >>> Unpacking xorg-server-1.1.99.903.tar.bz2 to /var/tmp/portage/xorg-server-1.1.99.903-r2/work >>> Unpacking MesaLib-6.5.2.tar.bz2 to /var/tmp/portage/xorg-server-1.1.99.903-r2/work * Applying 1.1.99.903-mesa-6.5.2.patch ... [ ok ] * Applying 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ... * Failed Patch: 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ! * ( /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/xorg-server-1.1.99.903-r2/temp/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch-10829.out !!! ERROR: x11-base/xorg-server-1.1.99.903-r2 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack xorg-server-1.1.99.903-r2.ebuild, line 350: Called x-modular_patch_source x-modular.eclass, line 241: Called epatch '/usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch' eutils.eclass, line 341: Called die !!! Failed Patch: 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/portage/local/layman/sabayon' localhost jay # cat /var/tmp/portage/xorg-server-1.1.99.903-r2/temp/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch-10829.out ***** 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ***** ================================================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ================================================================== patching file hw/xfree86/common/xf86Helper.c Hunk #1 FAILED at 2386. 1 out of 1 hunk FAILED -- saving rejects to file hw/xfree86/common/xf86Helper.c.rej ================================================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ================================================================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- hw/xfree86/common/xf86Helper.c.orig 2006-12-13 16:21:35.000000000 +0100 |+++ hw/xfree86/common/xf86Helper.c 2006-12-13 18:23:53.000000000 +0100 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ================================================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ================================================================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- hw/xfree86/common/xf86Helper.c.orig 2006-12-13 16:21:35.000000000 +0100 |+++ hw/xfree86/common/xf86Helper.c 2006-12-13 18:23:53.000000000 +0100 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ================================================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ================================================================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- hw/xfree86/common/xf86Helper.c.orig 2006-12-13 16:21:35.000000000 +0100 |+++ hw/xfree86/common/xf86Helper.c 2006-12-13 18:23:53.000000000 +0100 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ================================================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ================================================================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- hw/xfree86/common/xf86Helper.c.orig 2006-12-13 16:21:35.000000000 +0100 |+++ hw/xfree86/common/xf86Helper.c 2006-12-13 18:23:53.000000000 +0100 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored localhost jay # emerge --resume *** Resuming merge... >>> starting parallel fetching >>> Emerging (1 of 4) x11-base/xorg-server-1.1.99.903-r2 to / * xorg-server-1.1.99.903.tar.bz2 MD5 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 RMD160 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 SHA1 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 SHA256 ;-) ... [ ok ] * xorg-server-1.1.99.903.tar.bz2 size ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 MD5 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 RMD160 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 SHA1 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 SHA256 ;-) ... [ ok ] * MesaLib-6.5.2.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xorg-server-1.1.99.903.tar.bz2 ;-) ... [ ok ] * checking MesaLib-6.5.2.tar.bz2 ;-) ... [ ok ] * Forcing on xorg-x11 for new enough glxtokens.h... Switching to xorg-x11 OpenGL interface... done >>> Unpacking source... >>> Unpacking xorg-server-1.1.99.903.tar.bz2 to /var/tmp/portage/xorg-server-1.1.99.903-r2/work >>> Unpacking MesaLib-6.5.2.tar.bz2 to /var/tmp/portage/xorg-server-1.1.99.903-r2/work * Applying 1.1.99.903-mesa-6.5.2.patch ... [ ok ] * Applying 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ... * Failed Patch: 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ! * ( /usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/xorg-server-1.1.99.903-r2/temp/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch-14125.out !!! ERROR: x11-base/xorg-server-1.1.99.903-r2 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack xorg-server-1.1.99.903-r2.ebuild, line 350: Called x-modular_patch_source x-modular.eclass, line 241: Called epatch '/usr/portage/local/layman/sabayon/x11-base/xorg-server/files/1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch' eutils.eclass, line 341: Called die !!! Failed Patch: 1.1.99.903-dri-drm-workaround-for-stupid-drivers.patch! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/portage/local/layman/sabayon'

Kann mir evtl. da jemand weiterhelfen? Ich habe schon gesehen, daÃŸ manche das gleiche Problem haben - Allerdings kam darauf keine Antwort...

Danke im Voraus fÃ¼r eure BemÃ¼hungen!

mfG

Jay

by **Jesterhead** » Sat Feb 10, 2007 15:16

Das Problem ist das der xorg-server den du versuchst zu kompilieren ein pre-release ist.

Entweder maskiere diese Version, oder unmaske den xorg-server 1.2 (die neue stabile version).

by **BigPapaJ** » Sat Feb 10, 2007 18:24

Das Problem ist ein wenig komplizierter als "nur" weil ich ne Testing "will" - Wenn ich mit einem -avuDN world nÃ¤mlich versuche mein System zu updaten will meldet er daÃŸ zwar der "x11-base/xorg-x11-7.2_rc3-r1" als Paket abhÃ¤ngigkeit eben diesen Testing braucht... Da stimmt doch was nicht, oder?

by **Jesterhead** » Sat Feb 10, 2007 20:41

Stimmt schon.

Entferne einfach die Masks und unmasks von Sabayon.
Portage installiert dann die neuesten Versionen.

Notfalls poste deine /etc/portage/package.mak
und /etc/portage/package.unmask

Sabayon Community

xorg kann nicht kompiliert werden

xorg kann nicht kompiliert werden

Who is online