Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
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 21:44:49 +0100	[thread overview]
Message-ID: <1335300289.3133.136.camel@x121e.pbcl.net> (raw)
In-Reply-To: <4F970F9C.7030508@gmail.com>

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.





  reply	other threads:[~2012-04-24 20:55 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 [this message]
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
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=1335300289.3133.136.camel@x121e.pbcl.net \
    --to=philb@gnu.org \
    --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