I am seeing an error when I attempt to apply a patch, and could use some
clarification or way to resolve...
Am doing something wrong in patch creation ?
What is meant by : "Patch console.patch does not apply (enforce with -f)" ?
How can I best resolve this issue ?
I edited a file in the recipe
Any hints or ideas on what I might be doing wrong would be appreciated…
From: yocto@lists.yoctoproject.org On Behalf Of
Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Monday, September 19, 2022 2:22 PM
To: yocto@lists.yoctoproject.org
Subject: [yocto] #yocto #dunfell
External Email
lists.yoctoproject.org
Date: Tuesday, 20 September 2022 at 16:05
To: Monsees, Steven C (US) ,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell
Any hints or ideas on what I might be doing wrong would be appreciated…
From: yocto@lists.yoctoproject.org On Behalf Of
Monsees
Thanks... will give it a try.
From: Ross Burton
Sent: Tuesday, September 20, 2022 11:38 AM
To: Monsees, Steven C (US) ;
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please
there another release I
should be using ?
(2)Is there something I need to pre-configure for these builds to run
properly ?
(3)How might I resolve this issue ?
06:57 smonsees@yix490016
/disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunfell_Min>runqemu
qemux86-64
runq
Hello,
with the upgrade from Yocto Zeus → Dunfell, we observe lots of messages when
building our product which seem heavy to be understood or to debug.
Actually, it's the failure of the "do_package" task of a proprietary module
written in C with following message:
ERROR: eds-1.0-r0 do_pack
Hello,
thanks for the reply and the useful hints concerning our questions!
After a debug session, it came out, that the *.a archive doesn't contain only
*.o files, but also one *.c file.
That was missed during the first analysis.
Interestingly enough, the error came out only with the Dunfell Up
sing ?
>
> (2)Is there something I need to pre-configure for these builds to run
> properly ?
>
> (3)How might I resolve this issue ?
>
>
>
> 06:57 smonsees@yix490016
> /disk0/scratch/smonsees/yocto/yocto-dunfell/poky-dunfell-23.0.17/dunfell_Min>
, 2022 7:23 AM
To: Monsees, Steven C (US)
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell #qemux86-64
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to
> To: Monsees, Steven C (US)
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto #dunfell #qemux86-64
>
> External Email Alert
>
> This email has been sent from an account outside of the BAE Systems network.
>
> Please treat the email with caution, especially if you are r
One final question, does this issue exist in kirkstone-4.0.2 ?
Thanks,
Steve
-Original Message-
From: Alexander Kanavin
Sent: Wednesday, August 31, 2022 7:42 AM
To: Monsees, Steven C (US)
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell #qemux86-64
External
final question, does this issue exist in kirkstone-4.0.2 ?
>
> Thanks,
> Steve
>
> -Original Message-
> From: Alexander Kanavin
> Sent: Wednesday, August 31, 2022 7:42 AM
> To: Monsees, Steven C (US)
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #y
Wednesday, August 31, 2022 7:42 AM
> To: Monsees, Steven C (US)
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto #dunfell #qemux86-64
>
> External Email Alert
>
> This email has been sent from an account outside of the BAE Systems network.
>
> Please treat th
o@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto #dunfell #qemux86-64
>
> External Email Alert
>
> This email has been sent from an account outside of the BAE Systems network.
>
> Please treat the email with caution, especially if you are requested
> to click on
: [yocto] #yocto #dunfell #qemux86-64
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click
on a link, decrypt/open an attachment, or enable macros. For further
information
Thank you, and I am looking at kirkstone...
-Original Message-
From: Khem Raj
Sent: Wednesday, August 31, 2022 12:38 PM
To: Monsees, Steven C (US) ; Alexander Kanavin
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #dunfell #qemux86-64
On 8/31/22 4:36 AM, Monsees, Steven
Hi, folks.
I'm getting the error below in several packages. Some of then I could fix when
the recipe "do_intall"
has commands like:
"cp -a "
How can I solve this error when the recipe has no "cp" ? What else can cause
this issue ?
Thanks in advance...
WARNING: firefox-38.3.0esr-r0 do_pack
On 7/21/20 3:45 AM, Jan Hannig wrote:
Hello,
with the upgrade from Yocto Zeus → Dunfell, we observe lots of messages
when building our product which seem heavy to be understood or to debug.
Actually, it's the failure of the "do_package" task of a proprietary
module written in C with follow
Hi, all
I used recipetool to create the recipe for NPM packages
If the npm package has dependence(s) it works great.
But if not, the error below happens.
I just add a fake dependence in npm-shrinkwrap.json then it works
# cat google-protobuf/npm-shrinkwrap.json
{
"name": "google-protobuf",
Using dunfell 3.1.8
Will post this inquiry while doing my own investigation. When outputting to the
debug console that involves standard input(ex. busctl, systemctl status), the
output seems misaligned and dirty.
But I noticed this can be easily fixed by adding to the "tools-sdk" to the
EXTRA_I
Hi Edson,
You're right. I have seen seen this too. I have already created a bug
to track this issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13901
For now, as a workaround, you can just delete the npmsw:// line in
the generated recipe (and the shrinkwrap file).
Best Regards,
Jean-Mari
Hello,
I'm actually migrating a yocto project zeus version to dunfell LTS to build my
imx6 Linux system on this LTS release.
Almost all works fine except the following message I try to understand when I
try to compile the image:
--
Hi,
On Tue, Apr 20, 2021 at 03:24:25AM -0700, anthony.march...@navocap.com wrote:
> Hello,
> I'm actually migrating a yocto project zeus version to dunfell LTS to build
> my imx6 Linux system on this LTS release.
>
> Almost all works fine except the following message I try to understand when I
23 matches
Mail list logo
