From: Gary Thomas <gary@mlbassoc.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Problems building from master
Date: Fri, 30 Nov 2012 10:12:13 -0700 [thread overview]
Message-ID: <50B8E8ED.5000802@mlbassoc.com> (raw)
In-Reply-To: <20121130164256.GH3436@jama.jama.net>
On 2012-11-30 09:42, Martin Jansa wrote:
> On Fri, Nov 30, 2012 at 08:09:56AM -0700, Gary Thomas wrote:
>> trying to build 'core-image-sato' with this configuration:
>>
>> Build Configuration:
>> BB_VERSION = "1.17.0"
>> BUILD_SYS = "i686-linux"
>> NATIVELSBSTRING = "Unknown"
>> TARGET_SYS = "arm-poky-linux-gnueabi"
>> MACHINE = "qemuarm"
>> DISTRO = "poky"
>> DISTRO_VERSION = "1.3+snapshot-20121130"
>> TUNE_FEATURES = "armv5 dsp thumb"
>> TARGET_FPU = "soft"
>> meta
>> meta-yocto
>> meta-yocto-bsp = "master:247b6a3754c2c50318e2a73d79981ba0e9cb560b"
>> meta-oe = "master:8e489120f9c4ae91e121ae9d33fecc1aacdf3257"
>>
>> Fails with:
>> /local/qemuarm_test/tmp/sysroots/i686-linux/usr/libexec/armv5te-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld: cannot find -lsndfile
>> collect2: error: ld returned 1 exit status
>> make[1]: *** [sbc/sbctester] Error 1
>> make[1]: *** Waiting for unfinished jobs....
>> arm-poky-linux-gnueabi-libtool: link: arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork --sysroot=/local/qemuarm_test/tmp/sysroots/qemuarm -D_FORTIFY_SOURCE=2
>> -I/local/qemuarm_test/tmp/sysroots/qemuarm/usr/include/dbus-1.0 -I/local/qemuarm_test/tmp/sysroots/qemuarm/usr/lib/dbus-1.0/include
>> -I/local/qemuarm_test/tmp/sysroots/qemuarm/usr/include/glib-2.0 -I/local/qemuarm_test/tmp/sysroots/qemuarm/usr/lib/glib-2.0/include -O2 -pipe -g -feliminate-unused-debug-types
>> -Wl,-O1 -Wl,--hash-style=gnu -o tools/hcisecfilter tools/hcisecfilter.o
>> make: *** [all] Error 2
>> ERROR: oe_runmake failed
>> ERROR: Function failed: do_compile (see /local/qemuarm_test/tmp/work/armv5te-poky-linux-gnueabi/bluez4/4.101-r3/temp/log
>
> missing libsndfile1 in depends?
>
>> I then ran 'bitbake core-image-sato -k' to see what other failures I came
>> up with. There were none.
>>
>> When I ran 'bitbake core-image-sato' again (after the run with -k that had
>> the single failure), it succeeded! Must be a parallel build issue.
>> I'm using:
>> BB_NUMBER_THREADS = "4"
>> PARALLEL_MAKE = "-j 4"
>>
>> I also had a problem building 'web-webkit':
>>
>> | /local/qemuarm_test/tmp/sysroots/i686-linux/usr/libexec/armv5te-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld: failed to set dynamic section sizes: Memory exhausted
>> | collect2: error: ld returned 1 exit status
>> | make[1]: *** [libwebkitgtk-1.0.la] Error 1
>> | make[1]: Leaving directory `/local/qemuarm_test/tmp/work/armv5te-poky-linux-gnueabi/webkit-gtk/1.8.2-r2/webkit-1.8.2'
>>
>> Any ideas on how I can fix the build of webkit-gtk?
>
> Add more RAM/swap.
Didn't help - my machine has 6GB RAM + 20GB SWAP - still fails.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2012-11-30 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 15:09 Problems building from master Gary Thomas
2012-11-30 16:42 ` Martin Jansa
2012-11-30 17:12 ` Gary Thomas [this message]
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=50B8E8ED.5000802@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=martin.jansa@gmail.com \
--cc=poky@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.