[yocto] How to compile binary executable files

2023-03-30 Thread MOHAMMED HASSAN
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 "aarch64-poky-linux".

Can you please guide me as to what I need to load this binary executable
file is my generated image file.

Thanks and Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59557): https://lists.yoctoproject.org/g/yocto/message/59557
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] How to compile binary executable files

2023-03-31 Thread MOHAMMED HASSAN
> 
> 
>> 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.

> 
> 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 of
> "_") is shown, it doesn't apply to Dunfell.
> 
> I hope this helps
> Cheers
> Michael.
> 
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Will it be okay for me to refer the above link for my specific case?

Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59560): https://lists.yoctoproject.org/g/yocto/message/59560
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] How to compile binary executable files

2023-03-31 Thread MOHAMMED HASSAN
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 of
"_") is shown, it doesn't apply to Dunfell.

> 
> 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?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59562): https://lists.yoctoproject.org/g/yocto/message/59562
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] How to compile binary executable files

2023-03-31 Thread MOHAMMED HASSAN
> 
> 
>> 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 system a

Sorry, Ive made some errors here. I just run file command to check, and it 
seems I was misled by my team into believing it was a statically linked binary.
Ive attached a screenshot for your reference about the type of file it is.
Maybe that would help clear out the mess Ive made.

Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59564): https://lists.yoctoproject.org/g/yocto/message/59564
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] How to compile binary executable files

2023-03-31 Thread MOHAMMED HASSAN
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 check with the "file"
>> command). Just try to run it on your target system a
> 
> Sorry, Ive made some errors here. I just run file command to check, and it
> seems I was misled by my team into believing it was a statically linked
> binary.
> Ive attached a screenshot for your reference about the type of file it is.
> 
> Maybe that would help clear out the mess Ive made.
> 
> Thanks and regards,
> Hassan
> 
> 
> 
> 

I think the pictures are not clear so you can refer the attachements.
Ive also copied and pasted what in the attachments here.
*$: file Z3GatewayHostm*
*Z3GatewayHostm: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 
3.7.0, BuildID[sha1]=5eef6bf3e27434a4e20b7fdd50b3c13f929366ec, with debug_info, 
not stripped*

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59565): https://lists.yoctoproject.org/g/yocto/message/59565
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] How to compile binary executable files

2023-03-31 Thread MOHAMMED HASSAN
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 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 of
> > "_") is shown, it doesn't apply to Dunfell.
> >
> > 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 system a
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59566): https://lists.yoctoproject.org/g/yocto/message/59566
Mute This Topic: https://lists.yoctoproject.org/mt/97967124/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Unable to add nodejs and npm-related packages

2023-04-02 Thread MOHAMMED HASSAN
Hi guys,
I am trying to add nodejs and npm to my image file but get the below error
message.

ERROR: core-image-minimal-1.0-r0 do_image_cpio: The initramfs size
256914(K) exceeds INITRAMFS_MAXSIZE: 131072(K)
ERROR: core-image-minimal-1.0-r0 do_image_cpio: You can set
INITRAMFS_MAXSIZE a larger value. Usually, it should
ERROR: core-image-minimal-1.0-r0 do_image_cpio: be less than 1/2 of ram
size, or you may fail to boot it.

ERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_cpio.106257
ERROR: Task
(/home/mohan/amlogic/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_cpio)
failed with exit code '1'

I am new to yocto and am not able to solve this issue. Can you guys please
help.

Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59593): https://lists.yoctoproject.org/g/yocto/message/59593
Mute This Topic: https://lists.yoctoproject.org/mt/98029138/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Unable to solve the initramfs issues

2023-04-05 Thread MOHAMMED HASSAN
Hi guys,
I really need your help in solving this issue.
I want to add nodejs to my image and added the line *IMAGE_INSTALL_append
+= " nodejs "*
to my *local.conf* file, but got the error message






*ERROR: core-image-minimal-1.0-r0 do_image_cpio: The initramfs size
171613(K) exceeds INITRAMFS_MAXSIZE: 131072(K)ERROR:
core-image-minimal-1.0-r0 do_image_cpio: You can set INITRAMFS_MAXSIZE a
larger value. Usually, it shouldERROR: core-image-minimal-1.0-r0
do_image_cpio: be less than 1/2 of ram size, or you may fail to boot
it.ERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_cpio.211614ERROR:
Task
(/home/mohan/amlogic/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_cpio)
failed with exit code '1'*

I tried to solve this by adding the line
*INITRAMFS_MAXSIZE = "524288000"  *to my local.conf file and it compiled
successfully. But the OS flashing failed.
I have been stuck with this issue for a very long time and need your
support in this issue. I have attached all the log files or necessary files
for you to refer.

Thanks and regards,
Hassan


log_do_compile
Description: Binary data


core-image-minimal.bb
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59623): https://lists.yoctoproject.org/g/yocto/message/59623
Mute This Topic: https://lists.yoctoproject.org/mt/98099160/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Compilation of z3gateway

2023-04-06 Thread MOHAMMED HASSAN
Hi guys,
I am trying to compile and build an executable for my image file. but
facing issues with the compilation. I tried debugging for the whole day but
no success.
I tried by following this mechanism which I know is not for yocto but it's
somewhat similar.
I got the below error.










*ERROR: zigbee-0.1-r0 do_compile: Execution of
'/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/run.do_compile.333968'
failed with exit code 2ERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/log.do_compile.333968Log
data follows:| DEBUG: Executing shell function do_compile| make: *** No
targets specified and no makefile found.  Stop.| WARNING: exit code 2 from
a shell command.| ERROR: Execution of
'/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/run.do_compile.333968'
failed with exit code 2ERROR: Task
(/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_compile)
failed with exit code '1'NOTE: Tasks Summary: Attempted 553 tasks of which
545 didn't need to be rerun and 1 failed.NOTE: Writing buildhistoryNOTE:
Writing buildhistory took: 5 seconds*

I have attached my makefile and my zigbee_0.1.bb file for your reference.
What changes do I need to make for a successful build? The make command
works fine in its current directory, but throws the above error in the
do_compile block.
My kernel toolchain:aarch64-poky-linux-gcc (64-bit)
My application toolchain(32bit)- arm-pokymllib32-linux-gnueabi-gcc
My application toolchain(64bit)- aarch64-poky-linux-gcc

Thanks and Regards,
Hassan


Makefile
Description: Binary data


zigbee_0.1.bb
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59630): https://lists.yoctoproject.org/g/yocto/message/59630
Mute This Topic: https://lists.yoctoproject.org/mt/98104663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Compilation of z3gateway

2023-04-09 Thread MOHAMMED HASSAN
Hi guys,
please support me. I am not able to get through this issue. I am new to yocto 
so facing such issues.

Thanks and Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59651): https://lists.yoctoproject.org/g/yocto/message/59651
Mute This Topic: https://lists.yoctoproject.org/mt/98104663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Missing .o files.

2023-04-10 Thread MOHAMMED HASSAN
Hi guys,
Its my first time using yocto so I dont have much experience on this. I am
trying to cerate a .exe file for my target hardware. I am calling the
makefile using oe_runmake command but there are some missing .o files for
which I have no solution. If you  have any idea where I can find the
related .c files for this (I am still a beginner at work) then I would be
grateful to you. There error is shown below

ute-size.o build/attribute-storage.o build/attribute-table.o
build/client-api.o build/message.o build/multi-network.o build/print.o
build/print-formatter.o build/process-cluster-message.o
build/process-global-message.o build/service-discovery-common.o
build/time-util.o build/util.o build/af-main-host.o
build/service-discovery-host.o  -lreadline -lncurses  -lm -lpthread -o
./build/exe/hostforEdge3
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find Scrt1.o: No such file or directory
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find crti.o: No such file or directory
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find crtbeginS.o: No such file or directory
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lreadline
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lncurses
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lm
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lpthread
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lgcc
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lgcc_s
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lc
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lgcc
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find -lgcc_s
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find crtendS.o: No such file or directory
|
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
cannot find crtn.o: No such file or directory
| collect2: error: ld returned 1 exit status
| make: *** [Makefile:411: build/exe/hostforEdge3] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.


Thanks
Hassan


do_compile
Description: Binary data


makefile
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59665): https://lists.yoctoproject.org/g/yocto/message/59665
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing .o files.

2023-04-10 Thread MOHAMMED HASSAN
Hi Khem,
Thanks for your reply.
I tried the changes you wanted me to make and this is the error I got.

ERROR: zigbee-0.1-r0 do_compile: oe_runmake failed
ERROR: zigbee-0.1-r0 do_compile: Execution of 
'/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/run.do_compile.171358'
 failed with exit code 1
ERROR: Logfile of failure stored in: 
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/log.do_compile.171358
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 CC=aarch64-poky-linux-gcc  -march=armv8-a+crc 
-fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security 
-Werror=format-security 
--sysroot=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot
 RANLIB=aarch64-poky-linux-gcc-ranlib AR=aarch64-poky-linux-gcc-ar CFLAGS= -O2 
-pipe -g -feliminate-unused-debug-types 
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0=/usr/src/debug/zigbee/0.1-r0
                     
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot=
                     
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot-native=
                      
-I/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0 
BUILDDIR=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0 all
| aarch64-poky-linux-gcc  -march=armv8-a+crc -fstack-protector-strong  
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
--sysroot=/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot
 build/znet-bookkeeping.o build/call-command-handler.o build/callback-stub.o 
build/stack-handler-stub.o build/znet-cli.o build/hostforEdge3_callbacks.o 
build/library.o build/command-interpreter2.o build/zigbee-device-common.o 
build/zigbee-device-host.o build/event-control.o build/led-stub.o 
build/mem-util.o build/antenna-stub.o build/buzzer-stub.o build/address-table.o 
build/address-table-cli.o build/basic.o build/color-control-server.o 
build/concentrator-support.o build/concentrator-support-cli.o 
build/counters-cli.o build/counters-ota-host.o build/counters-host.o 
build/ez-mode.o build/ez-mode-cli.o build/ezsp-callbacks.o 
build/ezsp-enum-decode.o build/ezsp-frame-utilities.o build/ezsp.o 
build/ezsp-host-io.o build/ezsp-host-queues.o build/ezsp-host-ui.o 
build/serial-interface-uart.o build/ash-host-ui.o build/ash-host.o 
build/ash-common.o build/file-descriptor-dispatch.o build/gateway-support.o 
build/backchannel-support.o build/gateway-support-cli.o 
build/green-power-client.o build/green-power-client-cli.o 
build/green-power-common.o build/gp-util.o build/heartbeat.o 
build/ias-zone-client.o build/ias-zone-client-cli.o build/identify.o 
build/identify-cli.o build/identify-feedback.o build/level-control.o 
build/linked-list.o build/aes.o build/asn1parse.o build/asn1write.o 
build/base64.o build/bignum.o build/ccm.o build/chacha20.o build/chachapoly.o 
build/cipher.o build/cipher_wrap.o build/cmac.o build/ctr_drbg.o build/des.o 
build/ecdh.o build/ecdsa.o build/ecjpake.o build/ecp.o build/ecp_curves.o 
build/entropy.o build/error.o build/gcm.o build/md.o build/md5.o build/oid.o 
build/pem.o build/pk.o build/pk_wrap.o build/pkparse.o build/platform_util.o 
build/poly1305.o build/psa_crypto.o build/psa_crypto_cipher.o 
build/psa_crypto_client.o build/psa_crypto_driver_wrappers.o 
build/psa_crypto_ecp.o build/psa_crypto_hash.o build/psa_crypto_mac.o 
build/psa_crypto_slot_management.o build/psa_crypto_storage.o build/rsa.o 
build/rsa_internal.o build/sha1.o build/sha256.o build/sha512.o 
build/ssl_cache.o build/ssl_ciphersuites.o build/ssl_cli.o build/ssl_cookie.o 
build/ssl_msg.o build/ssl_srv.o build/ssl_ticket.o build/ssl_tls.o 
build/threading.o build/x509.o build/x509_create.o build/x509_crl.o 
build/x509_crt.o build/x509_csr.o build/x509write_crt.o build/x509write_csr.o 
build/ncp-configuration.o build/network-creator.o build/network-creator-cli.o 
build/network-creator-security.o build/network-creator-security-cli.o 
build/network-steering.o build/network-steering-cli.o 
build/network-steering-v2.o build/network-steering-host.o build/on-off.o 
build/ota-common.o build/ota-server.o build/ota-server-page-request.o 
build/ota-server-cli.o build/ota-server-dynamic-block-period.o 
build/ota-server-policy.o build/ota-storage-common.o 
build/ota-storage-common-cli.o build/ota-storage-linux.o 
build/poll-control-client.o build/poll-control-client-cli.o build/reporting.o 
build/reporting-cli.o build/reporting-default-configuration.o 
build/scan-dispatch.o build/secure-ezsp-stub.o build/simple-main.o 
build/simple-metering-client.o build/simple-metering-client-cli.o 
build/stack-diagnostics.o build/test-harness.o build/read-write-attributes.o 
build/test-harness-host.o build/time-server.o 
build/trust-center-nwk-key-update-broadcast.o 
build/trust-ce

Re: [yocto] Missing .o files.

2023-04-10 Thread MOHAMMED HASSAN
On Mon, Apr 10, 2023 at 10:45 PM, Khem Raj wrote:

> 
> you need to add
> 
> DEPENDS += "readline ncurses"
> 
> to your recipe.
> 
> 

Hi Khem,
Thanks for your reply. I didnt get any more errors and bitbake zigbee was a 
success.
The issue is in my executable is saved in 
/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe
 folder and not in the  
/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0 folder. I thought of 
making changes in the makefile but not sure with the commands I need to write. 
Can you please help.

Thanks and Reagrds,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59670): https://lists.yoctoproject.org/g/yocto/message/59670
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing .o files.

2023-04-11 Thread MOHAMMED HASSAN
Hi Khem,
Thanks for all your support.
I added the following lines in my recipe file.
do_install() {
install -d ${D}${bindir}
# install -m 0755 
/home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe
 ${D}
install -m 0755 
/home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
 ${D}${bindir}
# chmod 0755 
/home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
# cp 
/home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
 ${D}${bindir}
}

bitbake zigbee works fine but bitbake lib32-amlogic-yocto returns the error 
message.

ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in subprocesses:
Command '['arm-pokymllib32-linux-gnueabi-objcopy', '--only-keep-debug', 
'/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3',
 
'/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/.debug/hostforEdge3']'
 returned non-zero exit status 1.
Subprocess output:arm-pokymllib32-linux-gnueabi-objcopy: 
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3:
 file format not recognized

ERROR: Logfile of failure stored in: 
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/temp/log.do_package.246282
ERROR: Task 
(virtual:multilib:lib32:/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_package)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 5830 tasks of which 5825 didn't need to be rerun 
and 1 failed.

Is it because of the compiler in the makefile?
Is it possible to bypass this error.

Please guide.
Thanks and Regards,
Hassan


log.do_package
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59672): https://lists.yoctoproject.org/g/yocto/message/59672
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing .o files.

2023-04-11 Thread MOHAMMED HASSAN
Hi khem,
If possible can check the makefile once and guide me.

On Tue, 11 Apr 2023 at 12:50 PM, Khem Raj  wrote:

> On Tue, Apr 11, 2023 at 12:13 AM MOHAMMED HASSAN
>  wrote:
> >
> > Hi Khem,
> > Thanks for all your support.
> > I added the following lines in my recipe file.
> > do_install() {
> > install -d ${D}${bindir}
> > # install -m 0755
> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe
> ${D}
> > install -m 0755
> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
> ${D}${bindir}
>
> > # chmod 0755
> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
> > # cp
> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
> ${D}${bindir}
>
>
> > }
> >
> > bitbake zigbee works fine but bitbake lib32-amlogic-yocto returns the
> error message.
> >
> > ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in
> subprocesses:
> > Command '['arm-pokymllib32-linux-gnueabi-objcopy', '--only-keep-debug',
> '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3',
> '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/.debug/hostforEdge3']'
> returned non-zero exit status 1.
> > Subprocess output:arm-pokymllib32-linux-gnueabi-objcopy:
> /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3:
> file format not recognized
> >
> > ERROR: Logfile of failure stored in:
> /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/temp/log.do_package.246282
> > ERROR: Task
> (virtual:multilib:lib32:/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_package)
> failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 5830 tasks of which 5825 didn't need to
> be rerun and 1 failed.
> >
> > Is it because of the compiler in the makefile?
>
> you need to build for 32bit as well. I think you are building these
> binaries outside yocto and then weirdly mixing the install. So perhaps
> that should be fixed first maybe.
>
> > Is it possible to bypass this error.
> >
> > Please guide.
> > Thanks and Regards,
> > Hassan
> >
> >
> > 
> >
> thats
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59674): https://lists.yoctoproject.org/g/yocto/message/59674
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing .o files.

2023-04-11 Thread MOHAMMED HASSAN
Hi khem,
I didn’t understand your last reply. Please guide.
On Tue, 11 Apr 2023 at 1:46 PM, MOHAMMED HASSAN via lists.yoctoproject.org
 wrote:

> Hi khem,
> If possible can check the makefile once and guide me.
>
> On Tue, 11 Apr 2023 at 12:50 PM, Khem Raj  wrote:
>
>> On Tue, Apr 11, 2023 at 12:13 AM MOHAMMED HASSAN
>>  wrote:
>> >
>> > Hi Khem,
>> > Thanks for all your support.
>> > I added the following lines in my recipe file.
>> > do_install() {
>> > install -d ${D}${bindir}
>> > # install -m 0755
>> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe
>> ${D}
>> > install -m 0755
>> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
>> ${D}${bindir}
>>
>> > # chmod 0755
>> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
>> > # cp
>> /home/mohan/amlogic/meta-c/recipes-example/zigbee/files/gecko_sdk_suite/v3.2/build/Z3GatewayHostm/build/exe/hostforEdge3
>> ${D}${bindir}
>>
>>
>> > }
>> >
>> > bitbake zigbee works fine but bitbake lib32-amlogic-yocto returns the
>> error message.
>> >
>> > ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in
>> subprocesses:
>> > Command '['arm-pokymllib32-linux-gnueabi-objcopy', '--only-keep-debug',
>> '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3',
>> '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/.debug/hostforEdge3']'
>> returned non-zero exit status 1.
>> > Subprocess output:arm-pokymllib32-linux-gnueabi-objcopy:
>> /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3:
>> file format not recognized
>> >
>> > ERROR: Logfile of failure stored in:
>> /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/temp/log.do_package.246282
>> > ERROR: Task
>> (virtual:multilib:lib32:/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_package)
>> failed with exit code '1'
>> > NOTE: Tasks Summary: Attempted 5830 tasks of which 5825 didn't need to
>> be rerun and 1 failed.
>> >
>> > Is it because of the compiler in the makefile?
>>
>> you need to build for 32bit as well. I think you are building these
>> binaries outside yocto and then weirdly mixing the install. So perhaps
>> that should be fixed first maybe.
>>
>> > Is it possible to bypass this error.
>> >
>> > Please guide.
>> > Thanks and Regards,
>> > Hassan
>> >
>> >
>> >
>> >
>>
> thats
>>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59675): https://lists.yoctoproject.org/g/yocto/message/59675
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Compilation of z3gateway

2023-04-11 Thread MOHAMMED HASSAN
Hi Quentin,
Thanks for your reply.
I was able to compile create the executable file but faced issues at the final 
stage.
I only get error at the do_pack stage.

do_install() {
install -d ${D}${bindir}
# install -m 0755 /home/mohan/amlogic/meta-c/ recipes-example/zigbee/files/ 
gecko_sdk_suite/v3.2/build/ Z3GatewayHostm/build/exe ${D}
install -m 0755 /home/mohan/amlogic/meta-c/ recipes-example/zigbee/files/ 
gecko_sdk_suite/v3.2/build/ Z3GatewayHostm/build/exe/ hostforEdge3 ${D}${bindir}
# chmod 0755 /home/mohan/amlogic/meta-c/ recipes-example/zigbee/files/ 
gecko_sdk_suite/v3.2/build/ Z3GatewayHostm/build/exe/ hostforEdge3
# cp /home/mohan/amlogic/meta-c/ recipes-example/zigbee/files/ 
gecko_sdk_suite/v3.2/build/ Z3GatewayHostm/build/exe/ hostforEdge3 ${D}${bindir}
}

bitbake zigbee works fine but bitbake lib32-amlogic-yocto returns the error 
message.

ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in subprocesses:
Command '['arm-pokymllib32-linux- gnueabi-objcopy', '--only-keep-debug', 
'/home/mohan/amlogic/build/ tmp/work/armv7at2hf-neon- 
pokymllib32-linux-gnueabi/ lib32-zigbee/0.1-r0/package/ usr/bin/hostforEdge3', 
'/home/mohan/amlogic/build/ tmp/work/armv7at2hf-neon- 
pokymllib32-linux-gnueabi/ lib32-zigbee/0.1-r0/package/ 
usr/bin/.debug/hostforEdge3']' returned non-zero exit status 1.
Subprocess output:arm-pokymllib32-linux- gnueabi-objcopy: 
/home/mohan/amlogic/build/tmp/ work/armv7at2hf-neon- pokymllib32-linux-gnueabi/ 
lib32-zigbee/0.1-r0/package/ usr/bin/hostforEdge3: file format not recognized

ERROR: Logfile of failure stored in: /home/mohan/amlogic/build/tmp/ 
work/armv7at2hf-neon- pokymllib32-linux-gnueabi/ lib32-zigbee/0.1-r0/temp/log. 
do_package.246282
ERROR: Task (virtual:multilib:lib32:/home/ mohan/amlogic/meta-c/recipes- 
example/zigbee/zigbee_0.1.bb:d o_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5830 tasks of which 5825 didn't need to be rerun 
and 1 failed.

Actually I am completely new to yocto so I am finding it difficult debug.
Is it because of the compiler in the makefile?
Is it possible to bypass this error.

Please guide and support me.

Thanks and Regards,
Hassan


log.do_package
Description: Binary data


zigbee_0.1.bb
Description: Binary data


Makefile
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59678): https://lists.yoctoproject.org/g/yocto/message/59678
Mute This Topic: https://lists.yoctoproject.org/mt/98104663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Missing .o files.

2023-04-11 Thread MOHAMMED HASSAN
> 
> you need to build for 32bit as well. I think you are building these
> binaries outside yocto and then weirdly mixing the install. So perhaps
> that should be fixed first maybe.

I think the makefile is using the default compiler present in my laptop. Can 
you share the file paths for compiler present in my yocto build.
Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59686): https://lists.yoctoproject.org/g/yocto/message/59686
Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Error at do package stage

2023-04-12 Thread MOHAMMED HASSAN
Hi team,
I am trying to build an executable for my yocto dunfell. I am new to yocto
so dont have much knowledge on this. I am running to commands presently.
$ bitbake zigbee (builds successfully).
$ bitbake lib32-amlogic-yocto (do_package error).
 The error message is






*ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in
subprocesses:Command '['arm-pokymllib32-linux-gnueabi-objcopy',
'--only-keep-debug',
'/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3',
'/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/.debug/hostforEdge3']'
returned non-zero exit status 1.Subprocess
output:arm-pokymllib32-linux-gnueabi-objcopy:
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3:
file format not recognizedERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/temp/log.do_package.31632ERROR:
Task
(virtual:multilib:lib32:/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_package)
failed with exit code '1'NOTE: Tasks Summary: Attempted 6233 tasks of which
6220 didn't need to be rerun and 1 failed.*
I tried file command on the executable file and this is the result.

*$ file
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3
/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3:
ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-aarch64.so.1,
BuildID[sha1]=2533a98d31a7a00404b3ecf98cc24e43aafd3b33, for GNU/Linux
3.14.0, with debug_info, not stripped*

*$  file
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/package/usr/bin/hostforEdge3*
*/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/package/usr/bin/hostforEdge3:
ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-aarch64.so.1,
BuildID[sha1]=2533a98d31a7a00404b3ecf98cc24e43aafd3b33, for GNU/Linux
3.14.0, stripped*

I have attached the bb file, makefile and logs for your reference.
Also I am not sure how to add the proper compiler,linker,archive flags to
the makefile. If possible please guide me on that as well.


Thanks and Regards,
Hassan


Makefile
Description: Binary data


zigbee_0.1.bb
Description: Binary data


log.do_package
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59688): https://lists.yoctoproject.org/g/yocto/message/59688
Mute This Topic: https://lists.yoctoproject.org/mt/98214685/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] error adding symbols: DSO missing from command line

2023-04-18 Thread MOHAMMED HASSAN
Hi guys,
I am trying to build a custom application for my build but facing the
following error,
vice-discovery-host.o  -lreadline -lncurses  -lm -lpthread -o
./build/exe/hostforEdge3
|





* aarch64-poky-linux-ld: build/backchannel-support.o: undefined reference
to symbol 'socket@@GLIBC_2.17'| aarch64-poky-linux-ld:
/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/recipe-sysroot/lib64/libc.so.6:
error adding symbols: DSO missing from command line| make: ***
[Makefile:415: build/exe/hostforEdge3] Error 1| ERROR: oe_runmake failed|
WARNING: exit code 1 from a shell command.| ERROR: Execution of
'/home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/temp/run.do_compile.211997'
failed with exit code 1ERROR: Task
(/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_compile)
failed with exit code '1'*
I checked for the missing lib.so.6 file using *ldconfig -p | grep libc.so.6
*command and this is what I got,



*libc.so.6 (libc6,x32, OS ABI: Linux 3.4.0) => /libx32/libc.so.6 libc.so.6
(libc6,x86-64, OS ABI: Linux 3.2.0) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 3.2.0) => /lib/i386-linux-gnu/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 3.2.0) => /lib32/libc.so.6*

I am not sure how to add this library to my linker. Can you guys help me
with this.

Thanks and regards,
Hassan


makefile
Description: Binary data


zigbee_0.1.bb
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59721): https://lists.yoctoproject.org/g/yocto/message/59721
Mute This Topic: https://lists.yoctoproject.org/mt/98341723/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] error adding symbols: DSO missing from command line

2023-04-18 Thread MOHAMMED HASSAN
Hi guys,
Can you please support me on this.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59724): https://lists.yoctoproject.org/g/yocto/message/59724
Mute This Topic: https://lists.yoctoproject.org/mt/98341723/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] OTA updates for Application Software

2023-04-20 Thread MOHAMMED HASSAN
Hi guys,
I wanted to know if it is possible to update your application through OTA
updates.
If yes, then please share some documentation or some steps in achieving it.
If not, then what other alternatives do we have to update the
application in our hardware deployed at some remote location.

Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59744): https://lists.yoctoproject.org/g/yocto/message/59744
Mute This Topic: https://lists.yoctoproject.org/mt/98403981/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] NPM package management

2023-04-20 Thread MOHAMMED HASSAN
Hi guys,
I am writing a nodejs application for my board running on yocto dunfell. I
had a doubt regarding the npm packages. Since my application would use a
lot of node js packages, how do I load all those packages? I didn't
understand much about the npm registry tool and how it can help for custom
complex applications.
If you guys have any ideas or suggestions please let me know.


Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59745): https://lists.yoctoproject.org/g/yocto/message/59745
Mute This Topic: https://lists.yoctoproject.org/mt/98404043/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Unable to solve the initramfs issues

2023-04-20 Thread MOHAMMED HASSAN
Hi Merek,
Sorry for the late reply.

> 
> You didn't add log from flashing where it fails. Can you set
> INITRAMFS_MAXSIZE to only 200M or so? Also from logs it looks like
> you're using amlogic. Can you maybe ask for support from your vendor?

I was able to build the image but the rebooting failed.
I was able to solve the issue by using command CORE_IMAGE_EXTRA_INSTALL_append 
= " nodejs nodejs-npm"; in my local.conf folder.

Though I am not completely why above line worked. Can anyone explain to me the 
reasoning behind it.

Thanks and Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59748): https://lists.yoctoproject.org/g/yocto/message/59748
Mute This Topic: https://lists.yoctoproject.org/mt/98099160/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Integrating npm packages in yocto build

2023-04-24 Thread MOHAMMED HASSAN
Hi guys,
If I want to add a nodejs application, how can I add  its necessary npm
packages. Do I have to create a folder containing all the packages source
files and install or build them with the application.
I have gone through the documentation and read about devtool but
didn't understand much about it.
It would be better if you can share some real time examples you've worked
on.
If you want to share your insights feel free to connect with me.

Thanks and Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59765): https://lists.yoctoproject.org/g/yocto/message/59765
Mute This Topic: https://lists.yoctoproject.org/mt/98465678/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Trouble Adding Files to rootfs

2023-05-02 Thread MOHAMMED HASSAN
On Tue, May 2, 2023 at 03:17 PM, Anthony Abboud wrote:

> 
> HI Yocto Community,
> 
> I am currently working on build a custom Boot2Qt image to learn about
> How-To's since it's my first time playing with Yocto. I am successfully
> able to build an image for my system; manually inserting and launching my
> Qt application works great.
> 
> Now I want to include this app and some files into the rootfs of the
> image. I modified the recipe by adding the following lines at the end to
> attempt this:
> 
> ```
> SRC_URI += " \
> file://qtApp_qml \
> file://startup.sh \
> file://fb.modes \
> "
> 
> 

Add S=${WORKDIR}

> 
> 
> do_install() {
> install -d ${D}/home/root
> install -m 755 ${WORKDIR}/qtApp_qml ${D}/home/root/
> 
> install -d ${D}/etc/init.d
> install -m 755 ${WORKDIR}/startup.sh ${D}/etc/init.d/
> 
> install -d ${D}/etc
> install -m 755 ${WORKDIR}/fb.modes ${D}/etc/
> }
> 
> FILES_${PN} += " \
> /home/root/qtApp_qml \
> /etc/init.d/startup.sh \
> /etc/fb.modes \
> "
> ``
> 
> 

Run bitbake recipename
if it builds successfully then add the recipe to local.conf folder by appending 
the line CORE_IMAGE_EXTRA_INSTALL += “ recipename “

Save and run bitbake target

I've tried a few variations I saw around but still nothing. Any idea what's 
missing?
Can you please elaborate on all variations you have tried.

I am also a beginner on yocto so my additions may not work, but give it a try 
and let me know once the files are loaded.

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59846): https://lists.yoctoproject.org/g/yocto/message/59846
Mute This Topic: https://lists.yoctoproject.org/mt/98649960/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Trouble Adding Files to rootfs

2023-05-03 Thread Mohammed Hassan
On Wed, May 3, 2023 at 03:47 AM, Anthony Abboud wrote:

> 
> HI Yocto Community,
> 
> I am currently working on build a custom Boot2Qt image to learn about
> How-To's since it's my first time playing with Yocto. I am successfully
> able to build an image for my system; manually inserting and launching my
> Qt application works great.
> 
> Now I want to include this app and some files into the rootfs of the
> image. I modified the recipe by adding the following lines at the end to
> attempt this:
> 
> ```
> SRC_URI += " \
> file://qtApp_qml \
> file://startup.sh \
> file://fb.modes \
> "
> 
> 

I am also a beginner but try adding S=${WORKDIR} and then building.

> 
> 
> do_install() {
> install -d ${D}/home/root
> install -m 755 ${WORKDIR}/qtApp_qml ${D}/home/root/
> 
> install -d ${D}/etc/init.d
> install -m 755 ${WORKDIR}/startup.sh ${D}/etc/init.d/
> 
> install -d ${D}/etc
> install -m 755 ${WORKDIR}/fb.modes ${D}/etc/
> }
> 
> FILES_${PN} += " \
> /home/root/qtApp_qml \
> /etc/init.d/startup.sh \
> /etc/fb.modes \
> "
> ```
> 
> 

After this run bitbake recipe. If there are no errors, then  add the line 
CORE_IMAGE_EXTRA_APPEND += “ recipe “ in local.conf folder.
Bitbake target

> 
> 
> But I'm simply unable to get those three files to show up at all in the
> final build (both the folders and files!).
> 
> I've tried a few variations I saw around but still nothing. Any idea
> what's missing?
> 
> Thanks!
> Anthony
> 
> 

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59848): https://lists.yoctoproject.org/g/yocto/message/59848
Mute This Topic: https://lists.yoctoproject.org/mt/98649960/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Trouble Adding Files to rootfs

2023-05-03 Thread MOHAMMED HASSAN
On Tue, May 2, 2023 at 03:17 PM, Anthony Abboud wrote:

> 
> HI Yocto Community,
> 
> I am currently working on build a custom Boot2Qt image to learn about
> How-To's since it's my first time playing with Yocto. I am successfully
> able to build an image for my system; manually inserting and launching my
> Qt application works great.
> 
> Now I want to include this app and some files into the rootfs of the
> image. I modified the recipe by adding the following lines at the end to
> attempt this:
> 
> ```
> 
> 

Ignore my previous posts Ive made some mistakes there.
1) Create a custom recipe file.

> 
> 
> SRC_URI += " \
> file://qtApp_qml \
> file://startup.sh \
> file://fb.modes \
> "
> 
> 

Add line S="${WORKDIR}"

> 
> 
> do_install() {
> install -d ${D}/home/root
> install -m 755 ${WORKDIR}/qtApp_qml ${D}/home/root/
> 
> install -d ${D}/etc/init.d
> install -m 755 ${WORKDIR}/startup.sh ${D}/etc/init.d/
> 
> install -d ${D}/etc
> install -m 755 ${WORKDIR}/fb.modes ${D}/etc/
> }
> 
> FILES_${PN} += " \
> /home/root/qtApp_qml \
> /etc/init.d/startup.sh \
> /etc/fb.modes \
> "
> ```
> 
> 

Run bitbake recipename
If it runs successfully,  then add the below in your local.conf folder.
CORE_IMAGE_EXTRA_INSTALL_append += " recipename "
Next bitbake target

> 
> 
> But I'm simply unable to get those three files to show up at all in the
> final build (both the folders and files!).
> 
> I've tried a few variations I saw around but still nothing. Any idea
> what's missing?
> 

Would it be possible for you to share what changes you have tried. To be honest 
I am a beginner too and want too learn more, so I got curious.
Also the above will most probably work, but in case you solve it with any other 
method, then please post here for other's reference.

> 
> 
> 
> Thanks!
> Anthony
> 

Best Regards,
Hassan

> 
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59850): https://lists.yoctoproject.org/g/yocto/message/59850
Mute This Topic: https://lists.yoctoproject.org/mt/98649960/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Unable to locate insatlled nodejs packages

2023-05-08 Thread MOHAMMED HASSAN
Hi guys,
I am referring this link
https://stackoverflow.com/questions/71293110/how-to-add-nodejs-packages-to-yocto
as a basuc example to add npm packages in my image.

However,
I see no npm install, no do_install function in the .bb file so got
confused if the packages are actually installing in my image or not.

Can you guys guide me on this. How can I know if the file have been
installed, which directory do I check?

Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59900): https://lists.yoctoproject.org/g/yocto/message/59900
Mute This Topic: https://lists.yoctoproject.org/mt/98759386/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] OTA Updates

2023-05-11 Thread MOHAMMED HASSAN
Hi all,
So I am referring this page for OTA updates
https://wiki.yoctoproject.org/wiki/System_Update

However are these all paid or free services. Any more info about these
services is welcomed.
Also are there any tutorials, YouTube videos on ota updates for yocto? I
couldn’t find any though.


Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59989): https://lists.yoctoproject.org/g/yocto/message/59989
Mute This Topic: https://lists.yoctoproject.org/mt/98828664/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Out of tree driver file compilation error

2023-06-20 Thread MOHAMMED HASSAN
Hi guys,
I am trying to load TI bq2429x drivers into my yocto image. I face errors
when at the do_compile stage. At first glance it looks to be a c program
cross compilation error. I think the issue is due to not being able to link
with the header files.
The error I see on my screen.
ERROR: bq2429x-charger-0.1-r0 do_compile: oe_runmake failed
ERROR: bq2429x-charger-0.1-r0 do_compile: Execution of
'/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/temp/run.do_compile.322928'
failed with exit code 1
ERROR: Logfile of failure stored in:
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/temp/log.do_compile.322928
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
KERNEL_SRC=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
KERNEL_PATH=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
KERNEL_VERSION=5.4.180-amlogic CC=aarch64-poky-linux-gcc   -fuse-ld=bfd
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0=/usr/src/debug/bq2429x-charger/0.1-r0

-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/recipe-sysroot=

-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/recipe-sysroot-native=

 
-fdebug-prefix-map=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source=/usr/src/kernel
LD=aarch64-poky-linux-ld.bfd   AR=aarch64-poky-linux-ar
 
O=/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-build-artifacts
KBUILD_EXTRA_SYMBOLS=
| make -C
/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-source
M=/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0
| make[1]: Entering directory '/home/mohan/amlogic/aml-comp/kernel/aml-5.4'
| make[2]: Entering directory
'/home/mohan/amlogic/build/tmp/work-shared/mesons4-lib32-ap222/kernel-build-artifacts'
|   AR
 
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/built-in.a
|   CC [M]
 
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.o
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:37:
error: "BQ2429X_OTG_ENABLE" redefined [-Werror]
|37 | #define BQ2429X_OTG_ENABLE  0x00
|   |
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:36:
note: this is the location of the previous definition
|36 | #define BQ2429X_OTG_ENABLE  0x01
|   |
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_disable_otg':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:14:
error: 'BQ2429X_OTG_DISABLE' undeclared (first use in this function); did
you mean 'BQ2429X_WD_DISABLE'?
|   317 | u8 val = BQ2429X_OTG_DISABLE << BQ2429x_OTG_SHIFT;
|   |  ^~~
|   |  BQ2429X_WD_DISABLE
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:14:
note: each undeclared identifier is reported only once for each function it
appears in
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:317:37:
error: 'BQ2429x_OTG_SHIFT' undeclared (first use in this function); did you
mean 'BQ2429X_OTG_SHIFT'?
|   317 | u8 val = BQ2429X_OTG_DISABLE << BQ2429x_OTG_SHIFT;
|   | ^
|   | BQ2429X_OTG_SHIFT
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
At top level:
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:323:63:
error: function declaration isn't a prototype [-Werror=strict-prototypes]
|   323 | static int bq2429x_set_chargecurrent(struct bq2429x *bq, enum
bq2429x_charge_current current)
|   |
^~
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_set_chargevoltage':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:349:6:
error: unused variable 'ret' [-Werror=unused-variable]
|   349 |  int ret;
|   |  ^~~
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:
In function 'bq2429x_set_input_volt_limit':
|
/home/mohan/amlogic/build/tmp/work/mesons4_lib32_ap222-poky-linux/bq2429x-charger/0.1-r0/bq2429x_charger.c:373:6:
error: unused variable 'ret' [-Werror=unuse

[yocto] do_configure error while adding networkmanager to image

2023-07-06 Thread MOHAMMED HASSAN
Hi guys,
I am trying to add networkmanager to my image. However i get the error
message as shown below
DEBUG: Executing shell function autotools_preconfigure
DEBUG: Shell function autotools_preconfigure finished
DEBUG: Executing python function autotools_aclocals
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Python function autotools_aclocals finished
DEBUG: Executing shell function do_configure
automake (GNU automake) 1.16.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later <
https://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey 
   and Alexandre Duret-Lutz .
AUTOV is 1.16
NOTE: Executing intltoolize --copy --force --automake
NOTE: Executing ACLOCAL="aclocal
--system-acdir=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/lib32-recipe-sysroot/usr/share/aclocal/
--automake-acdir=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal-1.16"
autoreconf -Wcross --verbose --install --force --exclude=autopoint -I
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/NetworkManager-1.22.16/m4/
-I
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal/
autoreconf: Entering directory `.'
autoreconf: running: aclocal
--system-acdir=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/lib32-recipe-sysroot/usr/share/aclocal/
--automake-acdir=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal-1.16
-I
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/NetworkManager-1.22.16/m4/
-I
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal/
--force
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running:
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/bin/autoconf
--include=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/NetworkManager-1.22.16/m4/
--include=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal/
--force
autoreconf: running:
/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/bin/autoheader
--include=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/NetworkManager-1.22.16/m4/
--include=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-networkmanager/1.22.16-r0/recipe-sysroot-native/usr/share/aclocal/
--force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:29: installing 'build-aux/compile'
configure.ac:24: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
gtk-doc.make:173: warning: $(DOC_MAIN_SGML_FILE) was already defined in
condition BUILD_DOCS, which is included in condition TRUE ...
docs/api/Makefile.am:105:   'gtk-doc.make' included from here
docs/api/Makefile.am:14: ... '$(DOC_MAIN_SGML_FILE)' previously defined here
autoreconf: running: gnu-configize
autoreconf: Leaving directory `.'
NOTE: Running ../NetworkManager-1.22.16/configure  --build=x86_64-linux
 --host=arm-pokymllib32-linux-gnueabi
 --target=arm-pokymllib32-linux-gnueabi  --prefix=/usr  --exec_prefix=/usr
 --bindir=/usr/bin  --sbindir=/usr/sbin  --libexecdir=/usr/libexec
 --datadir=/usr/share  --sysconfdir=/etc  --sharedstatedir=/com
 --localstatedir=/var  --libdir=/usr/lib  --includedir=/usr/include
 --oldincludedir=/usr/include  --infodir=/usr/share/info
 --mandir=/usr/share/man  --disable-silent-rules
 --disable-dependency-tracking
 
--with-libtool-sysroot=/home/hp/Yocto-SDK/build/tmp/work/armv7at2hf-neon-pokymllib32-li

Re: [yocto] do_configure error while adding networkmanager to image

2023-07-06 Thread MOHAMMED HASSAN
On Thu, Jul 6, 2023 at 02:29 AM, Adrian Freihofer wrote:

> 
> Hi Hassan

Hi Adrian,
Thanks for your reply.

> 
> It's a bit hard to guess what you are really doing. The bb is a fork
> from a quite old version when it was still using the autotools. Now we
> use meson.
> 
> The check for rl_echo_signal_char came into NetworkManager 8 years ago
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b69143b5085c58e51ab8077ee5cbe6fafe73e041
> .
> It's probably not a change on NetworkManager side which came in
> recently with your update to 1.22.16.
> 
> Compiling nmcli with readline works with the bb from meta-openembedded
> and the poky version with a similar age. That's the default.
> 
> Some ideas:
> - Try if the original recipe throws the same error
> - Pass the readline parameter to autotools (what we do with newer
> versions of the recipe and meson)
> - Compile without nmcli and remove the readline dependency. Look at the
> commit history of the networkmanager.bb. There was an autotools based
> recipe which supported compiling without nmcli at some point in time.

Actually I want nmcli recipe in my yocto image file. I am still a beginner with 
this so i am facing these issues. Alternatively, I was looking at adding 
wireless-tools to my image file but i dont have its related recipe in my SDK. 
Do let me know if you have any suggestions.

> 
> Regards,
> Adrian

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60524): https://lists.yoctoproject.org/g/yocto/message/60524
Mute This Topic: https://lists.yoctoproject.org/mt/99982001/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] do_configure error while adding networkmanager to image

2023-07-06 Thread MOHAMMED HASSAN
On Thu, Jul 6, 2023 at 02:29 AM, Adrian Freihofer wrote:

> 
> Hi Hassan
> 
> It's a bit hard to guess what you are really doing. The bb is a fork
> from a quite old version when it was still using the autotools. Now we
> use meson.
> 
> The check for rl_echo_signal_char came into NetworkManager 8 years ago
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b69143b5085c58e51ab8077ee5cbe6fafe73e041
> .
> It's probably not a change on NetworkManager side which came in
> recently with your update to 1.22.16.
> 
> Compiling nmcli with readline works with the bb from meta-openembedded
> and the poky version with a similar age. That's the default.
> 
> Some ideas:
> - Try if the original recipe throws the same error
> - Pass the readline parameter to autotools (what we do with newer
> versions of the recipe and meson)
> - Compile without nmcli and remove the readline dependency. Look at the
> commit history of the networkmanager.bb. There was an autotools based
> recipe which supported compiling without nmcli at some point in time.

Actually I want nmcli recipe in my yocto image file. I am still a beginner with 
this so i am facing these issues. Alternatively, I was looking at adding 
wireless-tools to my image file but i dont have its related recipe in my SDK. 
Do let me know if you have any suggestions.
Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60525): https://lists.yoctoproject.org/g/yocto/message/60525
Mute This Topic: https://lists.yoctoproject.org/mt/99982001/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Memory requirements for building images with different architectures

2023-09-07 Thread MOHAMMED HASSAN
Hi guys,
I wanted to build images for different architectures and machine types on
one SDK. I know that the build directory takes a lot of space (in my case
more than 90 GB). What to do in such a case.
Are they any efficient techniques that you can share with me?




Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60941): https://lists.yoctoproject.org/g/yocto/message/60941
Mute This Topic: https://lists.yoctoproject.org/mt/101231469/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Memory requirements for building images with different architectures

2023-09-07 Thread MOHAMMED HASSAN
> 
> 
> Right, you're not the only one!
> See
> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
> 
> and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html

I can use rm_work and remove all the build related files, however every 
subsequent build would take a lot more time to build. I want my builds to be as 
fast as possible. Do you have any suggestions to for faster builds while 
consuming less memory space.

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60943): https://lists.yoctoproject.org/g/yocto/message/60943
Mute This Topic: https://lists.yoctoproject.org/mt/101231469/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Memory requirements for building images with different architectures

2023-09-08 Thread MOHAMMED HASSAN
My builds on an average take 15-20 mins with the build folder intact.
How much time do you think it will take on average with rm_work enabled?

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60946): https://lists.yoctoproject.org/g/yocto/message/60946
Mute This Topic: https://lists.yoctoproject.org/mt/101231469/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Cross-compilation of driver files

2023-09-18 Thread MOHAMMED HASSAN
Hi guys,
So long back I was trying to load driver files for a battery charger and a
battery fuel gauge as a kernel module. However I face errors that are
actually related to cross-compilation. I  am not sure how to proceed with
this. Can you guys refer to some documentation from both the yocto project
and any other that can help.
Thanks

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61032): https://lists.yoctoproject.org/g/yocto/message/61032
Mute This Topic: https://lists.yoctoproject.org/mt/101433218/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Cross-compilation of driver files

2023-09-20 Thread MOHAMMED HASSAN
On Mon, Sep 18, 2023 at 06:36 AM, MOHAMMED HASSAN wrote:

> 
> Hi guys,
> So long back I was trying to load driver files for a battery charger and a
> battery fuel gauge as a kernel module. However I face errors that are
> actually related to cross-compilation. I  am not sure how to proceed with
> this. Can you guys refer to some documentation from both the yocto project
> and any other that can help.
> Thanks
> 

Come on guys, give me something!! I am tyring to load TI BQ2429x driver.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61047): https://lists.yoctoproject.org/g/yocto/message/61047
Mute This Topic: https://lists.yoctoproject.org/mt/101433218/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-09-25 Thread MOHAMMED HASSAN
What prerequiste knowledge should I have before deciding to help. I have less 
experience with yocto and embedded linux in general.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61115): https://lists.yoctoproject.org/g/yocto/message/61115
Mute This Topic: https://lists.yoctoproject.org/mt/101587890/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] How to use updated npm version in my image

2023-09-29 Thread MOHAMMED HASSAN
Hi guys,
I am using yocto dunfell for my image. I am able to install nodejs 14 and
npm version 6.something.
I want it to instead install 9.8.1 with my image. At present I have to
manually install it after loading the image. Is there a way to update it in
the recipe file? My recipe file name is nodejs_12.22.12.bb.


Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61166): https://lists.yoctoproject.org/g/yocto/message/61166
Mute This Topic: https://lists.yoctoproject.org/mt/101658969/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Password added succesfully but defaults to autologin

2023-10-09 Thread MOHAMMED HASSAN
Hi guys,
I am trying to set up a login password for my hardware but the problem is
that my device uses automatic login. I checked online to comment out
automatic login but it seems like
my /lib/systemd/system/serial-getty\@.service contains the line
"ExecStart=-/sbin/agetty -8 -L %I 921600 $TERM --autologin root" but before
building the image i checked my service file and "ExecStart=-/sbin/agetty
-8 -L %I @BAUDRATE@ $TERM". There is no mention of autologin and in my
image recipe file I have not enabled it.
After removing the line manually and reloading the service I can use the
login creds to login but ssh login returns the message "permission denied".

I have attached the relevant files for your reference. Let me know if you
need more information.

Regards,
Hassan


amlogic-yocto.bb
Description: Binary data
#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Serial Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=http://0pointer.de/blog/projects/serial-console.html
PartOf=dev-%i.device
ConditionPathExists=/dev/%i
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
After=rc-local.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes

# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service

[Service]
Environment="TERM=xterm"
ExecStart=-/sbin/agetty -8 -L %I @BAUDRATE@ $TERM
Type=idle
Restart=always
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes

[Install]
WantedBy=getty.target


systemd-serialgetty.bb
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61283): https://lists.yoctoproject.org/g/yocto/message/61283
Mute This Topic: https://lists.yoctoproject.org/mt/101849757/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN
Hi guys,
I want to know more about security updates in yocto.
So generally we update our distros when we get pop-ups about security
updates and it's done. But what if my device is installed at a
remote location? How does security update take place in the case of yocto?
How can we do it?
Any other relevant information is graciously welcomed.


Thanks and Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61284): https://lists.yoctoproject.org/g/yocto/message/61284
Mute This Topic: https://lists.yoctoproject.org/mt/101851310/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN
On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:

> 
> Please see https://wiki.yoctoproject.org/wiki/System_Update
> 
> 

Thanks for your reply. I am aware of the system_updates feature though still 
yet to implement. Is it possible to update the yocto version (i use dunfell) to 
the latest one, to update the linux version(mine is 5.4.180) to the latest and 
to update the tools to the latest using these features. Actually i have no 
clarity with this so I am asking.

Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61286): https://lists.yoctoproject.org/g/yocto/message/61286
Mute This Topic: https://lists.yoctoproject.org/mt/101851310/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN
On Mon, Oct 9, 2023 at 07:11 AM, Michael Opdenacker wrote:

> 
> Hi Hassan
> 
> On 09.10.23 at 15:22, MOHAMMED HASSAN wrote:
> 
>> On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:
>> 
>> Please see https://wiki.yoctoproject.org/wiki/System_Update
>> 
>> Thanks for your reply. I am aware of the system_updates feature though
>> still yet to implement. Is it possible to update the yocto version (i
>> use dunfell) to the latest one, to update the linux version(mine is
>> 5.4.180) to the latest and to update the tools to the latest using
>> these features. Actually i have no clarity with this so I am asking.
> 
> 
> Which version of Yocto are you using? If you have one that is still
> supported (like Kirkstone or Dunfell), I'd recommend to stick to these
> and just rebuild with the latest release update. This way you have the
> latest vulnerability fixes supported by the Yocto Project. Once a new
> image is generated, you can deploy it using one of the tools Josef
> mentioned.
> 
> Moving to the latest version of Yocto will represent more work, all the
> more as the latest one should be replaced this month.
> 
> As far as the Linux kernel is concerned, I'd rather work with a stable
> LTS kernel ( https://kernel.org/category/releases.html ), as I guess the
> Yocto Project releases can't match the stable kernels in terms of
> vulnerability fixes and how quickly they are deployed. That's my own
> opinion though.
> 
> 

Hi Michael,
Thanks for your reply.
I am currently using dunfell 3.1.11 and my kernel release is Linux 
5.4.180-amlogic. Going by your suggestion i should rebuild to the latest 
dunfell update i.e 3.1.28. Moving to kirkstone would take more work.
I will search on how to update my yocto release version and get into it.

Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61289): https://lists.yoctoproject.org/g/yocto/message/61289
Mute This Topic: https://lists.yoctoproject.org/mt/101851310/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Password added succesfully but defaults to autologin

2023-10-09 Thread MOHAMMED HASSAN
Let me know if I am making any mistakes here. Also let me know if you need any 
other piece of information to help me on this issue.

Thanks,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61290): https://lists.yoctoproject.org/g/yocto/message/61290
Mute This Topic: https://lists.yoctoproject.org/mt/101849757/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] inode mismatch

2023-10-09 Thread MOHAMMED HASSAN
Hi guys,
I did bitbake image clean && bitbake image but it continuously due to inode
mismatch
The error i see
Initialising tasks: 100%
|##|
Time: 0:00:19
Sstate summary: Wanted 236 Found 217 Missed 19 Current 2867 (91% match, 99%
complete)
NOTE: Executing Tasks
ERROR: lib32-libdrm-meson-git-r0 do_prepare_recipe_sysroot: Error executing
a python function in exec_func_python() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:extend_recipe_sysroot(d)
 0003:
File: '/Yocto/yocto_sdk/poky/meta/classes/staging.bbclass', lineno: 595,
function: extend_recipe_sysroot
 0591:for f in fixme:
 0592:staging_processfixme(fixme[f], f, recipesysroot,
recipesysrootnative, d)
 0593:
 0594:for p in postinsts:
 *** 0595:subprocess.check_output(p, shell=True,
stderr=subprocess.STDOUT)
 0596:
 0597:for dep in manifests:
 0598:c = setscenedeps[dep][0]
 0599:os.symlink(manifests[dep], depdir + "/" + c + ".complete")
File: '/usr/lib/python3.8/subprocess.py', lineno: 415, function:
check_output
 0411:else:
 0412:empty = b''
 0413:kwargs['input'] = empty
 0414:
 *** 0415:return run(*popenargs, stdout=PIPE, timeout=timeout,
check=True,
 0416:   **kwargs).stdout
 0417:
 0418:
 0419:class CompletedProcess(object):
File: '/usr/lib/python3.8/subprocess.py', lineno: 516, function: run
 0512:# We don't call process.wait() as .__exit__ does that
for us.
 0513:raise
 0514:retcode = process.poll()
 0515:if check and retcode:
 *** 0516:raise CalledProcessError(retcode, process.args,
 0517: output=stdout, stderr=stderr)
 0518:return CompletedProcess(process.args, retcode, stdout, stderr)
 0519:
 0520:
Exception: subprocess.CalledProcessError: Command
'/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/lib32-recipe-sysroot/usr/bin/postinst-useradd-lib32-systemd'
returned non-zero exit status 1.

Subprocess output:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/recipe-sysroot-native/usr/sbin/useradd
Running groupadd commands...
NOTE: lib32-systemd: Performing groupadd with [--root
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/lib32-recipe-sysroot
-r systemd-journal]
abort()ing pseudo client by server request. See
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/pseudo//pseudo.log
Aborted (core dumped)
ERROR: lib32-systemd: groupadd command did not succeed.

ERROR: Logfile of failure stored in:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/temp/log.do_prepare_recipe_sysroot.870561
ERROR: Task
(virtual:multilib:lib32:/Yocto/yocto_sdk/meta-meson/recipes-graphics/wayland/libdrm-meson_git.bb:do_prepare_recipe_sysroot)
failed with exit code '1'



*Here is the data of the entire log file.
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/pseudo//pseudo.log*

debug_logfile: fd 2
pid 163883 [parent 163882], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 163882.
db cleanup for server shutdown, 09:44:43.924
memory-to-file backup complete, 09:44:43.924.
db cleanup finished, 09:44:43.924
debug_logfile: fd 2
pid 384934 [parent 384929], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 384929.
db cleanup for server shutdown, 09:54:34.912
memory-to-file backup complete, 09:54:34.912.
db cleanup finished, 09:54:34.912
debug_logfile: fd 2
pid 1804511 [parent 1804508], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 1804508.
creat for '/tmp/sh-thd.X4MAa7' replaces existing 9438805
['/tmp/sh-thd.qyh9bp'].
creat for '/tmp/sh-thd.XAqy56' replaces existing 9438805
['/tmp/sh-thd.X4MAa7'].
creat for '/tmp/sh-thd.OU5Xfn' replaces existing 9438805
['/tmp/sh-thd.XAqy56'].
creat for '/tmp/sh-thd.EXpf9x' replaces existing 9438805
['/tmp/sh-thd.OU5Xfn'].
creat for '/tmp/sh-thd.XJ9pbB' replaces existing 9438805
['/tmp/sh-thd.EXpf9x'].
db cleanup for server shutdown, 10:47:41.903
memory-to-file backup complete, 10:47:41.903.
db cleanup finished, 10:47:41.903
debug_logfile: fd 2
pid 1960923 [parent 1960922], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 1960922.
db cleanup for server shutdown, 10:52:14.678
memory-to-fil

[yocto] What laptops do you use for faster builds

2023-10-10 Thread MOHAMMED HASSAN
Hi guys,
I was curious to know the laptops/desktop/workstations you guys use for
quick and faster builds. Can you list out the specs as well and maybe some
tips and tricks for reducing build time.


Thanks and regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61314): https://lists.yoctoproject.org/g/yocto/message/61314
Mute This Topic: https://lists.yoctoproject.org/mt/101891951/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Architecture did not match

2023-11-14 Thread MOHAMMED HASSAN
On Tue, Nov 14, 2023 at 11:17 PM, Khem Raj wrote:

> 
> add lib32-testing-firmware in your image instead of testing-firmware
> 
> 

NOTE: lib32-gst-plugin-video-sink: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-video-sink
NOTE: lib32-gst-plugin-aml-v4l2dec: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-aml-v4l2dec
NOTE: u-boot: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/uboot
ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: Architecture did 
not match (x86-64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.musl.node
Architecture did not match (x86-64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.glibc.node
Architecture did not match (AArch64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/android-arm64/node.napi.armv8.node
Architecture did not match (AArch64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm64/node.napi.armv8.node
 [arch]
WARNING: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: 
/home/root/Edge/install.sh contained in package lib32-testing-firmware requires 
/bin/bash, but no providers found in RDEPENDS_lib32-testing-firmware? 
[file-rdeps]
ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA run found fatal errors. 
Please consider fixing them.
ERROR: Logfile of failure stored in: 
/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/log.do_package_qa.52476
ERROR: Task 
(virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/meta-blaze/recipes-example/testing-firmware/testing-firmware_0.1.bb:do_package_qa)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 7801 tasks of which 7737 didn't need to be rerun 
and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds

Summary: 1 task failed:

Still the same error but now the architecture is shown different.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61687): https://lists.yoctoproject.org/g/yocto/message/61687
Mute This Topic: https://lists.yoctoproject.org/mt/102600630/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Unable to run arm 64 binary on arm64 machine

2023-11-14 Thread MOHAMMED HASSAN
On Tue, Nov 14, 2023 at 11:40 PM, Khem Raj wrote:

> 
> it seems you have a mixed mode image where kernel is 64bit but userspace
> is 32bit, so you have to compile your app to be 32bit as well.
> otherwise you need to include 64bit runtime as well to support 64bit apps.
> 
> 

Unfortunately I don't have much clarity on how to achieve this. Can you suggest 
what i should do.
Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61690): https://lists.yoctoproject.org/g/yocto/message/61690
Mute This Topic: https://lists.yoctoproject.org/mt/102600996/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Unable to run arm 64 binary on arm64 machine

2023-11-14 Thread MOHAMMED HASSAN
root@se-704a0efe85c4:~# ./hello
-sh: ./hello: No such file or directory
root@se-704a0efe85c4:~#

This is the response.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61692): https://lists.yoctoproject.org/g/yocto/message/61692
Mute This Topic: https://lists.yoctoproject.org/mt/102600996/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Architecture did not match

2023-11-15 Thread MOHAMMED HASSAN
On Tue, Nov 14, 2023 at 11:45 PM, Khem Raj wrote:

> 
> in your recipe, you need to add runtime dependencies. e.g.
> 
> RDEPENDS:${PN} += "bash"
> 
> or you can ignore the deps if your image has them all in already.
> since your package is binary only.
> add
> INSANE_SKIP:${PN} = "file-rdeps"
> 
> 

Tested but still the same error. Also its not a binary file, i couldnt create 
nodejs binary using yocto. *Let me know if such feature is available.* So the 
files I have actually is an complete application inside the Edge folder 
containing the application along with the package-json and the node_modules.
Also I have referred to the nodejs page but its not as easy to load the 
packages as it looks, specially when you have lots of npm packages to download. 
Do let me know if you have any easier alternatives.

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61694): https://lists.yoctoproject.org/g/yocto/message/61694
Mute This Topic: https://lists.yoctoproject.org/mt/102600630/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Installing entire directory in my image file

2023-11-15 Thread MOHAMMED HASSAN
Hi guys,
So I want to load an entire directory in my image file but I am unable to
achieve two things.
1) Load the entire directory in my image.
2) Unable to load any file, directory in my /home/root directory.

*My recipe file is:*
DESCRIPTION =  "Testing firmware for Edge 3 hubs"

LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

#SRC_URI = "file://Edge \
#  file://Edge/package.json \
#  file://Edge/node_modules"
SRC_URI = "file://Edge \
   file://server "
#file://z_WaveManufacturerSpecific.json

S = "${WORKDIR}"
#INSANE_SKIP:${PN} += "arch:/Edge/node_modules/"
#INSANE_SKIP:${PN} = "file-rdeps"


do_configure(){
:
}

do_compile(){
:
}
INHERIT_remove = "pseudo"

do_install() {
install -d ${D}${bindir}/Edge
install -d ${D}${bindir}/server
install -d ${D}/home/root/Edge
install -d ${D}/home/root/server

cp -r ${WORKDIR}/Edge/* ${D}${bindir}/Edge/
cp -r ${WORKDIR}/server/* ${D}${bindir}/server/
cp -r ${WORKDIR}/Edge/* ${D}/home/root/Edge/
cp -r ${WORKDIR}/server/* ${D}/home/root/server/
}
FILES_${PN} = "${bindir}"
FILES_${PN} = "/home/root"

*I get the error message:*
ERROR: lib32-testing-firmware-0.1-r0 do_install: Execution of
'/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/run.do_install.2725327'
failed with exit code 134
ERROR: Logfile of failure stored in:
/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/log.do_install.2725327
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-core/glibc/glibc_2.31.bb:do_populate_sysroot',
'/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/quilt/quilt-native_0.66.bb:do_populate_sysroot',
'virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/gcc/gcc-runtime_9.3.bb:do_populate_sysroot',
'virtual:native:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
'virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/gcc/gcc-cross_9.3.bb:do_populate_sysroot',
'virtual:native:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/patch/patch_2.7.6.bb:
do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['lib32-glibc',
'quilt-native', 'lib32-gcc-runtime', 'pseudo-native',
'lib32-gcc-cross-arm', 'patch-native', 'lib32-linux-libc-headers',
'lib32-libgcc', 'automake-native', 'texinfo-dummy-native',
'gnu-config-native', 'flex-native', 'lib32-binutils-cross-arm',
'libmpc-native', 'mpfr-native', 'gmp-native', 'zlib-native',
'libtool-native', 'xz-native', 'autoconf-native', 'attr-native',
'gettext-minimal-native', 'm4-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| abort()ing pseudo client by server request. See
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
| Check logfile:
/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/pseudo//pseudo.log
| Aborted (core dumped)
| WARNING: exit code 134 from a shell command.
| ERROR: Execution of
'/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/run.do_install.2725327'
failed with exit code 134
ERROR: Task
(virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/meta-blaze/recipes-example/testing-firmware/testing-firmware_0.1.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 6321 tasks of which 6317 didn't need to be
rerun and 1 failed.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61702): https://lists.yoctoproject.org/g/yocto/message/61702
Mute This Topic: https://lists.yoctoproject.org/mt/102605627/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] install: cannot create directory: File exists

2023-11-15 Thread MOHAMMED HASSAN
Hi guys,
So I am trying to load node js files in my image. I am able to load the
node_modules and package.json file, but when i try to load the
directory that contains multiple js files, i get the following *error*:

ERROR: lib32-testing-firmware-0.1-r0 do_install: Execution of
'/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/run.do_install.22011'
failed with exit code 1
ERROR: Logfile of failure stored in:
/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/log.do_install.22011
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/quilt/quilt-native_0.66.bb:do_populate_sysroot',
'virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/gcc/gcc-cross_9.3.bb:do_populate_sysroot',
'virtual:native:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
'virtual:native:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot',
'virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-devtools/gcc/gcc-runtime_9.3.bb:do_populate_sysroot',
'virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/poky/meta/recipes-core/glibc/glibc_2.31.bb:
do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native',
'lib32-gcc-cross-arm', 'pseudo-native', 'patch-native',
'lib32-gcc-runtime', 'lib32-glibc', 'lib32-linux-libc-headers',
'libmpc-native', 'mpfr-native', 'gnu-config-native', 'zlib-native',
'xz-native', 'flex-native', 'gmp-native', 'libtool-native',
'lib32-binutils-cross-arm', 'autoconf-native', 'texinfo-dummy-native',
'automake-native', 'attr-native', 'lib32-libgcc', 'gettext-minimal-native',
'm4-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
|















*install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/apiGateway.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/app.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/global.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/gpio.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/gsm.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/http.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/install.sh’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/mqtt.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/mqtt.js~’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/ota.sh’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/ota_se.sh’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/package-lock.json’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/package.json’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/udp.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/watchdog.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/wifi.js’:
File exists| install: cannot create directory
‘/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/Edge/wifi.js~’:
File exists*
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of
'/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/run.do_install.2201

Re: [yocto] install: cannot create directory: File exists

2023-11-15 Thread MOHAMMED HASSAN
> 
> 
> 
> man install:
> 
> -d, --directory
> treat all arguments as directory names; create all components of
> the specified directories
> 
> So you are trying to install all normal files (Edge/*) as directories (as
> you use -d). This then, as per error message message, will fail.
> 
> Maybe you meant -D (to create previous dirs)? Or just had it copied by
> mistake.
> 
> 

Thanks, I found my error. I am able to build now.

Now the only issue remains is why my files cant be stored in the /home/root 
directory?

If you can share some documentation or some solution then let me know.

Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61708): https://lists.yoctoproject.org/g/yocto/message/61708
Mute This Topic: https://lists.yoctoproject.org/mt/102622725/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] TI AM62x based EV charger platform with Pionix UI s/w Image build problem. #distro #poky #apt #bitbake

2023-11-27 Thread MOHAMMED HASSAN
On Mon, Nov 27, 2023 at 10:06 PM, Federico Pellegrin wrote:

> 
> 
> Hi,
> nodejs is very, *very*, heavy to build due to it's complex C++ code. I
> would suggest you to limit the number of parallel builds supported: this
> may slow down other (lighter) builds but will avoid going out of memory
> for heavy ones such as node.
> 
> This can be done by putting in your local configuration
> (build/conf/local.conf or replace "build" with your build directory)
> directives like:
> 
> BB_NUMBER_THREADS = '4'
> PARALLEL_MAKE = '-j 4'
> 
> (this limits to 4, you can play on this depending on number of cores and
> amount of RAM of course)
> 
> hth,
> Federico
> 
> 
> Il giorno mar 28 nov 2023 alle ore 07:00 < sairajl...@gmail.com > ha
> scritto:
> 
>> 
>> 
>> Hi team,
>> 
>> 
>> 
>> 
>> 
>> we are trying to build TI AM62x EVSE SDK referring to 
>> https://github.com/PionixPublic/ti-am62x-evse-sdk
>> ( https://github.com/PionixPublic/ti-am62x-evse-sdk ) we have tried
>> building in virtual machine and now we are trying to build in Linux  host
>> pc with 500gb of storage and 16gb ram but still bitbake runs till 99
>> percentage   and last module Nodejs takes forever to run system
>> experiences a freeze. Tried multiple times running the bitbake but still
>> problem remains same .
>> 
>> 
>> 
> 
> 
> 

I was able to build nodejs when I upgraded my RAM to 32GB. Upgrade your RAM.

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61766): https://lists.yoctoproject.org/g/yocto/message/61766
Mute This Topic: https://lists.yoctoproject.org/mt/102846254/21656
Mute #distro:https://lists.yoctoproject.org/g/yocto/mutehashtag/distro
Mute #poky:https://lists.yoctoproject.org/g/yocto/mutehashtag/poky
Mute #apt:https://lists.yoctoproject.org/g/yocto/mutehashtag/apt
Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Reg. Efficient methods to transfer yocto source file

2023-12-05 Thread MOHAMMED HASSAN
Hi guys,
So I have been copying and transferring yocto source files into different
partitions to test new features and to have a preexisting working build. I
generally just copy the files and I am aware that this will take a lot of
time. I was looking for an efficient way to transfer the source code as
later I will be transferring the code to my other team members as well. I
copy everything except the tmp directory.

Please share some efficient methods to transfer code.
Also is it good to use GIT to save entire source code?

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61811): https://lists.yoctoproject.org/g/yocto/message/61811
Mute This Topic: https://lists.yoctoproject.org/mt/103007903/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Update the yocto dunfell to latest version

2023-12-17 Thread MOHAMMED HASSAN
Hi guys,
Can you suggest some resources for me to update to the latest yocto dunfell
version. Currently I am using dunfell 3.1.11 and want to update to 3.1.29.
What could be the consequences?
Also If I manually update the nodejs folder to the latest one will it fetch
the latest nodejs files(example)?

Regards,
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61952): https://lists.yoctoproject.org/g/yocto/message/61952
Mute This Topic: https://lists.yoctoproject.org/mt/103238937/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Menuconfig saving erased after bitbake clean

2024-01-09 Thread MOHAMMED HASSAN
Hi guys,
I open menuconfig and add/remove some features, save and exit.
If I build using "bitbake linux-meson" the built image has all the features.
However If I use "bitbake linux-meson -c clean && bitbake linux-meson" ,
then all the menuconfig modifications are erased and the default
configuration is built.
What to do.


Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62117): https://lists.yoctoproject.org/g/yocto/message/62117
Mute This Topic: https://lists.yoctoproject.org/mt/103618090/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto kirstone bitbake failed

2024-02-26 Thread MOHAMMED HASSAN
Hi guys,
So I had earlier downloaded kirkstone and built an image . Later I deleted
the entire directory and moved to other works. Now I created a new
partition and tried to bitbake core-image-minimal.
But I get the error
[image: image.png]

Not sure why but even the source oe-init-build-env pointed to an older
yocto sdk(dunfell).

Please suggest what to do.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62602): https://lists.yoctoproject.org/g/yocto/message/62602
Mute This Topic: https://lists.yoctoproject.org/mt/104579162/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Update glib-2.0 from 2.7 to 2.8

2024-07-28 Thread MOHAMMED HASSAN
Hi guys,
I have kirkstone SDK with me that supports glib-2.0 version 2.70. I
currently require version 2.80 which I noticed is available in the main
branch of git. Do you think pulling the recipes and manually replacing the
file will resolve my issue. Or any other good methods I can try?

Thanks
Hassan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63580): https://lists.yoctoproject.org/g/yocto/message/63580
Mute This Topic: https://lists.yoctoproject.org/mt/107603886/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Update glib-2.0 from 2.7 to 2.8

2024-07-29 Thread MOHAMMED HASSAN
Well, I seem to be facing issue with the bluez stack. Though it builds
well, functionality wise I think it doesn’t  work as intended. So I wanted
to try building it on the board using the source code. Now the source code
wants glib-2 2.8 .

Also, on a second thought how do you guys work your way around in case a
particular package is outdated? Really curious!

Thanks

On Tue, 30 Jul 2024 at 12:03 AM, Alexander Kanavin 
wrote:

> You can try, but this is likely to unravel into a mass scale upgrade
> of half of oe-core recipes, and you're on your own trying to make it
> work. I would suggest simply moving to a tagged master milestone
> rather.
>
> Where is the requirement coming from?
>
> Alex
>
> On Mon, 29 Jul 2024 at 06:46, MOHAMMED HASSAN via
> lists.yoctoproject.org
>  wrote:
> >
> > Hi guys,
> > I have kirkstone SDK with me that supports glib-2.0 version 2.70. I
> currently require version 2.80 which I noticed is available in the main
> branch of git. Do you think pulling the recipes and manually replacing the
> file will resolve my issue. Or any other good methods I can try?
> >
> > Thanks
> > Hassan
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63591): https://lists.yoctoproject.org/g/yocto/message/63591
Mute This Topic: https://lists.yoctoproject.org/mt/107603886/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Update glib-2.0 from 2.7 to 2.8

2024-07-29 Thread MOHAMMED HASSAN
Well, I see your point. Thanks!

On Tue, Jul 30, 2024 at 8:10 AM Khem Raj  wrote:

>
>
> On Mon, Jul 29, 2024 at 5:23 PM MOHAMMED HASSAN via lists.yoctoproject.org
>  wrote:
>
>> Well, I seem to be facing issue with the bluez stack. Though it builds
>> well, functionality wise I think it doesn’t  work as intended. So I wanted
>> to try building it on the board using the source code. Now the source code
>> wants glib-2 2.8 .
>>
>> Also, on a second thought how do you guys work your way around in case a
>> particular package is outdated? Really curious!
>>
>
> This is subjective usually it’s best to keep using the version set that
> comes with a given release even if it is not latest release because it is
> integrated with the baseline of the packages from the given release and
> usually maintained releases do get security fixes etc over the life of the
> release so usually it ends up fine and you are with a large set of users so
> any issue you run into you may find good support in community
>
> On the other hand if you want to upgrade a recipe for a package to use
> another major version older or newer will mean you will have to own the
> integration part and there will be less users with such combinations so you
> will be stuck on doing the work your self. In some cases it’s worth it in
> some not so much
>
> Some leaf packages are easier to upgrade then some core libraries etc so
> your mileage may vary
>
>
>> Thanks
>>
>> On Tue, 30 Jul 2024 at 12:03 AM, Alexander Kanavin <
>> alex.kana...@gmail.com> wrote:
>>
>>> You can try, but this is likely to unravel into a mass scale upgrade
>>> of half of oe-core recipes, and you're on your own trying to make it
>>> work. I would suggest simply moving to a tagged master milestone
>>> rather.
>>>
>>> Where is the requirement coming from?
>>>
>>> Alex
>>>
>>> On Mon, 29 Jul 2024 at 06:46, MOHAMMED HASSAN via
>>> lists.yoctoproject.org
>>>  wrote:
>>> >
>>> > Hi guys,
>>> > I have kirkstone SDK with me that supports glib-2.0 version 2.70. I
>>> currently require version 2.80 which I noticed is available in the main
>>> branch of git. Do you think pulling the recipes and manually replacing the
>>> file will resolve my issue. Or any other good methods I can try?
>>> >
>>> > Thanks
>>> > Hassan
>>> >
>>> >
>>> >
>>>
>>
>> 
>>
>>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63596): https://lists.yoctoproject.org/g/yocto/message/63596
Mute This Topic: https://lists.yoctoproject.org/mt/107603886/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Linking stage error

2024-09-04 Thread MOHAMMED HASSAN
Hi guys,
I am trying to run a Makefile and add the binary to my arm64 yocto dunfell
build. The issue is
the linking stage throws generic ELF error. I have commented out compiler
related info in my Makefile but still face the issue. Please have a look
and point me in the right direction.

Initialising tasks: 100%
|##|
Time: 0:00:04
Sstate summary: Wanted 5 Found 0 Missed 5 Current 537 (0% match, 99%
complete)
NOTE: Executing Tasks
WARNING: QA Issue: PN: z3gatewayGPCombo is upper case, this can result in
unexpected behavior. [uppercase-pn]
WARNING: QA Issue: PN: z3gatewayGPCombo is upper case, this can result in
unexpected behavior. [uppercase-pn]
ERROR: z3gatewayGPCombo-0.1-r0 do_compile: Execution of
'/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/run.do_compile.137942'
failed with exit code 2
ERROR: Logfile of failure stored in:
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/log.do_compile.137942
Log data follows:
|







* DEBUG: Executing shell function do_compile| # No pre-build defined|
Linking ././Z3GatewayGPCombo| aarch64-poky-linux-ld: ././project/app.o:
Relocations in generic ELF (EM: 62)| aarch64-poky-linux-ld:
././project/app.o: Relocations in generic ELF (EM: 62)|
aarch64-poky-linux-ld: ././project/app.o: Relocations in generic ELF (EM:
62)| aarch64-poky-linux-ld: ././project/app.o: error adding symbols: file
in wrong format| make: *** [Makefile:157: Z3GatewayGPCombo.out] Error 1|
WARNING: exit code 2 from a shell command.*
| ERROR: Execution of
'/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/run.do_compile.137942'
failed with exit code 2
ERROR: Task
(/home/edula/yocto3.0/meta-blaze/recipes-example/z3gatewayGPCombo/z3gatewayGPCombo_0.1.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1782 tasks of which 1780 didn't need to be
rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds


Thanks
Hassan


z3gatewayGPCombo_0.1.bb
Description: Binary data


Makefile
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63783): https://lists.yoctoproject.org/g/yocto/message/63783
Mute This Topic: https://lists.yoctoproject.org/mt/108266063/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] Linking stage error

2024-09-05 Thread MOHAMMED HASSAN
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/plugin/byte_utilities/byte-utilities.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/silicon_labs/silabs_core/event_queue/event-queue.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/aes.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/constant_time.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/platform.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/platform_util.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/psa_crypto_client.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/psa_util.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/mbedtls/library/threading.c
Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/printf/printf.c









*Building
/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/simplicity_sdk/Z3GatewayGPCombo/../../simplicity_sdk/util/third_party/printf/src/iostream_printf.cLinking
././Z3GatewayGPCombo/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
././project/app.o: Relocations in generic ELF (EM:
62)/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
././project/app.o: Relocations in generic ELF (EM:
62)/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
././project/app.o: Relocations in generic ELF (EM:
62)/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.3.0/ld:
././project/app.o: error adding symbols: file in wrong formatcollect2:
error: ld returned 1 exit statusmake: *** [Makefile:158:
Z3GatewayGPCombo.out] Error 1WARNING: exit code 2 from a shell command.*
*ERROR: Execution of
'/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/run.do_compile.5763'
failed with exit code 2 *


*Regards,*
*Hassan*

On Wed, Sep 4, 2024 at 8:17 PM Khem Raj  wrote:

> On Wed, Sep 4, 2024 at 7:36 AM MOHAMMED HASSAN via
> lists.yoctoproject.org
>  wrote:
> >
> > Hi guys,
> > I am trying to run a Makefile and add the binary to my arm64 yocto
> dunfell build. The issue is
> > the linking stage throws generic ELF error. I have commented out
> compiler related info in my Makefile but still face the issue. Please have
> a look and point me in the right direction.
> >
> > Initialising tasks: 100%
> |##|
> Time: 0:00:04
> > Sstate summary: Wanted 5 Found 0 Missed 5 Current 537 (0% match, 99%
> complete)
> > NOTE: Executing Tasks
> > WARNING: QA Issue: PN: z3gatewayGPCombo is upper case, this can result
> in unexpected behavior. [uppercase-pn]
> > WARNING: QA Issue: PN: z3gatewayGPCombo is upper case, this can result
> in unexpected behavior. [uppercase-pn]
> > ERROR: z3gatewayGPCombo-0.1-r0 do_compile: Execution of
> '/home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/run.do_compile.137942'
> failed with exit code 2
> > ERROR: Logfile of failure stored in:
> /home/edula/yocto3.0/build/tmp/work/aarch64-poky-linux/z3gatewayGPCombo/0.1-r0/temp/log.do_compile.137942
> > Log data follows:
> > | DEBUG: Executing shell function do_compile
> > | # No pre-build defined
> > | Lin