All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ulf@emagii.com,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: "Garman, Scott A" <scott.a.garman@intel.com>
Subject: Re: Feedback on building openembedded-core for qemuarm. Excerpts from buildlog
Date: Tue, 29 Nov 2011 15:03:49 +0000	[thread overview]
Message-ID: <1322579029.7964.0.camel@ted> (raw)
In-Reply-To: <4ED0CC76.4040606@emagii.com>

On Sat, 2011-11-26 at 12:24 +0100, Ulf Samuelsson wrote:
> Downloaded the latest, and tried building console-image for qemuarm.
> Host = Ubuntu 11.04 i686.
> 
> Looked through the build log, and thought I'd share it with the list.

Thanks for doing this, its valuable feedback.

> A number of warnings (see below)

We're trying to work through addressing those. Some of them are from
versions in meta-oe where there is a fix for the error in OECore (such
as the libgcc linker hash style).

> 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?

> 2.    "ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz" is no longer 
> available.
>          tzdata , same problem.
>          The recipe is located in two places.
>          meta-openembedded/meta-oe/recipes-extended/tz*/tz*.bb have the 
> problem
>          This is what the build uses.

This is something to raise with the meta-oe maintainers. I think there
isn't a problem in OECore.

> 3.    When I ran into this problem, I exited with ctrl-C.
>          This left some recipes in the middle of a fetch ,and the build 
> could not continue.
>          I had to "bitbake -c clean <package>" on all problematic 
> packages to recover.
>          Seems a little bit fragile to me.

Yes, this isn't good. Could you file a bug report on this please?

> 4.     linux-3.0 recipe in meta-ti does not build (On Ubuntu 11.10 x64).
>          Fails in the fetch stage.
>          I removed the layer, since it was not needed for qemuarm.

Makes sense and its something raise with the meta-ti layer maintainers
which I think I've seen elsewhere.

> 5.    When compiling on a Ubuntu 11.10 x64 host  (linux 3.x host)
>          tiff won't build.
>          Did:
>              bitbake console-image"
>              bitbake -c clean tiff
>              bitbake  tiff
>          - No luck
>          Reading through the mailing list, I found someone which deleted
>          $TMPDIR and then
>              bitbake tiff
>              bitbake console-image
>          That worked for me as well once, second time, same problem.
>          Problem is that #include <iostream> fails.
> 
>          I noted that "iostream" is built and available in 
> <sysroot>/usr/include/c++
>          On the host, it is located in /usr/incolude/c++/<version>
>          "tiff" build seems to be OK with Ubuntu 11.04 i686.

I think these errors should be fixed by recent changes. If not I'd be
interested in the full console log please.

Cheers,

Richard





  parent reply	other threads:[~2011-11-29 15:10 UTC|newest]

Thread overview: 32+ 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 [this message]
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
2011-12-03 20:03         ` Ulf Samuelsson
2011-12-04 11:20           ` Henning Heinold
2011-12-04 11:20             ` [OE-core] " Henning Heinold
2011-12-04 11:35             ` Richard Purdie
2011-12-04 11:35               ` [OE-core] " Richard Purdie
2011-12-07 22:51               ` Khem Raj
2011-12-07 22:51                 ` [OE-core] " 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=1322579029.7964.0.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.