From: Ulf Samuelsson <openembedded-core@emagii.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Feedback on building openembedded-core for qemuarm. Excerpts from buildlog
Date: Thu, 01 Dec 2011 15:49:06 +0100 [thread overview]
Message-ID: <4ED793E2.5070205@emagii.com> (raw)
In-Reply-To: <4ED66835.3050400@intel.com>
On 2011-11-30 18:30, Scott Garman wrote:
> On 11/29/2011 01:18 PM, Ulf Samuelsson wrote:
>>
>>>> Seen a couple of errors as well.
>>>>
>>>> 1. ERROR: Function 'useradd_sysroot' failed
>>>> Tried to access "/etc/group" but this was locked.
>>>> Problem disappeared the next time I rebuilt.
>>> Can you file a bug about this problem please. I think we need to go
>>> through the code paths in shadow and ensure its locking is sane. I took
>>> a quick look at the code and was left wondering what lckpwdf() does for
>>> example. Scott, could you take a look at this?
>>
>> Bugzilla is out of service, so bugs cannot be filed.
>
> I have filed a bug for this, and have been trying to reproduce it
> without success:
>
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1794
>
>> Haven't seen the issue since then so it is hard to give any details.
>> I used very high BB_NUMBER_THREADS = 24.
>
> I do have access to a system with a lot of cores, and have been doing
> builds on it.
>
> I'd just like to confirm that when you saw this, it was a build from
> scratch (e.g, not using sstate cache from a previous build). And also,
> you *weren't* building this from a remote filesystem (NFS), correct?
>
> Thanks,
>
> Scott
>
No NFS for sure.
I think this was the first build, but only 99% sure.
It disappered when I restarted the build.
Have not seen this problem repeated, but then, the build on this
machine has other problems
Packages tend to fail since the c++ compiler seems to ignore "--sysroot"
Machine = Ubuntu-11.10 x64.
This is with BB_NUMBER_THREADS = "4"
If I change this, then the same problem occur, but in a different package.
(Tried with "4" AND "24")
BR
Ulf
--
Best Regards
Ulf Samuelsson
eMagii
next prev parent reply other threads:[~2011-12-01 14:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 11:24 Feedback on building openembedded-core for qemuarm. Excerpts from buildlog Ulf Samuelsson
2011-11-26 12:38 ` Eric Bénard
2011-11-26 14:14 ` Ulf Samuelsson
2011-11-27 11:40 ` Richard Purdie
2011-11-27 11:47 ` Eric Bénard
2011-11-28 21:31 ` Ulf Samuelsson
2011-11-29 8:48 ` Eric Bénard
2011-11-29 15:03 ` Richard Purdie
2011-11-29 15:50 ` Koen Kooi
2011-11-29 16:03 ` Richard Purdie
2011-12-01 1:52 ` Khem Raj
2011-12-01 9:26 ` Richard Purdie
2011-11-29 19:36 ` Ulf Samuelsson
2011-11-29 20:06 ` Koen Kooi
2011-11-29 21:12 ` Ulf Samuelsson
2011-12-01 13:16 ` Philip Balister
2011-12-01 15:37 ` Koen Kooi
2011-12-01 16:31 ` Ulf Samuelsson
2011-12-02 9:46 ` Frans Meulenbroeks
2011-12-02 9:49 ` Koen Kooi
2011-12-02 22:36 ` Ulf Samuelsson
2011-11-29 21:18 ` Ulf Samuelsson
2011-11-30 17:30 ` Scott Garman
2011-12-01 14:49 ` Ulf Samuelsson [this message]
2011-12-03 20:03 ` Ulf Samuelsson
2011-12-04 11:20 ` Henning Heinold
2011-12-04 11:35 ` Richard Purdie
2011-12-07 22:51 ` Khem Raj
2011-12-07 23:45 ` Ulf Samuelsson
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=4ED793E2.5070205@emagii.com \
--to=openembedded-core@emagii.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.com \
/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