From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] 3 build machines all failing in the same manner - was:ld segfault cant figure it out
Date: Tue, 24 Apr 2012 13:57:07 -0700 [thread overview]
Message-ID: <4F9713A3.4010803@gmail.com> (raw)
In-Reply-To: <1335300289.3133.136.camel@x121e.pbcl.net>
On 04/24/2012 01:44 PM, Phil Blundell wrote:
> On Tue, 2012-04-24 at 13:39 -0700, j wrote:
>> So the qa.log I attached previously is meaningless? The
>> warnings/messages mean nothing? To me the ld segfault is the reason most
>> of qa.log has messages. Also why would oe-classic build on my laptop and
>> one of the borrowed machines with no segfaults and no issues with the
>> completed images, but then doing the new setup and version used gives me
>> the build issues on multiple machines. I also do not understand why if
>> while building, the build machine segfaults while building some package
>> but the "offending" package does not fail.
> What exactly do you mean by "the build machine segfaults"? What
> precisely is the problem that you're having, and which particular
> messages in qa.log do you think are associated with "the ld segfault"?
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
The build machines all give messages like this just vary on libc version
listed
[47152.769257] ld[22617]: segfault at 403 ip 00007f2149cfd435 sp
00007fffb83ccb50 error 4 in libc-2.15.so[7f2149cb6000+197000]
2012-04-18T14:50:08-07:00 localhost kernel: [47163.860996] ld[31096]:
segfault at 403 ip 00007fc2da152435 sp 00007fffab491c30 error 4 in
libc-2.15.so[7fc2da10b000+197000]
qa.log has more than these messages but every machines logs are the same
like this
udev-182: udev:
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/udev-182-r0/packages-split/libgudev/lib/libgudev-1.0.so.0.1.1
links to something under exec_prefix
udev-182: ldd reports: libudev.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libudev.so.0
(0xdead1000)
libgobject-2.0.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libgobject-2.0.so.0
(0xdead2000)
libffi.so.5 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libffi.so.5
(0xdead3000)
libgthread-2.0.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libgthread-2.0.so.0
(0xdead4000)
libpthread.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libpthread.so.0
(0xdead5000)
libglib-2.0.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libglib-2.0.so.0
(0xdead6000)
librt.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/librt.so.1
(0xdead7000)
libc.so.6 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libc.so.6
(0xdead8000)
libgcc_s.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libgcc_s.so.1
(0xdead9000)
/lib/ld-linux.so.3 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/ld-linux.so.3
(0xdeada000)
udev-182: udev:
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/udev-182-r0/packages-split/udev/lib/udev/udevd
links to something under exec_prefix
udev-182: ldd reports: libblkid.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libblkid.so.1
(0xdead1000)
libkmod.so.2 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libkmod.so.2
(0xdead2000)
librt.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/librt.so.1
(0xdead3000)
libc.so.6 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libc.so.6
(0xdead4000)
libuuid.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libuuid.so.1
(0xdead5000)
libpthread.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libpthread.so.0
(0xdead6000)
/lib/ld-linux.so.3 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/ld-linux.so.3
(0xdead7000)
libcgroup-0.37.1: libcgroup:
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r1/packages-split/cgroups-pam-plugin/lib/security/pam_cgroup.so.0.0.0
links to something under exec_prefix
libcgroup-0.37.1: ldd reports: libcgroup.so.1 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/usr/lib/libcgroup.so.1
(0xdead1000)
libpthread.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libpthread.so.0
(0xdead2000)
libpam.so.0 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libpam.so.0
(0xdead3000)
libdl.so.2 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libdl.so.2
(0xdead4000)
libc.so.6 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/libc.so.6
(0xdead5000)
/lib/ld-linux.so.3 =>
/home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beagleboard/lib/ld-linux.so.3
(0xdead6000)
each one of the machines from a fresh install have this problem. The
resulting image boots but does not fully function. I have issues such as
the native sdk does not install all the packages correctly.
example would be install.
normall you would find it
/usr/bin/install
I end up with
/home/bill/OE/usr/bin/install
How I have done each mahine
fresh install Ubuntu
reconfigure dash
install required packages as per OE and your distro
update then reboot
git clone angstrom setup-scripts
configure machine as beagleboard.
source the environment
build either just perl first. to save time as it will segfault building
anything on a fresh install
or build a complete image such as xfce-nm-image or systemd-gnome-image.
I change nothing else in the configs.
next prev parent reply other threads:[~2012-04-24 21:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 22:46 ld segfault cant figure it out j
2012-04-13 22:50 ` j
2012-04-16 22:11 ` [oe-core] " j
2012-04-16 22:28 ` Gary Thomas
2012-04-16 22:32 ` j
2012-04-16 22:41 ` Gary Thomas
2012-04-16 22:54 ` j
2012-04-16 22:34 ` j
2012-04-17 1:43 ` j
2012-04-17 15:41 ` J. L.
2012-04-17 15:54 ` Gary Thomas
2012-04-17 16:11 ` J. L.
2012-04-17 16:13 ` J. L.
2012-04-17 19:09 ` j
2012-04-17 19:34 ` Mark Hatle
2012-04-17 19:49 ` j
2012-04-17 20:17 ` j
2012-04-17 21:16 ` j
2012-04-18 0:37 ` j
2012-04-18 5:30 ` Khem Raj
2012-04-18 5:40 ` j
2012-04-18 22:00 ` Khem Raj
2012-04-19 3:32 ` j
2012-04-19 6:24 ` Khem Raj
2012-04-20 0:39 ` j
2012-04-20 11:13 ` Gary Thomas
2012-04-20 16:17 ` j
2012-04-20 18:03 ` j
2012-04-21 21:47 ` [oe-core] 3 build machines all failing in the same manner - was:ld " j
2012-04-24 20:39 ` j
2012-04-24 20:44 ` Phil Blundell
2012-04-24 20:57 ` j [this message]
2012-04-24 20:57 ` j
2012-04-24 21:03 ` Phil Blundell
2012-04-24 21:15 ` j
2012-04-27 17:16 ` j
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=4F9713A3.4010803@gmail.com \
--to=vwyodapink@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox