Bug 352351 – games-engines/scummvm-1.2.1 build fails with CHOST=i686 but uname=x86_64

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Martin Doucha 2011-01-21 17:21:50 UTC]

I'm running i686 userspace under x86_64 kernel. ScummVM ebuild therefore passes --enable-nasm argument to configure script but then the configure script detects the system as x86_64 through uname -m and skips NASM detection. This leads to compile failure. You should either drop the --enable-nasm argument or force --arch=$CHOST as well for x86 systems.

Reproducible: Always

[Comment 1 David Abbott (RETIRED) 2011-01-22 19:22:07 UTC]

Archtested on x86: Everything fine

[Comment 2 Martin Doucha 2011-01-22 19:42:45 UTC]

(In reply to comment #1)
> Archtested on x86: Everything fine
> 

Did you test it under x86_64 kernel? The problem won't trigger if both kernel and userspace have the same platform.

[Comment 3 Mr. Bones. (RETIRED) 2011-01-26 08:51:36 UTC]

go ahead and attach a patch that makes it work for you.

[Comment 4 Martin Doucha 2011-01-26 21:33:54 UTC]

Created attachment 260816 [details, diff]
Ebuild patch: Force --host=$CHOST on x86 when calling configure

This patch fixes the compile failure.

[Comment 5 Mr. Bones. (RETIRED) 2011-01-26 22:22:50 UTC]

Why wouldn't we always just pass --host=$CHOST to configure?

[Comment 6 Martin Doucha 2011-01-27 09:57:49 UTC]

(In reply to comment #5)
> Why wouldn't we always just pass --host=$CHOST to configure?
> 

Sure you can. But x86 is the only one that really needs it because of --enable-nasm argument and the fact that some x86 configurations won't be autodetected as x86.

[Comment 7 Mr. Bones. (RETIRED) 2011-01-27 10:01:45 UTC]

ok, it's in portage.  thanks for the bug report.