Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Gary Thomas]

On 2016-10-03 20:48, Trevor Woerner wrote:

On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote:

Note: I just launched the build again with bitbake -k core-image-x11and

 the error did not occur again.
Well, a bit weird. Don't really know why does this error raised though.


Unless you made a change to the image, your second bitbake command will have
no effect which is [probably] why no message.

Also note that this is labeled "Error", but the image is actually built



It looks like the patch to which Khem refers was just added and pushed within
the last couple hours :-)


Actually, it was pushed on 2016-09-16




is it due to use of DATE and TIME issue ? I think there was such a patch 
proposed to meta-rpi see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10



--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Need inputs on integrating YP-Core Krogoth to Brilliant Blow-fish AGL release.

[Vijayakumar Badiger]

Hello All,

I am trying to integrate the YP Core - Krogoth 2.1.1 to the AGL Blowfish
release. I am getting the below error when I try to build the image.
Can you pls let me know how to fix this issue.

I see that in the earlier YP release the IMAGE_CMD was actually referenced
in the poky/meta/lib/oe/image.py. Now I don't see this file in that
location.
Please let me know if any one has faced this issue. Thanks.

/poky/meta-qti-internal/recipes/images/qt5-image.bb: No IMAGE_CMD defined
for IMAGE_FSTYPES entry 'fastboot' - possibly invalid type name or missing
support class:  --:--:--
ERROR: Failed to parse recipe:
/local/mnt/workspace/Oct-3/poky/meta-qti-internal/recipes/images/
qt5-image.bb


Cheers,
Vijay
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 05/10] layerindex: Add distribution to web interface and model.

[Paul Eggleton]

On Mon, 26 Sep 2016 14:25:33 Liam R. Howlett wrote:
> Add the distributions to the index.  This looks a lot like the machines
> and allows users to search for a particular distribution.
> 
> Signed-off-by: Liam R. Howlett 
> ---
>  layerindex/admin.py | 11 +
>  layerindex/models.py| 14 ++
>  layerindex/recipeparse.py   |  5 +++
>  layerindex/restviews.py | 10 -
>  layerindex/tools/import_classic.py  |  2 +
>  layerindex/update_layer.py  | 46 +++-
>  layerindex/urls.py  |  3 ++
>  layerindex/urls_branch.py   |  6 ++-
>  layerindex/views.py | 29 -
>  templates/layerindex/detail.html| 23 ++
>  templates/layerindex/distributions.html | 76

Sorry, I know it's probably going to be a pain, I'd really like to be using 
the term "distro" here rather than "distribution" - that would match up with 
our existing variable and path naming, and at the same time will resolve a few 
typos in this patch (e.g. "distribuiton").

Also, any change to the structure needs to be accompanied by a migration to 
handle existing databases. Since you're working with Django 1.8 you'd be 
creating its migrations rather than South's, and we had to start with a clean 
slate for that so I can see perhaps why you missed them.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 08/10] layerindex: Add collection and version to layerbranch

[Paul Eggleton]

On Mon, 26 Sep 2016 14:25:36 Liam R. Howlett wrote:
> Collection and version will be pulled from the layer.conf if it exists
> and dependencies will be resolved by first checking for layers with the
> dependency name and then checking for collections.  It is necessary to
> shutdown tinfoil to avoid bitbake complaining about multiple instances.

I'm not sure I understand why though, and there's not an explanation given 
here. What you're doing as a workaround only works by chance and I suspect it 
will break horribly when we do the tinfoil2 refactor in the next release (it's 
not expected that you'd have datastores still around and be parsing recipes 
when tinfoil has been shut down), so we *really* need to try to avoid shutting 
down like this. Can you explain what you saw?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 07/10] layerindex: Detect dependencies from layer.conf files

[Paul Eggleton]

On Mon, 26 Sep 2016 14:25:35 Liam R. Howlett wrote:
> Read dependencies from layer.conf and try to create the LayerDependency
> entry by looking up the correct database object.  Dependencies are found
> by layer name only - no collection support.  layer.conf parsing is
> handled by the bitbake code.

I see you did some refactoring here to move some of the code needed to parse 
the layer conf to the utils module. Generally I do that kind of thing in a 
separate patch, although I won't insist upon it - however if you do do it as 
part of this patch then it needs to at least be mentioned as part of the 
commit message.


> diff --git a/layerindex/models.py b/layerindex/models.py
> index 6aec030..2db8818 100644
> --- a/layerindex/models.py
> +++ b/layerindex/models.py
> @@ -209,6 +209,9 @@ class LayerBranch(models.Model):
>  return "%s: %s" % (self.layer.name, self.branch.name)
> 
> 
> +def get_required(self):
> +return self.dependencies_set.filter(required=True)
> +
>  class LayerMaintainer(models.Model):
>  MAINTAINER_STATUS_CHOICES = (
>  ('A', 'Active'),
> @@ -230,6 +233,7 @@ class LayerMaintainer(models.Model):
>  class LayerDependency(models.Model):
>  layerbranch = models.ForeignKey(LayerBranch,
> related_name='dependencies_set') dependency = models.ForeignKey(LayerItem,
> related_name='dependents_set') 
> +required = models.BooleanField(default=True)
> 
>  class Meta:
>  verbose_name_plural = "Layer dependencies"

This "required" field doesn't seem to be used in this commit - can you move 
these two changes to be part of the "recommends" support patch where they are 
used?


> --- a/layerindex/tools/import_layer.py
> +++ b/layerindex/tools/import_layer.py
> @@ -19,6 +19,7 @@ import glob
>  import utils
>  import logging
>  import subprocess
> +from layerconfparse import LayerConfParse
> 
>  class DryRunRollbackException(Exception):
>  pass
> @@ -375,11 +376,18 @@ def main():
>  if layer.name != settings.CORE_LAYER_NAME:
>  if not core_layer:
>  core_layer =
> utils.get_layer(settings.CORE_LAYER_NAME) 
> +
>  if core_layer:
> +logger.debug('Adding dep %s to %s' %
> (core_layer.name, layer.name)) layerdep = LayerDependency()
>  layerdep.layerbranch = layerbranch
>  layerdep.dependency = core_layer
>  layerdep.save()
> +layerconfparser = LayerConfParse(logger=logger)
> +config_data = layerconfparser.parse_layer(layerdir)
> +layerconfparser.shutdown()
> +utils.add_dependencies(layerbranch, config_data,
> logger=logger) 
> +

Use try..finally here to ensure shutdown() gets run.


>  # Get some extra meta-information
>  readme_files = glob.glob(os.path.join(layerdir, 'README*'))
> diff --git a/layerindex/update.py b/layerindex/update.py
> index 423eb53..ecd2380 100755
> --- a/layerindex/update.py
> +++ b/layerindex/update.py
> @@ -16,6 +16,8 @@ import subprocess
>  import signal
>  from distutils.version import LooseVersion
>  import utils
> +from layerconfparse import LayerConfParse
> +
> 
>  import warnings
>  warnings.filterwarnings("ignore", category=DeprecationWarning)
> @@ -92,7 +94,7 @@ def main():
> 
>  utils.setup_django()
>  import settings
> -from layerindex.models import Branch, LayerItem
> +from layerindex.models import Branch, LayerItem, LayerDependency
> 
>  logger.setLevel(options.loglevel)
> 
> @@ -201,6 +203,22 @@ def main():
>  # Interrupted by user, break out of loop
>  break
> 
> +# Once indexed, then conf/layer.conf dependencies should be
> reevaluated. 

Shouldn't this be triggered solely when layer.conf changes rather than every 
time?


> +layerconfparser = LayerConfParse(logger=logger,
> bitbakepath=bitbakepath) 
> +for branch in branches:
> +for layer in layerquery:
> +urldir = layer.get_fetch_dir()
> +repodir = os.path.join(fetchdir, urldir)
> +
> +layerbranch = layer.get_layerbranch(branch)
> +if layerbranch.vcs_subdir:
> +repodir = os.path.join(repodir, layerbranch.vcs_subdir)
> +config_data = layerconfparser.parse_layer(repodir)
> +utils.add_dependencies(layerbranch, config_data,
> logger=logger)
> +
> +layerconfparser.shutdown()

Use try..finally here as well.

> diff --git a/layerindex/utils.py b/layerindex/utils.py
> index 23b81f5..f82f8c7 100644
> --- a/layerindex/utils.py
> +++ b/layerindex/utils.py
> @@ -27,6 +27,114 @@ def get_layer(layername):
>  return res[0]
>  return None
> 
> +def get_dependency_layer(depname, version_str=None, logger=None):
> +from layerindex.models import LayerItem, LayerBranch

Re: [yocto] [layerindex-web][PATCH 02/10] layerindex/tools/import_layer.py: Sanitize layer name.

[Paul Eggleton]

On Mon, 26 Sep 2016 14:25:30 Liam R. Howlett wrote:
> Django will produce a cryptic error message if layers are added with
> invalid names.  Sanitize the layer names when trying to add them.
> 
> Signed-off-by: Liam R. Howlett 
> ---
>  layerindex/tools/import_layer.py | 6 ++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/layerindex/tools/import_layer.py
> b/layerindex/tools/import_layer.py index 9b5da22..8d9e8cb 100755
> --- a/layerindex/tools/import_layer.py
> +++ b/layerindex/tools/import_layer.py
> @@ -181,6 +181,8 @@ def get_github_layerinfo(layer_url, username = None,
> password = None):
> 
> 
>  def main():
> +valid_layer_name = re.compile('[-\w]+$')
> +
>  parser = optparse.OptionParser(
>  usage = """
>  %prog [options]  [name]""")
> @@ -222,6 +224,10 @@ def main():
>  if layer_name.endswith('.git'):
>  layer_name = layer_name[:-4]
> 
> +if not valid_layer_name.match(layer_name):
> +logger.error('Invlaid layer name "%s" -  Layer name can only
> include letters, numbers and dashes.', layer_name) 
> +sys.exit(1)

Typo "Invlaid", and the indenting is out here too.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 06/10] layerindex/tools/import_project: Add import_project

[Paul Eggleton]

On Mon, 26 Sep 2016 14:25:34 Liam R. Howlett wrote:
> import_project will scan through a project and find any layer and add it
> to the database by calling import_layer on each layer.  This differs
> from import_layer as it tires to figure out the remote url and uses the
> subdirectory (if one exists) as the name.

Looks good, but the two dryrun blocks have incorrect indenting.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Khem Raj]

I guess you need to look at sognatures and see why its changing.

On Oct 3, 2016 1:39 PM, "Trevor Woerner"  wrote:

> Odd... even with this patch I'm still seeing sporadic failures :-(
>
> On Mon, Oct 3, 2016 at 2:48 PM, Trevor Woerner  wrote:
> > On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote:
> >> Note: I just launched the build again with bitbake -k
> core-image-x11and
> >>
> >>  the error did not occur again.
> >> Well, a bit weird. Don't really know why does this error raised though.
> >
> > It looks like the patch to which Khem refers was just added and pushed
> within
> > the last couple hours :-)
> >
> >> is it due to use of DATE and TIME issue ? I think there was such a
> patch proposed to meta-rpi see
> >> http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=
> 4c02c7ce07121c2f5367204445f93199d828bb10
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Trevor Woerner]

Odd... even with this patch I'm still seeing sporadic failures :-(

On Mon, Oct 3, 2016 at 2:48 PM, Trevor Woerner  wrote:
> On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote:
>> Note: I just launched the build again with bitbake -k core-image-x11and
>>
>>  the error did not occur again.
>> Well, a bit weird. Don't really know why does this error raised though.
>
> It looks like the patch to which Khem refers was just added and pushed within
> the last couple hours :-)
>
>> is it due to use of DATE and TIME issue ? I think there was such a patch 
>> proposed to meta-rpi see
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Trevor Woerner]

On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote:
> Note: I just launched the build again with bitbake -k core-image-x11and
> 
>  the error did not occur again.
> Well, a bit weird. Don't really know why does this error raised though.

It looks like the patch to which Khem refers was just added and pushed within
the last couple hours :-)

> is it due to use of DATE and TIME issue ? I think there was such a patch 
> proposed to meta-rpi see
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Karim ATIKI]

Hi all,


Note: I just launched the build again with bitbake -k core-image-x11and

 the error did not occur again.
Well, a bit weird. Don't really know why does this error raised though.

Karim


De : yocto-boun...@yoctoproject.org  de la part 
de Karim ATIKI 
Envoyé : lundi 3 octobre 2016 18:31
À : Khem Raj; yocto
Objet : Re: [yocto] [meta-raspberrypi] taskhash mismatch



Hi Khem,

I have the same issue.
Get the latest master branches of poky, meta-raspberrypi and meta-oe.
Built a core-image-x11 and get the error:

ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
d77076c1266433c3dcd51a78947f273f versus 0eb1129a3545034a516ca72e5804ac33 for 
/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb.do_image_rpi_sdimg
ERROR: Taskhash mismatch d77076c1266433c3dcd51a78947f273f versus 
0eb1129a3545034a516ca72e5804ac33 for 
/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb.do_image_rpi_sdimg



Karim



De : yocto-boun...@yoctoproject.org  de la part 
de Khem Raj 
Envoyé : lundi 3 octobre 2016 01:51
À : Trevor Woerner
Cc : yocto@yoctoproject.org
Objet : Re: [yocto] [meta-raspberrypi] taskhash mismatch


> On Oct 2, 2016, at 7:34 AM, Trevor Woerner  wrote:
>
> Hi,
>
> For the last week or so my raspberry pi builds have been failing with:
>
> ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
> 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
> ERROR: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus 
> a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
>
> This is with both poky and oe+bitbake, master branches all around, and fully
> up-to-date. Before sending this email I pulled yet again and re-tested just to
> confirm.
>

is it due to use of DATE and TIME issue ? I think there was such a patch 
proposed to meta-rpi see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10

> Poky:
>
>Build Configuration:
>BB_VERSION= "1.31.1"
>BUILD_SYS = "x86_64-linux"
>NATIVELSBSTRING   = "SUSELINUX-42.1"
>TARGET_SYS= "arm-poky-linux-gnueabi"
>MACHINE   = "raspberrypi"
>DISTRO= "poky"
>DISTRO_VERSION= "2.1+snapshot-20161002"
>TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>TARGET_FPU= "hard"
>meta
>meta-poky = "master:3a73fe0efcb7aeefcca7011bba887caad03d4d03"
>meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
>
> OE + bitbake:
>
>Build Configuration:
>BB_VERSION= "1.31.1"
>BUILD_SYS = "x86_64-linux"
>NATIVELSBSTRING   = "SUSELINUX-42.1"
>TARGET_SYS= "arm-oe-linux-gnueabi"
>MACHINE   = "raspberrypi"
>DISTRO= "nodistro"
>DISTRO_VERSION= "nodistro.0"
>TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>TARGET_FPU= "hard"
>meta  = "master:21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935"
>meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
yocto Info Page
lists.yoctoproject.org
Discussion of all things about the Yocto Project. Read our Community Guidelines 
or learn more about how to participate in other community discussions.




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build a toolchain compiler with ARM hard-float support

[Lennart Sorensen]

On Thu, Sep 29, 2016 at 08:17:47AM -0500, Mark Hatle wrote:
> The machine configuration file should be setting the 'DEFAULTTUNE' variable to
> an appropriate ISA and ABI (hard float) for your configuration.  If it is not,
> you may have to create your own variant and change the DEFAULTTUNE setting --
> assuming the board supports the necessary hard float components.  (And yes,
> there are some armv7a variants that people removed the VFP instructions from 
> --
> even though it's theoretically against spec.)

ARM says the Cortex-A5 and A9 are both optional VFP, so I don't think
it is against the spec in any way.

-- 
Len Sorensen
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error: Nothing PROVIDES 'libxfont'

[Dishu Sharma]

Hello Ma'am/Sir,

While doing $ bitbake xorg-xserver , I am getting a error :
Error: Nothing PROVIDES 'libxfont'

libxfont recipe is present in meta/recipes-graphics/xorg-lib/
Could you please help me in debugging  this.

Thankyou,
Priyanshu Sharma
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

[Karim ATIKI]

Hi Khem,

I have the same issue.
Get the latest master branches of poky, meta-raspberrypi and meta-oe.
Built a core-image-x11 and get the error:

ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
d77076c1266433c3dcd51a78947f273f versus 0eb1129a3545034a516ca72e5804ac33 for 
/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb.do_image_rpi_sdimg
ERROR: Taskhash mismatch d77076c1266433c3dcd51a78947f273f versus 
0eb1129a3545034a516ca72e5804ac33 for 
/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb.do_image_rpi_sdimg



Karim



De : yocto-boun...@yoctoproject.org  de la part 
de Khem Raj 
Envoyé : lundi 3 octobre 2016 01:51
À : Trevor Woerner
Cc : yocto@yoctoproject.org
Objet : Re: [yocto] [meta-raspberrypi] taskhash mismatch


> On Oct 2, 2016, at 7:34 AM, Trevor Woerner  wrote:
>
> Hi,
>
> For the last week or so my raspberry pi builds have been failing with:
>
> ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
> 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
> ERROR: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus 
> a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
>
> This is with both poky and oe+bitbake, master branches all around, and fully
> up-to-date. Before sending this email I pulled yet again and re-tested just to
> confirm.
>

is it due to use of DATE and TIME issue ? I think there was such a patch 
proposed to meta-rpi see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10

> Poky:
>
>Build Configuration:
>BB_VERSION= "1.31.1"
>BUILD_SYS = "x86_64-linux"
>NATIVELSBSTRING   = "SUSELINUX-42.1"
>TARGET_SYS= "arm-poky-linux-gnueabi"
>MACHINE   = "raspberrypi"
>DISTRO= "poky"
>DISTRO_VERSION= "2.1+snapshot-20161002"
>TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>TARGET_FPU= "hard"
>meta
>meta-poky = "master:3a73fe0efcb7aeefcca7011bba887caad03d4d03"
>meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
>
> OE + bitbake:
>
>Build Configuration:
>BB_VERSION= "1.31.1"
>BUILD_SYS = "x86_64-linux"
>NATIVELSBSTRING   = "SUSELINUX-42.1"
>TARGET_SYS= "arm-oe-linux-gnueabi"
>MACHINE   = "raspberrypi"
>DISTRO= "nodistro"
>DISTRO_VERSION= "nodistro.0"
>TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>TARGET_FPU= "hard"
>meta  = "master:21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935"
>meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
yocto Info Page
lists.yoctoproject.org
Discussion of all things about the Yocto Project. Read our Community Guidelines 
or learn more about how to participate in other community discussions.




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [pseudo-native] No real function for mknod -- SOLVED

[Michel D'HOOGE]

Thank you Jussi,

> > No real function for mknod:
> > /mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
> > undefined symbol: mknod
> > No real function for mknodat:
> > /mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
> > undefined symbol: mknodat

> I believe this issue was fixed with a patch in poky master with
> commit e090775f7e in May (and later in an upstream pseudo release).
> Are you sure you are seeing this with poky master?

I did so many tests that I mixed all the problems and errors I met…

With the master branch, the problem was with the sanity check about the locale. 
I re-enabled en_US.utf8 on my console and the image creation succeeded! So I 
guess the problem appeared after an upgrade of my debian unstable system. But I 
was lost and getting crazy.

So thanks again :-)
M.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [pseudo-native] No real function for mknod

[Jussi Kukkonen]

On 3 October 2016 at 15:02, Michel D'HOOGE  wrote:
>
> Dear all,
>
> Since the end of last week, I try to produce any kind of images, with no
success :-(
>
> Note that even though I'm not a seasoned Yocto user, in more than a year
I managed many times to produce images & SDKs. And this time, I tried
several configs, erased everything and restarted from scratch, etc., but
with always the same problem.
>
> I have the following logs (in grey, so I guess not a warning nor an
error) when running bitbake:
> No real function for mknod:
/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
undefined symbol: mknod
> No real function for mknodat:
/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
undefined symbol: mknodat

I believe this issue was fixed with a patch in poky master with
commit e090775f7e in May (and later in an upstream pseudo release). Are you
sure you are seeing this with poky master?

 - Jussi

> And at the end, this crashes with:
> ERROR: core-image-minimal-initramfs-1.0-r0 do_rootfs: Unable to install
packages. Command
'/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/smart
--log-level=warning
--data-dir=/mnt/Yocto/Fabric-x64/build/tmp/work/genericx86_64-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/var/lib/smart
install --attempt -y ' returned 1:
>
>
> I tried the poky git repo with krogoth (HEAD & mid-september) and master;
with recipes core-image-minima & core-image-sato.
>
> I know that I always have a warning from bitbake about "Debian-unstable"
not being validated, but so far, it worked.
>
>
> So if any of you has an idea, I'd be most grateful!
> Michel
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] fix-parallel-build.patch error Krogoth branch

[idealsim]

Hi, i have a problem with the patch give in  
sources/poky/meta/recipes-support/db/db/fix-parallel-build.patch. I have  
this error during the build :


NOTE: Applying patch 'fix-parallel-build.patch'  
(../sources/poky/meta/recipes-support/db/db/fix-parallel-build.patch)
ERROR: Command Error: 'quilt --quiltrc  
/home/xxx/udoo-community-bsp/SA62/tmp/sysroots/x86_64-linux/etc/quiltrc  
push' exited with 1  Output:

Applying patch fix-parallel-build.patch
patching file Makefile.in
Hunk #1 FAILED at 1034.
1 out of 1 hunk FAILED -- rejects in file Makefile.in
Patch fix-parallel-build.patch can be reverse-applied
DEBUG: Python function patch_do_patch finished
DEBUG: Python function do_patch finished
ERROR: Function failed: patch_do_patch

I use this layer https://github.com/graugans/meta-udoo for my card.

Can you help about this issue please ?


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [pseudo-native] No real function for mknod

[Michel D'HOOGE]

Dear all,

Since the end of last week, I try to produce any kind of images, with no 
success :-(

Note that even though I'm not a seasoned Yocto user, in more than a year I 
managed many times to produce images & SDKs. And this time, I tried several 
configs, erased everything and restarted from scratch, etc., but with always 
the same problem.

I have the following logs (in grey, so I guess not a warning nor an error) when 
running bitbake:
No real function for mknod: 
/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
 undefined symbol: mknod
No real function for mknodat: 
/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64/libpseudo.so:
 undefined symbol: mknodat

And at the end, this crashes with:
ERROR: core-image-minimal-initramfs-1.0-r0 do_rootfs: Unable to install 
packages. Command 
'/mnt/Yocto/Fabric-x64/build/tmp/sysroots/x86_64-linux/usr/bin/smart 
--log-level=warning 
--data-dir=/mnt/Yocto/Fabric-x64/build/tmp/work/genericx86_64-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/var/lib/smart
 install --attempt -y ' returned 1:


I tried the poky git repo with krogoth (HEAD & mid-september) and master; with 
recipes core-image-minima & core-image-sato.

I know that I always have a warning from bitbake about "Debian-unstable" not 
being validated, but so far, it worked.


So if any of you has an idea, I'd be most grateful!
Michel
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

[Gary Thomas]

On 2016-10-03 08:07, Karim ATIKI wrote:

Hi Gary



The key is that you must use the latest OE-core (or Poky/Yocto) layer.



Sorry, but isn't it what I did by cloning the very latest branches ?
Or do you also mean that I need to clone also the very latest poky as well ?


Yes, you also need the latest [master branch] version of Poky for this to work.

n.b. it's polite to CC the mailing list so that everyone benefits from the 
answers.



*De :* yocto-boun...@yoctoproject.org  de la part de 
Gary Thomas 
*Envoyé :* lundi 3 octobre 2016 06:58
*À :* yocto@yoctoproject.org
*Objet :* Re: [yocto] [meta-raspberrypi] failed to copy the final 
***rootfs.rpi-sdimg image file

On 2016-10-02 17:58, Karim ATIKI wrote:

Hi Gary,



That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.



I've cloned meta-raspberrypi and meta-openembedded with the latest branches.

It still fails at the same step ☹ (see below).


The key is that you must use the latest OE-core (or Poky/Yocto) layer.




I'm building a custom core-image-x11 for my raspberrypi3 board, with poky 
krogoth.

In the very last steps:


ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Function failed: 
do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)


ERROR: Logfile of failure stored in:

/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110


Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_rpi_sdimg
| Creating filesystem with Boot partition 40960 KiB and RootFS 430080 KiB

| dd: failed to open 
'/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied

| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)

ERROR: Task 16 
(/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb, 
do_image_rpi_sdimg) failed
with exit code '1'
NOTE: Tasks Summary: Attempted 4771 tasks of which 4770 didn't need to be rerun 
and 1 failed.
No currently running tasks (4367 of 4773)


It looks like it tries to create the image in the path:
  /core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied


I looked into the bbclass, and at first glance I'd say that the respective path
is "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"


So ${IMGDEPLOYDIR} seems to be empty.


I haven't found any reference to IMGDEPLOYDIR elsewhere.



Make sure you have the latest [master] revisions.  This should have been fixed 
by:

commit 4817e2c087097c02755d6309304878e42cf61d3c
Author: Andreas Müller 
Date:   Tue Sep 13 02:19:06 2016 +0200

sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-core



That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto