Runtime target 'openchrome' is unbuildable

[Paul Sokolovsky]

Hello,

On Thu, 13 Mar 2008 08:26:20 +0100
"Javi Roman" <javiroman at kernel-labs.org> wrote:

> On Wed, Mar 12, 2008 at 10:39 PM, Javi Roman
> <javiroman at kernel-labs.org> wrote:
> > I have got the following error when I add openchrome to my custom
> > file image:
> >
> >  ------------ my-image.bb ------------
> >  require packages/images/bootstrap-image.bb
> >
> >  export IMAGE_INSTALL += "j2re \
> >                 grub \
> >                 ipkg \
> >                 openchrome \
> >                 "
> >  inherit image
> >
> >  export IMAGE_BASENAME = "my-image"
> >  ------------------------------------------
> >
> >  $ bitbake my-image
> >
> >  NOTE: Resolving any missing task queue dependencies
> >  ERROR: '['/home/jroman/OE_EPIA/local/packages/images/my-image.bb']'
> >  RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity
> >  'openchrome' but it wasn't found in any PACKAGE or RPROVIDES
> > variables NOTE: Runtime target 'openchrome' is unbuildable,
> > removing... Missing or unbuildable dependency chain was:
> > ['openchrome'] ERROR: Required build target 'my-image' has no
> > buildable providers. Missing or unbuildable dependency chain was:
> > [my-image', 'openchrome']
> >
> >
> >  Openchrome bitbake package is a standard package of OE, so, what's
> > happening? Can anybody advice me?
> >
> >  Thanks a lot.
> >
> >  --
> >  Javi Roman
> >
> 
> BTW, when I try to make "openchrome" package directly I got the
> following error:
> 
> $ bitbake openchrome
> 
> .....
[]
> Applying patch configure.patch
> can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |--- trunk/configure.ac 2007-01-16 16:58:44.000000000 +0000
> |+++ trunk/configure.ac 2007-01-16 18:09:26.000000000 +0000
> --------------------------
> No file to patch.  Skipping patch.
> 2 out of 2 hunks ignored
> patching file m4/check-build.m4
> Patch configure.patch does not apply (enforce with -f)
> ERROR: Task 6
> (/home/jroman/OE_EPIA/openembedded/packages/openchrome/openchrome_svn.bb,
> do_patch) failed NOTE: Tasks Summary: Attempted 746 tasks of which
> 728 didn't need to be rerun and 1 failed.
> ERROR:
> '/home/jroman/OE_EPIA/openembedded/packages/openchrome/openchrome_svn.bb'
> failed
> 
> 
> Openchrome was tested?

Possibly yes, possibly no. .dev is development branch, so it doesn't
require formal testing to get stuff in. Also, there's a notion of
"bitrot" which especially applies to packages based on SCM revisions
(comparing to release versions). Also, some packages are used often and
always buildable in OE, some rarely, and their issues may be unnoticed
and unfixed for long time.

> Could anybody get around this problem?

You? OE is not a magic box out of which you can pull out anything on
wish, it's just a build tool. And anyone who does build engineering
should be prepared to do patching, patch fixing, version and
revision review and hunting, etc., anyway.

> 
> Thanks a lot.
> 
> 
> 
>        - Javi Roman



-- 
Best regards,
 Paul                          mailto:pmiscml at gmail.com