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 14:15:25 -0700 [thread overview]
Message-ID: <4F9717ED.9020503@gmail.com> (raw)
In-Reply-To: <1335301431.3133.144.camel@x121e.pbcl.net>
On 04/24/2012 02:03 PM, Phil Blundell wrote:
> On Tue, 2012-04-24 at 13:57 -0700, j wrote:
>> 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]
> Does this correlate with an actual problem, or did you just see those
> messages in the log and think that they were cause for concern?
I was assuming since the machine segfaulted and I could not get working
images they were related.
>
> If I had to guess I would say that this is probably some autoconf test
> which is tickling a bug in ld. You could probably establish which
> package is doing that by looking at the timestamps and correlating them
> with the build logs.
I will try this once the machines go through the process again.
>
>> 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
> That doesn't appear to be related to the ld segfault
> .
>> 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
> ... and nor really does this. This latter problem is almost certainly
> just a bug in the SDK packaging and nothing at all to do with your build
> host.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
I will just focus on trying to match timestamps with the segfault and
trying to sort out all the issues once I have a built image.
I know I do not fully grasp everything here so thank you for your help
and if I find anything relevant or can post further info on this I will
share. Unless there are more suggestions.
Thank you
next prev parent reply other threads:[~2012-04-24 21:25 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
2012-04-24 20:57 ` j
2012-04-24 21:03 ` Phil Blundell
2012-04-24 21:15 ` j [this message]
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=4F9717ED.9020503@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