Hello All,
I am trying to include the cron to my yocto (release Morty) image. In the image
recipe I have added IMAGE_INSTALL_append = " cronie". This created the crontab
and cron.d directory in /etc/. Also other directories like /etc/cron.daily/,
/etc/cron.hourly/, are created. But when I
You need to send your public ssh key to Michael (cc) and explain what
access should be granted with that (which repo, which branch(es)).
In this case,
https://git.yoctoproject.org/meta-lts-mixins/
kirkstone/go
Alex
On Fri, 31 Mar 2023 at 18:15, Jose Quaresma wrote:
>
> Hi Alex,
>
> I don't
Hi
On 31.03.23 at 12:35, MOHAMMED HASSAN wrote:
Can you help me to compile for dynamically linked executable file in
yocto dunfell?
Thanks
For a dynamically linked executable you should definitely build it from
source.
There is no shortcut here. You should take the time to read the Yocto
Signed-off-by: Jose Quaresma
---
README | 1 +
1 file changed, 1 insertion(+)
diff --git a/README b/README
index d33c576..5a24ec2 100644
--- a/README
+++ b/README
@@ -20,3 +20,4 @@ The patches can be backport from openembedded-core with:
Maintainers:
Alexander Kanavin
+Jose Quaresma
--
Signed-off-by: Jose Quaresma
---
README | 5 +
1 file changed, 5 insertions(+)
diff --git a/README b/README
index b2fa46b..d33c576 100644
--- a/README
+++ b/README
@@ -13,5 +13,10 @@ or local.conf:
GOVERSION = "1.20%"
+The patches can be backport from openembedded-core with:
+
+ git -C
Since go 1.20 some packages fails to link [1][2]
and only build staticaly with GO_LINKSHARED = ""
[1] https://lists.yoctoproject.org/g/meta-virtualization/topic/97182310
[2] https://github.com/golang/go/issues/58966
Signed-off-by: Jose Quaresma
---
recipes-devtools/go-1.20/go-1.20.1.inc
From: Peter Marko
All golang vulnerabilities are reported under product 'go'.
By default there is no vulnerability reported for images with
golang components because none of used golang packages
have correct CVE product set:
* go-binary-native
* go-runtime
* go-cross-*
Signed-off-by: Peter
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
Signed-off-by: Jose Quaresma
---
recipes-devtools/go-1.20/{go-1.20.inc => go-1.20.1.inc} | 2 +-
...{go-binary-native_1.20.bb => go-binary-native_1.20.1.bb} | 6 +++---
...o-cross-canadian_1.20.bb
From: Alexander Kanavin
The recipe was building native go against build host headers and libraries,
and then installing it as a nativesdk item, which is entirely incorrect. This
has
been working by coincidence (go generally uses C and C libraries lightly)
but with go 1.20 this turned into hard
From: Chen Qi
The GO_WORKDIR is used only in go-mod.bbclass. As this recipe does
not inherit go-mod.bbclass, this variable is useless here.
This go-helloworld recipe was made to inherit go-mod.bbclass and build
in module-aware mode. However, it was found that we need to build go
recipes in
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
Signed-off-by: Jose Quaresma
---
recipes-extended/go-examples/go-helloworld_0.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/go-examples/go-helloworld_0.1.bb
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
Signed-off-by: Jose Quaresma
---
recipes-extended/go-examples/go-helloworld_0.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/go-examples/go-helloworld_0.1.bb
Signed-off-by: Jose Quaresma
---
README | 12 +++-
conf/layer.conf | 4 ++--
2 files changed, 5 insertions(+), 11 deletions(-)
diff --git a/README b/README
index 5b22b72..b2fa46b 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
"Mixin" layer for adding latest Go toolchain
From: Alexander Kanavin
This allows a quick smoke test for whether go toolchain produces
working executables.
Link:
https://git.yoctoproject.org/poky/tree/meta/recipes-extended/go-examples?id=278cb0fc0725fbfdcafd3b3afcfb7c7c6a4eee14
(copy from external source:
git:
Signed-off-by: Jose Quaresma
---
.../go-examples/go-helloworld_0.1.bb | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename {recipes-devtools => recipes-extended}/go-examples/go-helloworld_0.1.bb
(100%)
diff --git
From: Alexander Kanavin
Reviewed-by: Martin Kaistra
Signed-off-by: Alexander Kanavin
Signed-off-by: Jose Quaresma
---
COPYING.MIT | 17 +
README | 23 +++
conf/layer.conf | 19 +++
3 files changed, 59 insertions(+)
create mode
Hi Alex,
I don't have any account/keys that allow me to push directly
git.yoctoproject.org
maybe I need to setup my keys somewhere like with poky-contrib [1]
I will send all the patches to the yocto mailing list as recommended.
[1] https://wiki.yoctoproject.org/wiki/Poky_Contributions
Jose
Bruce Ashfield escreveu no dia quinta,
30/03/2023 à(s) 16:14:
> On Thu, Mar 30, 2023 at 10:41 AM Jose Quaresma
> wrote:
> >
> > Hi,
> >
> > I already did some tests using the meta-virt master branch with
> > the oe-core kirkstone and this version of the meta-lts-mixins.
> > Our stack on
Okay, it worked fine.
Thanks again
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59567): https://lists.yoctoproject.org/g/yocto/message/59567
Mute This Topic: https://lists.yoctoproject.org/mt/97886388/21656
Group Owner:
Can you help me to compile for dynamically linked executable file in yocto
dunfell?
Thanks
On Fri, Mar 31, 2023 at 3:20 PM Michael Opdenacker <
michael.opdenac...@bootlin.com> wrote:
>
> On 31.03.23 at 11:42, MOHAMMED HASSAN wrote:
> > If so, you could write a recipe to integrate the binary into
On Fri, Mar 31, 2023 at 03:01 AM, MOHAMMED HASSAN wrote:
>
>
>>
>>> Will it be okay for me to refer the above link for my specific
>>> case?I'd say yes, write a similar recipe for your binary.
>>>
>>> Its a .exe binary file. Will it work?
>>
>>
>> Not if that's a Windows executable (you can
>
>
>> Will it be okay for me to refer the above link for my specific
>> case?I'd say yes, write a similar recipe for your binary.
>>
>> Its a .exe binary file. Will it work?
>
>
> Not if that's a Windows executable (you can check with the "file"
> command). Just try to run it on your target
On 31.03.23 at 11:42, MOHAMMED HASSAN wrote:
If so, you could write a recipe to integrate the binary into your
root
filesystem, as it's possible to do with pre-compiled libraries :
https://docs.yoctoproject.org/dev-manual/common-tasks.html#working-with-pre-built-libraries.
Caution, in this
If so, you could write a recipe to integrate the binary into your
root
filesystem, as it's possible to do with pre-compiled libraries :
https://docs.yoctoproject.org/dev-manual/common-tasks.html#working-with-pre-built-libraries.
Caution, in this document, the new override syntax (with ":"
instead
On 31.03.23 at 09:36, MOHAMMED HASSAN wrote:
Can you please guide me as to what I need to load this binary
executable file is my generated image file.
Is this binary statically linked? Otherwise, you have no guarantee
that
it will run on your root filesystem.
It
>
>
>> Can you please guide me as to what I need to load this binary
>> executable file is my generated image file.
>
>
> Is this binary statically linked? Otherwise, you have no guarantee that
> it will run on your root filesystem.
It is statically linked file written using c language.
>
>
Hi Hassan
On 31.03.23 at 06:34, MOHAMMED HASSAN wrote:
Hi guys,
I am new to yocto needed your help.
I have an executable binary file that is probably compiled using the
gcc compiler. I am using yocto dunfell for my project my build_sys is
"x86_64-linux" , my target_sys is
27 matches
Mail list logo
