[solved] ERROR: x11-base/x11-drm-20080710 failed.

m_0_r_0_n · Last edited by m_0_r_0_n on Mon Sep 15, 2008 2:14 pm; edited 1 time in total

Hi,
I dont understand the following error and how to fix it. Can you help me?

*
* ERROR: x11-base/x11-drm-20080710 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3797: Called src_compile_os
* environment, line 3826: Called src_compile_linux
* environment, line 3818: Called linux-mod_src_compile
* environment, line 2983: Called die
* The specific snippet of code:
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CC=\"$(get-KERNEL_CC)\" LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
* The die message:
* Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CC=i686-pc-linux-gnu-gcc LDFLAGS= LINUXDIR="/usr/src/linux" DRM_MODULES=" radeon.ko" modules
*
* 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-base/x11-drm-20080710/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-base/x11-drm-20080710/temp/environment'.
*
* GNU info directory index is up-to-date.

NeddySeagoon · Posted: Sat Sep 13, 2008 11:13 pm Post subject:

m_0_r_0_n,

Thats not an error message, its a status report, saying it failed.
The error will be in /var/tmp/portage/x11-base/x11-drm-20080710/temp/build.log

Please post that file.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Hu · Watchman Joined: 06 Mar 2007 Posts: 6828

Also, post the output of emerge --info.

m_0_r_0_n · Posted: Sun Sep 14, 2008 6:41 am Post subject:

I think I dont need to paste the complete build.log

The error message is:

[...]
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/ati_pcigart.c: In Funktion »gart_insert_page_into_table«:
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/ati_pcigart.c:49: Warnung: Implizite Deklaration der Funktion »upper_32_bits«
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/ati_pcigart.c: In Funktion »drm_ati_pcigart_init«:
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/ati_pcigart.c:129: Warnung: Variable »page_base« wird nicht verwendet
CC [M] /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_sman.o
CC [M] /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_hashtab.o
CC [M] /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_mm.o
CC [M] /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_object.o
CC [M] /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.o
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c: In Funktion »drm_bo_vm_fault«:
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c:220: Fehler: Zu wenige Argumente für Funktion »drm_bo_wait«
make[2]: *** [/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.o] Fehler 1
make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.20-gentoo-r10'
make: *** [modules] Fehler 2
*
* ERROR: x11-base/x11-drm-20080710 failed.
* Call stack:
[...]

It s a message in german. It means that there too few arguments for the funkction drm_bo_wait

emerge --info prints:

m_0_r_0_n · Posted: Sun Sep 14, 2008 4:32 pm Post subject:

The function drm_bo_wait is defined in
/var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_bo.c

int drm_bo_wait(struct drm_buffer_object *bo,
int lazy,
int interruptible,
int no_wait,
int check_unfenced)

Then I changed the function call drm_bo_wait in line 220 of the the file /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c

from
err = drm_bo_wait(bo, 0, 1, 0);
to
err = drm_bo_wait(bo, 0, 1, 0, 1);

to match the parameters of the defined function. The I tried to emerge all new packages to get an update to date system, but I always get the same error! Then I noticed that my changes were removed. The line 220 tries to call the function with four argumensts again. What the hell! Why does portage ignore my change?

m_0_r_0_n · Posted: Mon Sep 15, 2008 11:35 am Post subject:

Thanks for you help so far.

I tried to add a patch as described in http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild#Fixing_a_Patched_Ebuild

1. Rename original feature.c to feature.c.orig

I rename /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c to /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c.orig

2. Put feature.c.orig and your new feature.c to the same folder

I copied both files to /root/gentoofix

3. cd /root/gentoofix && diff -u drm_compat.c.orig drm_compat.c > drm_compat-20080815.patch

4. I copied drm_compat-20080815.patch to /usr/portage/x11-base/x11-drm/files/

5. Then I added the line epatch /usr/portage/x11-base/x11-drm/files/drm_compat-20080815.patch to the function src_unpack() { in the file /usr/portage/x11-base/x11-drm/x11-drm-20080710.ebuild

6. ebuild /usr/portage/x11-base/x11-drm/x11-drm-20080710.ebuild digest

The error message is:

m_0_r_0_n

The problem was that I didnt use aboslute pathnames to the file to patch.

--- /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c.orig 2008-09-15 15:48:18.000000000 +0200
+++ /var/tmp/portage/x11-base/x11-drm-20080710/work/drm/linux-core/drm_compat.c 2008-09-15 15:55:58.000000000 +0200
@@ -217,7 +217,7 @@

mutex_lock(&bo->mutex);

- err = drm_bo_wait(bo, 0, 1, 0);
+ err = drm_bo_wait(bo, 0, 1, 0, 1);
if (err) {
data->type = (err == -EAGAIN) ?
VM_FAULT_MINOR : VM_FAULT_SIGBUS;

Battousai · Developer Joined: 05 Jan 2004 Posts: 7

Hello.

Thanks for reporting this. It's been filed as a Gentoo bug now, and will have to go upstream once I've made the patch for it.

This appears to be caused by a compatibility function for rather old kernels (I see you're using 2.6.20) which isn't necessarily triggered by newer ones -- I tested this package with 2.6.25 and didn't encounter it. I guess they missed updating a call to drm_bo_wait() after adding an argument to it.

It will be fixed in portage shortly, and hopefully upstream before too long.