Bug 672492 – net-libs/webkit-gtk - cross-compiling from x86_64 to i686 - CalleeBits.h:54:81: error: 'TagBitsWasm' was not declared in this scope

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description jan vereecke 2018-12-04 11:09:56 UTC]

when using a x86_64 machine to crosscompile webkit-gtk 2.22.2 or 2.22.4 to i686 architecture, the compile fails with 
CalleeBits.h:54:81: error: 'TagBitsWasm' was not declared in this scope

Reproducible: Always

Steps to Reproduce:
1. Using a x86_64 machine: chroot
2. set in /etc/portage/make.conf:
CHOST="i686-pc-linux-gnu"
CPU_FLAGS_X86=" mmx mmxext sse sse2 sse3 ssse3"
CFLAGS="-march=bonnell -mtune=bonnell -mno-cx16 -O2 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -msse3 -mssse3"
CPPFLAGS=" -D_FILE_OFFSET_BITS=64"
CXXFLAGS="${CFLAGS}"
LDFLAGS="$LDFLAGS -Wl,--hash-style=gnu -Wl,--sort-common"

3. emerge -1 webkit-gtk
Actual Results:  
the compile fails with 
CalleeBits.h:54:81: error: 'TagBitsWasm' was not declared in this scope

Expected Results:  
The compile should have succeeded.


running 
linux32 emerge -1 webkit-gtk
the emerge succeeds.

CMAKE_SYSTEM_PROCESSOR is defined by CMake using (I believe) "uname -m", which incorrectly reports x86_64 (the architecture of the compiling machine) instead of i686 (the architecture of the target machine.

=> portage should based on CHOST call the ebuild command prefixed with linux32 or not.

[Comment 1 Jeroen Roovers (RETIRED) 2018-12-04 16:07:01 UTC]

Please attach the entire build log to this bug report.
Please post your `(cross-)emerge --info` output in a comment.