From: Richard Purdie <rpurdie@linux.intel.com>
To: Hector Oron <hector.oron@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Build failures on yocto
Date: Mon, 01 Nov 2010 20:48:19 +0000 [thread overview]
Message-ID: <1288644499.28481.67.camel@rex> (raw)
In-Reply-To: <AANLkTinu_38Fo9yC1Hpkgf_JN5FqW-WFfFxfxztvOhJr@mail.gmail.com>
Hi,
I don't have answers to all of the failures but let me try and respond
to the ones I have some ideas about:
On Mon, 2010-11-01 at 18:23 +0000, Hector Oron wrote:
> lenny_i386)
> cat <<EOF
> [...]
> | NOTE: Running
> /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/gmp-4.2.4/configure
> --build=x86_64-linux --host=x86_64-linux
> --target=x86_64-linux
> --prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr
> --exec_prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr
>
> --bindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/bin
> --sbindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/sbin
>
> --libexecdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/libexec
>
> --datadir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share
> --sysconfdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/etc
> --sharedstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/com
> --localstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/var
> --libdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/lib
>
> --includedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include
>
> --oldincludedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include
> --infodir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/info
> --mandir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/man
> ...
> | checking build system type... x86_64-pc-linux-gnu
> | checking host system type... x86_64-pc-linux-gnu
> | checking for a BSD-compatible install... /usr/bin/install -c
> [...]
> | checking size of unsigned short... 2
> | checking for unsigned... yes
> | checking size of unsigned... 4
> | checking for unsigned long... yes
> | checking size of unsigned long... 4
> | checking for mp_limb_t... yes
> | 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.
> | FATAL: oe_runconf failed
> NOTE: Task failed:
> /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/temp/log.do_configure.28892
> NOTE: package gmp-native-4.2.4-r0: task do_configure: failed
> ERROR: TaskFailed event exception, aborting
> NOTE: package gmp-native-4.2.4: failed
> ERROR: Build of
> /srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb
> do_configure failed
> ERROR: Task 556
> (/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb,
> do_configure) failed
> NOTE: Tasks Summary: Attempted 135 tasks of which 135 didn't need to
> be rerun and 1 failed.
> ERROR: '/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb'
> failed
> NOTE: build 201011011717: completed
> make: *** [/srv/build/builds/menuconfig2-i386/../build/rootfs/yocto/purple-3.2/foo]
> Error 1
> EOF
At a guess this is a 64 bit kernel and a 32 bit userspace? What does
"uname -a" show?
I suspect if you add
BUILD_ARCH = "i686"
to your local.conf, the build might work better? If you can confirm that
we can probably detect this problem and avoid this failure.
> ;;
> unstable_i386)
> cat <<EOF
> [...]
> | checking size of unsigned long... 4
> | 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.
> | FATAL: oe_runconf failed
> | ERROR: Task failed: ('function do_configure failed',
> '/srv/build/builds/build/rootfs/yocto/laverne-4.0/build/tmp/work/x86_64-linux/gmp-native-5.0.1-r0/temp/log.do_configure.13641')
> NOTE: package gmp-native-5.0.1-r0: task do_configure: Failed
> ERROR: Task 971
> (virtual:native:/srv/build/builds/build/rootfs/yocto/laverne-4.0/meta/recipes-support/gmp/gmp_5.0.1.bb,
> do_configure) failed with 1
> Waiting for 1 active tasks to finish:
> 1: gettext-native-0.17-r5 do_compile (pid 13646)
> NOTE: package gettext-native-0.17-r5: task do_compile: Succeeded
> ERROR: 'virtual:native:/srv/build/builds/build/rootfs/yocto/laverne-4.0/meta/recipes-support/gmp/gmp_5.0.1.bb'
> failed
> make: *** [/srv/build/builds/menuconfig2-i386/../build/rootfs/yocto/laverne-4.0/foo]
> Error 1
> EOF
Same as the above failure (64 bit kernel and 32 bit userspace)?
> ;;
> others|*)
> cat <<EOF
> - I need to setup "vm.mmap_min_addr = 0" under /etc/sysctl.conf
Right, but it detected that?
> - sh linked to dash makes build system fail
> (./build/rootfs/yocto/laverne-4.0/poky-init-build-env):
> (sid_i386)zumbi@enorme:/srv/build/builds/build/rootfs/yocto/laverne-4.0$
> checkbashisms poky-init-build-env
> possible bashism in poky-init-build-env line 24 ($BASH_SOMETHING):
> elif test x"$BASH_SOURCE" = x; then
> possible bashism in poky-init-build-env line 27 ($BASH_SOMETHING):
> . `dirname $BASH_SOURCE`/scripts/poky-env-internal
Ouch. We don't support building with /bin/sh as dash (way too many
broken scripts our there still) and the system would tell you as such if
it detected that. Looks like bashisms have made it into the setup script
though which we need to fix.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-01 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 18:23 Build failures on yocto Hector Oron
2010-11-01 20:48 ` Richard Purdie [this message]
2010-11-02 10:03 ` Hector Oron
2010-11-02 11:27 ` Richard Purdie
2010-11-02 9:17 ` Hector Oron
2010-11-02 9:51 ` Richard Purdie
2010-11-02 10:08 ` Hector Oron
2010-11-02 11:29 ` Richard Purdie
2010-11-02 11:39 ` Hector Oron
2010-11-02 12:07 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1288644499.28481.67.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=hector.oron@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.