From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe-core] ld segfault cant figure it out
Date: Tue, 17 Apr 2012 14:34:13 -0500 [thread overview]
Message-ID: <4F8DC5B5.600@windriver.com> (raw)
In-Reply-To: <4F8DBFF3.2060508@gmail.com>
On 4/17/12 2:09 PM, j wrote:
> On 04/17/2012 09:13 AM, J. L. wrote:
>> <snip>
>>
>>
>> <http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel>
>>
>>
>>
> I went for a build on the borrowed machine again but this time I did not
> go into X just stayed in RL3. Then ran bitbake perl, on a clean build
> dir. It is just about to finish building a few steps away but where I
> normally get the segfaults, it has not spit those out. There are no QA
> logs being generated either. So looks like it had/has something to do
> with running X, both systems are running nvidia graphics cards. The
> laptop has a new mobile one, borrowed an old one that is nouveau
> compatible. So both open and closed nvidia drivers were tried. But
> something when in the graphical environment is giving the segfault
> issues I have been seeing. I have not yet verified if killing X on the
> laptop builds and eliminates the issues as well.
>
> Will post back once I have built the kernel on both machines with no X
> running.
There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is something in
perl (or elsewhere) trying to run qemu to finish up a task?
--Mark
> Thank you
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-04-17 19:43 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 [this message]
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
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=4F8DC5B5.600@windriver.com \
--to=mark.hatle@windriver.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