I'm following an approach described in JumpNow Technologies to build a Yocto image for a Raspberry PI. These steps utilize the Yocto meta-raspberrypi layer.
The bitbake process fails when doing a git fetch from git://github.com/raspberrypi/firmware.git. The relevant part of the log is below.
bcm2835-bootfiles-20170303-r42 do_fetch: Failed to fetch URL git://github.com/raspberrypi/firmware.git;protocol=git;branch=master, attempting MIRRORS if available
ERROR: bcm2835-bootfiles-20170303-r42 do_fetch: Fetcher failure: Unable to find revision 78bcdeae6bda4ecbc599af8c75e16c2ddd392d3a in branch master even from upstream
ERROR: bcm2835-bootfiles-20170303-r42 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/firmware.git;protocol=git;branch=master'. Unable to fetch URL from any source.
ERROR: bcm2835-bootfiles-20170303-r42 do_fetch: Function failed: base_do_fetch
This step takes close to an hour or more. I'm assuming it's timing out somewhere and hence it fails. This is happening because it's pulling down several GB.
I can fetch this repository manually separate to bitbake. Is there a way to insert the repo contents downloaded manually? e.g. into the downloads or tmp directly?
Alternatively, does anyone have a suggestion for dealing with this download?
The issue was with meta-rpi as identified by #jku. I'm told jumpnow has fixed the issue.
Related
I'm developing on Yocto 2.4 rockowith a BSP given by my provider. I'm trying to build modemmanager from the meta-openembedded layer, included in the meta-oe sub layer.
The configure task fail and give me as error :
checking for gobject-introspection...
configure: error: gobject-introspection-1.0 is not installed
After some search I've installed the libgirepository1.0-dev package on my host machine. But the error is always present.
I've continued investigations, and find in my recipe log the line :
DEBUG: EXCLUDE FROM WORLD: virtual:native:/home/test/share/sc20_linux/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.52.1.bb
I've tried to find which recipe excludes the dependency, with no success.
Can you help me to understand how works the EXCLUDE_FROM_WORLD mechanism ?
Thanks for your help.
I suspect that is debug output and doesn't mean the recipe is excluded. Have you looked at the modemmanager recipe to see if it has a DEPENDS on gobject-introspection-native and perhaps gobject-introspection? If not, or the PACKAGECONFIG isn't set, try adding the DEPENDS or enabling the PACKGECONFIG?
Also, have you tried simply building "bitbake object-introspection-native" and "bitbake object-introspection". You should get an error about why they ar disabled if you try and build them directly and they are excluded/disabled for some reason.
I'm trying to build core-image-minimal for raspberrypi4-64 on the zeus branch
and I had to create the file sanity.conf and I'm getting this errors:
fstrati$ bitbake -c cleanall core-image-minimal
Loading cache: 100% Time: 0:00:00
Loaded 28 entries from dependency cache.
ERROR: rpi-basic-image.bb: Unable to determine endianness for architecture 'INVALID'
ERROR: rpi-basic-image.bb: Please add your architecture to siteinfo.bbclass
ERROR: rpi-hwup-image.bb: Unable to determine endianness for architecture 'INVALID'
ERROR: rpi-hwup-image.bb: Please add your architecture to siteinfo.bbclass
ERROR: Failed to parse recipe: rpi-hwup-image.bb
ERROR: vte_0.56.3.bb: Unable to determine endianness for architecture 'INVALID'
ERROR: vte_0.56.3.bb: Please add your architecture to siteinfo.bbclass
I don't understand why core-image-minimal is using such deprecated recipes.
do I need to switch to the master branch?
Forgive me if this is a dumb question...
It seems my MACHINE configuration was wrong. I tried with MACHINE ?= "raspberrypi4-64" instead and everything went fine.
Removing conf resolved issue for me as well.
I'm trying to setup Yocto project in my linux system. I have added two layers which point outside the Yocto poky folder.
I'm following build steps from here:
https://www.yoctoproject.org/docs/2.7/brief-yoctoprojectqs/brief-yoctoprojectqs.html
I am trying to run the following command "bitbake-layers show-recipes 'ara-'*"
I'm getting this error
ERROR: ExpansionError during parsing /home/XXX/YYYYY/codebase/apd-source/meta-openembedded/meta-oe/recipes-support/syslog-ng/syslog-ng_3.6.4.bb
But I'm expecting output something like this:
***Parsing recipes..done.
=== Matching recipes: ===
ara-com-examples:
meta-ara 1.0.0
ara-com-fusion-example:
meta-ara 1.0.0
ara-com-gen:***
.
.
.
.
.
This error indicates bitabake failed to parse the recipe and could be due to syntax error from the recipe. But I have encounter this issue even without any error in my recipes. Honestly the don't know why that happened and that could be some issue with the build environment. Not sure.
In this situation, can you try
1. Remove the build directory and also ssttate cache directory.
2. Execute the setup environment script and rebuild
Try with the above steps and check issue resolved. And before that make sure you don't have any syntax error in the syslog_ng recipe , check do you have any bbappend recieps for syslog_ng in your layer or any other layers and they don't have any syntax errors.
Recently I started with yocto-project to build images for raspberry-pi.
I cloned poky and meta-raspberrypi under a directory named as yocto_project on my ubuntu host. Initiated the build using source oe-init-build-env rpi-build.
The first image I created the rpi-basic-image which was a successful attempt.
Upon booting RPi with the image I got a CLI based interface, but the problem is few commands are missing. Came to know by-default all the packages didn't get combine with image, we need to add it manually for example systemd.
If I run bitbake-layers show-recipes I get long list of all the recipes available for RPi. So I added the text IMAGE_INSTALL_append = " systemd" after reading some documents online to append systemd. After this when I bitbake rpi-basic-image got error as ERROR: Nothing RPOVIDES 'systemd' (but /path_to/rpi-basic-image.bb RDEPENDS on or otherwise requires it)
ERROR: systemd was skipped: 'systemd' not in DISTRO_FEATURES
ERROR: Required build target 'rpi-basic-image' has no buildable providers
Don't have clue, why I get this error. How to resolve it. Also do I have to manually add those packages/recipes using build/local.conf to get all the commands.
Need a good explanation/guidance .
From Selecting an Initialization Manager - Yocto Development Manual:
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
You can set those variables in your local.conf.
For awhile in my Team City build, I am unable to publish my source NuGet packages to symbolsource.org as it responds with 500 Internal Server Error.
[16:02:36][push] Pushing NCode.Composition.DisposableParts 1.0.1 to the symbol server (http://nuget.gw.symbolsource.org/Public/NuGet)...
[16:04:18][push] Failed to process request. 'Internal Server Error'.
[16:04:18][push] The remote server returned an error: (500) Internal Server Error..
[16:04:18][push] Process exited with code 1
I am able to publish my normal packages to NuGet.org just fine. I believe that I have properly configured everything as documented by symbol source.
https://www.symbolsource.org/MyGet/Wiki/Publishing
http://www.symbolsource.org/Public/Metadata/NuGet
https://www.symbolsource.org/Public/Account/Register
Here is my Build Step configuration for NuGet Publish:
Runner Type: NuGet Publish
NuGet.exe: Default 2.8.6
Packages: *.nupkg
API Key: (my personal API key from NuGet.org)
Package Source: (blank)
In my build output directory and artifacts recognized by TeamCity, I do have both of my packages in there:
NCode.Composition.DisposableParts.1.0.1.nupkg
NCode.Composition.DisposableParts.1.0.1.symbols.nupkg
Any assistance would be appreciated!
I think that the problem is with two packages with the same name. Did you try a workaround with another build configuration and snapshot dependency?
I'm using another build configuration with snapshot dependency to build which produces *.nupkg and *.symbol.nupkg. Artifact dependency is set to:
-:*.nupkg => <replace with location>
+:*.symbol.nupkg
The build configuration only publishes *.symbol.nupkg to symbolsource.org.