Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: util-macros.do_package failed Re: Build failure
Date: Sat, 05 Apr 2014 10:33:28 +0100	[thread overview]
Message-ID: <1396690408.13862.51.camel@ted> (raw)
In-Reply-To: <533FBEDD.3030902@windriver.com>

On Sat, 2014-04-05 at 16:29 +0800, Robert Yang wrote:
> 
> On 04/05/2014 01:18 AM, Robert Yang wrote:
> >
> > Hi Andreas,
> >
> > I met the error on the master, we seldom met this error, but we did meet
> > it once in a while, I did several rough investigations, I think that the
> > problem is happened when etc/passwd is being created but is null before
> > write anything into it, and the util-macros.do_package runs right at the
> > same time, here is a hack way to reproduce it: (Use qemux86 as an example):
> >
> > $ bitbake base-passwd
> >
> > # Move the passwd file
> > $ mv tmp/sysroots/qemux86/etc/passwd tmp/sysroots/qemux86/etc/passwd.bak
> >
> > # Create a passwd file which is null
> > $ touch tmp/sysroots/qemux86/etc/passwd
> >
> > $ bitbake util-macros
> >
> > Then we will see the errors.
> >
> > The build is be OK if there is no tmp/sysroots/qemux86/etc/passwd, maybe
> > the pwd.getpwnam() reads the host's /etc/passwd when there is no
> > tmp/sysroots/qemux86/etc/passwd (not sure about this). but it would fail
> > if it exists and is null.
> >
> > Maybe we can let the do_package depend on base-passwd:do_populate_sysroot
> > to fix the problem.
> >
> 
> It seems that this is not a good idea since once we add the following line,
> it would cause all the target recipe's do_package depends on
> base-passwd:do_populate_sysroot, this would cause the arch "all" depends on
> eglibc since base-passwd depends on eglibc, we may need fix in another way.
> 
> do_package[depends] += "base-passwd:do_populate_sysroot"

This is very similar to the issue:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5612

I think I'm leaning in favour of putting in a basic passwd/group file
into the sysroot, even if we have to maintain such a copy ourselves.

Cheers,

Richard



      reply	other threads:[~2014-04-05  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  9:15 Build failure Andreas Müller
2012-11-14  9:30 ` Andreas Müller
2014-04-04 17:18   ` util-macros.do_package failed " Robert Yang
2014-04-04 20:01     ` Burton, Ross
2014-04-04 22:44       ` Richard Purdie
2014-04-05  8:29     ` Robert Yang
2014-04-05  9:33       ` Richard Purdie [this message]

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=1396690408.13862.51.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@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