Yocto build failure -- supposedly due to opkg-4.2 download
Alex G.
Hi,
I'm trying to get started with yocto builds. My builds keep failing trying to build the qemu-x86 image. Here's what I did: 1. I got poky from git://git.yoctoproject.org/poky.git -b dunfell 2. $ source path/to/poky/oe-init-build-env 3. $ time bitbake core-image-minimal I keep getting the following error: ERROR: opkg-1_0.4.2-r0 do_fetch: Fetcher failure for URL: 'http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz';. Unable to fetch URL from any source. The file doesn't seem to be present on the server. I'm stuck. How do I fix this? Alex
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
FLoraVLogs <eripflo@...>
Ok, thanks for the update. Kindly keep me posted.
On Tue., Aug. 4, 2020, 2:05 p.m. Michael Halstead, <mhalstead@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: cannot bring global environment var into a recipe
Rob Prowel
On 2020-08-04 13:11, codusnocturnus via lists.yoctoproject.org wrote:
I think what you need to do is add the environment variable to BB_ENV_WHITELIST or BB_ENV_EXTRAWHITE:Thanks, NightCoder! It worked, once I put it in the right place. must be declared in global shell environment after running oe-init-build-environment export BB_ENV_EXTRAWHITELIST="${BB_ENV_EXTRAWHITELIST} VAR_TO_BRING IN" Unfortunately it's not always obvious to me where a variable is to be declared: some in global shell, sometimes in local.conf, sometimes in bb files... Anyway, fixed! Thanks!
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
Michael Halstead
Remote troubleshooting has stalled. I'm headed to the data center to continue. No ETA yet.
On Tue, Aug 4, 2020 at 9:02 AM FLoraVLogs <eripflo@...> wrote:
--
Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: cannot bring global environment var into a recipe
codusnocturnus
I think what you need to do is add the environment variable to BB_ENV_WHITELIST or BB_ENV_EXTRAWHITE:
toggle quoted messageShow quoted text
https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_WHITELIST Thanks, Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 4, 2020 9:54 AM, Rob Prowel <rprowel@comcast.net> wrote:
I don't want to get into a discussion about why it is a good or bad
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
cannot bring global environment var into a recipe
Rob Prowel
I don't want to get into a discussion about why it is a good or bad idea, but I need to use a global shell variable as follows:
using "sumo"...that's all I can use. $ export PM1_DEVEL_IMAGE=1 or $ PM1_DEVEL_IMAGE=1 bitbake my-image and reference that global var in a kernel bbappend such as SRC_URI += "${@ 'file://rootnfs.cfg' if d.getVar('PM1_DEVEL_IMAGE') else ' '}" to include the required fragment that supports rootnfs. If I define the var right in the bbappend then it works as expected: undefined skips the SRC_URI append, and if defined then it adds my fragment. I need this to work for a var that is defined (or not) in the global work shell, not depend upon the definition being IN a recipe file. I tried using export PM1_DEVEL_IMAGE right in the bbappend, but then as far as the recipe is concerned it's defined and the conditional always succeeds. is d.getVar not the right function? What function behaves the same but uses real shell variables? Suggestions?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Technical Team Minutes, Engineering Sync, for August 4 2020
Trevor Woerner
Yocto Technical Team Minutes, Engineering Sync, for August 4 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to ensure the below is accurate and valid. However, errors sometimes happen. If any errors or omissions are found, please feel free to reply to this email with any corrections. == attendees == Trevor Woerner, Stephen Jolley, Armin Kuster, Richard Purdie, Josef Holzmayr, Joshua Watt, Alejandro H, Steve Sakoman, Bruce Ashfield, (phone-in), Jon Mason, Scott Murray, Denys Dmytriyenko, Matthew Zeng, Philip Balister, Peter Kjellerstedt, Saul Wold, Tim Orling, Ross Burton == notes == - 3.1.2 released - 3.1-m2 in QA - qemumips issues continue on AB - published doc on inclusive language - published doc on future directions - intermittent AB failures, but seems to be going down - lots of unassigned bugs, please pitch in - 3.0.4 (last build of 3.0 series, zeus) probably built sometime next week (if everything stays good) - project tracking metrics are good, probably the best in roughly 18 months - overall project appears healthy and growing == general == RP: relatively quiet week RP: binutils update caused perf issues, Bruce already submitted a patch RP: infrastructure has issues today (some parts are down) Michael is aware RP: inclusive language: agreed on by various groups in the project. please join in. RP: future directions is something we’ve been working on for a while, please take a look RP: i’ve been looking at the sphynx doc update (hi Nico!) RP: Nico has been making great progress. i’d like to make improvements to how doc versions are selected, looking into what sphynx can do for us. i think Nico is about to publish a list of ways to contribute(?) Timo: bug triage: we decided to create a new mailing list for AB failures. any name suggestions? RP: i think it wasn’t AB failures, but QA reports SS: yes RP: with AB1 we realised that what was being emailed out was wrong, with AB2 we never re-enabled/re-implemented it. the problem with an AB failures list was that people started reporting general failures not happening on AB. the idea was to shut down the build failures list and create a QA list RP: we could create it, if there is demand, but i don’t think the demand is there Timo: i’d rather get an email than staring at the AB2 UI RP: having that email sounds great, but we don’t have the code in place or anyone to create/maintain it Timo: fedora project has some stuff that maybe we could use RP: resource issue, patch-test and patchwork are limping along already Timo: fyi, Intel is hoping to take a look (shortly) at patch-test and patchwork (it’s in the queue) RP: thankfully some tools are getting tested since they have test suites, hopefully more tools will get test suites TW: we had a nice OEHH last Wednesday, thanks to all for the opportunity, nice to see people attending Timo: i appreciate it too Crofton: i’ve created an OE calendar with the dates going forward, let me know how that works http://www.openembedded.org/wiki/Calendar TW: time to start planning for next YPDD? Armin: yes, David was on yesterday’s advocacy meeting and said he was taking a lead on it SS: getting ready for next LTS release, please take a look at the current CVE list (we’re getting it down) Armin: what’s different between having Steve send it out rather than the AB? RP: i think generating it automatically causes it to end up in a black hole that nobody looks at. i prefer to have it be more personal SS: it is automatically generated Timo: we also have tool (from WR) RP: that is a good tool (the WR one). i’d like to see SS’s tool released too so we can say “this is what we’re using” Crofton: is YP security list still a thing? (varous): yes, there is a mailing list Crofton: it appears dead, bad for people to sign up then not see any activity Armin: i thought there were hooks Scott: the hooks stopped working a while back, there hasn’t been an email to that list in months. talks to get it working again (MarkH) RP: there was a datacentre move a while back, maybe that’s what happened TW: oecommits emails stopped at end of March, maybe same thing? Scott: or maybe the groups.io move? Scott: yesterday, announcement of the new open software security foundation (which appears to be an LF project) did OE/YP get invited? https://openssf.org/ Crofton: i posted that on twitter, i’ll get back with the replies. chances are we could use their help and they could use ours RP: it’s the first i’ve heard of this, i’ve discussed with LF to have better communication between LF members, especially for new foundations, we weren’t notified but we should try to reach out Timo: is there any regular LF-wide meeting within LF? RP: no Crofton: closest would be the Leadership Conference RP: coordination between all the LF projects is hard and doesn’t exist (yet, at least not to the degree that maybe it could) Timo: fop is a “you should have this installed if you want to generate the docs” Timo: do we know how some of our diagrams were generated? do we have the “sources”? RP: i’m guessing not. i looked at some of them recently and noticed some tweaking was needed and was wondering how we’d do that Timo: last week Thea had some ideas for solving some of our resourcing issues. e.g. looking at stats of past contributors can help find resources Armin: i was at yesterday’s advocacy meeting, and this wasn’t a big topic of discussion Scott: is foundries.io a member now? RP: yes Scott: needs to be added to website RP: odd, they are a silver member now Bruce: hoping to go with 5.8 kernel (and related libc headers) for gatesgarth. things are looking good, lots of pain (strace!) but coming along well
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
FLoraVLogs <eripflo@...>
Is there any ETA on this? Regards, Ripu
On Tue, Aug 4, 2020 at 11:30 AM Josef Holzmayr-Khosh Amoz <jester@...> wrote: https://twitter.com/TheYoctoJester/status/1290569609100308480
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
Josef Holzmayr
https://twitter.com/TheYoctoJester/status/1290569609100308480
toggle quoted messageShow quoted text
Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs <eripflo@gmail.com>:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: do_package() failing due to "no attribute"
Quentin Schulz
Hi Itai,
On Tue, Aug 04, 2020 at 03:11:55PM +0000, Itai Kleiman via lists.yoctoproject.org wrote: export SDKTARGETSYSROOT = "${TMPDIR}/sysroots/x86_64-linux/usr/bin/mips64-poky-linux/"SDKTARGETSYSROOT = "${STAGING_BINDIR_NATIVE}/mips64-poky-linux" do_configure() {--sysroot=${STAGING_DIR_TARGET} \ -C--build=${BUILD_SYS} \--sysroot=${STAGING_DIR_TARGET} --sysroot=${STAGING_DIR_TARGET} -L/${STAGING_LIBDIR} At least for the path, haven't checked anything else. Also, most of those arguments should be passed by Yocto already to your recipe's makefile. Quentin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
do_package() failing due to "no attribute"
Itai Kleiman
Hi,
I wrote a recipe (.bb file) for xerces-c 2.8 version.
I run the command 'bitbake xerces-c -vvv' in order to build the package and I get the following error:
ERROR: xerces-c-2.8.0-r2 do_package: Error executing a python function in exec_python_func() autogenerated:
the recipe:
DESCRIPTION = "Xerces-c is a validating xml parser written in C++" I'm using yocto-2.2.4.
Any idea what is the problem?
Thank you,
Itai
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Status WW31'20
Stephen Jolley
Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 build date 2020/8/31
Next Team Meetings:
Key Status/Updates:
Help with any of these would be much appreciated.
YP 3.2 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
FLoraVLogs <eripflo@...>
I am seeing the following error: Gateway TimeoutServer error - server 198.145.29.63 is unreachable at this moment. Kindly help. Regards, Ripu
On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs <eripflo@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto host not found
FLoraVLogs <eripflo@...>
Hi, It seems like Yocto is down again. Could you please help solve this? Regards, Ripu
On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs <eripflo@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Cannot fetch sources, downloads.yoctoproject.org is down
Quentin Schulz
Hi Lluis,
On Tue, Aug 04, 2020 at 02:32:05AM -0700, Lluis Campos via lists.yoctoproject.org wrote: Hello,It's known: https://twitter.com/yoctoproject/status/1290570140468285441?s=20 Thanks for the report anyway :) Quentin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cannot fetch sources, downloads.yoctoproject.org is down
Lluis Campos
Hello,
Since two hours ago, I am not able to build anything due to downloads.yoctoproject.org being down. Do you have any more info on what is going on? I am getting the following error: --2020-08-04 07:55:45-- http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.29.63 Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection timed out. Retrying. --2020-08-04 07:56:16-- (try: 2) http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection timed out. Giving up. ERROR: opkg-native-1_0.4.2-r0 do_fetch: Fetcher failure for URL: 'http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz'. Unable to fetch URL from any source. Thanks! -- Lluís M- Campos Martínez
Northern.tech ++ Mender.io
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Quentin Schulz
Hi Sheng Leong,
On Tue, Aug 04, 2020 at 12:18:26AM -0700, Soi, Sheng Leong wrote: Hi,Start from a core-image-minimal and add packages manually. Only the packages that are specified to be installed explicitly in your image recipe and the packages specified in RDEPENDS and RRECOMMENDS of those packages will be installed in the recipe. Some packages are also pulled because of configuration files (machine, distro or local.conf). If there are RRECOMMENDS you don't want, you can use BAD_RECOMMENDATIONS in your image recipe to ask the image to not pull them in. If it's an RDEPENDS that you don't want, maybe it's pulled because of a selected PACKAGECONFIG that you don't need, in that case create a bbappend for that recipe and set PACKAGECONFIG accordingly. If that still does not do it, you'll have to dig deeper into what can be removed from RDEPENDS and for which reason (is it a mistake? is is safe in one specific configuration). The way to know which package is pulling which package is to use `-g` as argument of bitbake. DO not attempt to create a scheme/drawing/image from the dot files, they are too big for dot to handle properly (takes hours and the result is unusable). "recipeA:do_foo" => "recipeB:do_bar" means that do_foo task from recipeA depends on do_bar from recipeB. Hope that helps, if not, please be a bit more explicit with what you want to do, what's happening and what you're expecting, so we can help you the best way we can. Cheers, Quentin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Soi, Sheng Leong
Hi,
Does anyone here know how to disable specific default recipe (e.g. CUPS and HPLIP) to be included in Yocto image? Thanks Sheng Leong
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors
Robert Joslyn
On Tue, 2020-07-28 at 08:30 +0200, Jeff Ithier wrote:
Hi Robert,My builds normally use ipk, but I tried rpm on one and did not see this error when building icedtea7-native. Sorry! Thanks, Robert Cheers
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
M+ & H bugs with Milestone Movements WW31
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|