Bug 4529

Summary: x32 build fails with gmp_5.1.1 do_configure
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Alexandru Palalau <alexandrux.palalau>
Component: coreAssignee: Nitin Kamble <nitin.a.kamble>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium CC: dvhart, laurentiu.palcu, meta.mr.watcher, meta.watcher
Version: 1.5   
Target Milestone: 1.6   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
x32 gmp do_configure log none

Description Alexandru Palalau 2013-05-22 13:33:47 UTC
Created attachment 1220 [details]
x32 gmp do_configure log

Build Configuration:
BB_VERSION        = "1.19.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "CentOS-6.4"
TARGET_SYS        = "x86_64-poky-linux-gnux32"
MACHINE           = "qemux86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4+snapshot-20130522"
TUNE_FEATURES     = "mx32"
TARGET_FPU        = ""
meta              
meta-yocto        
meta-yocto-bsp    = "master:176a46b088135f2891983bb8540bc45389341d90"


Adding the following in local conf and building core-image-sato-sdk:
####################################
MACHINE = "qemux86-64"
DEFAULTTUNE = "x86-64-x32"
baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE', True) or 'INVALID'), True) or 'lib'}"
####################################

The image build fails at gmp_5.1.1 recipe, do_configure task with the following error:

| checking size of mp_limb_t... 4
| configure: error: Oops, mp_limb_t is 32 bits, but the assembler code
| in this configuration expects 64 bits.
| You appear to have set $CFLAGS, perhaps you also need to tell GMP the
| intended ABI, see "ABI and ISA" in the manual.
| Configure failed. The contents of all config.log files follows to aid debugging
| ERROR: oe_runconf failed

Attaching the entire log file
Comment 1 Laurentiu Palcu 2014-02-11 15:00:15 UTC
It's the same bug as 5783. I sent a patch on the ML.

*** This bug has been marked as a duplicate of bug 5783 ***