Ka-Ro's Yocto layer for NXP i.MX Processors based boards.
See the official, full documentation here: https://karo-electronics.github.io/docs/yocto-guide/nxp/index.html
https://www.karo-electronics.de
Contact support: [email protected]
Hi,
I'm trying to build an image for the tx6s-8134 board , meta-karo-nxp rev: 4.14.98-2.2.0-sumo . When building according to the instructions: https://karo-electronics.github.io/docs/yocto-guide/yocto-sumo-guide/BuildTX6.html, throws the error:
ERROR: bison-native-3.0.4-r0 do_compile: oe_runmake failed
ERROR: bison-native-3.0.4-r0 do_compile: Function failed: do_compile (log file is located at / home / armsdk / KARO / YOCTO / karo / build-tx6s / tmp / work / x86_64-linux / bison-native / 3.0.4-r0 / temp / log.do_compile.112188)
ERROR: Logfile of failure stored in: /home/armsdk/KARO/YOCTO/karo/build-tx6s/tmp/work/x86_64-linux/bison-native/3.0.4-r0/temp/log.do_compile.112188
I find patch to yocto-poky: https://marc.info/?l=openembedded-core&m=154715365203505&q=p4 . More info: https://marc.info/?l=openembedded-core&m=154715365203505&w=2
This is a problem with YOCTO-poky, maybe you could add this information to README
I am trying build my distro with meta-karo-nxp layer, but it fail because of files/fs-perms-karo.txt. I believe this file should be part of meta-karo-nxp-distro repo and FILESYSTEM_PERMS_TABLES should be part of distro too, not a tx8m-base.inc
File: '/home/builder/yocto/output/build/../../input/poky/meta/classes/package.bbclass', lineno: 740, function: _procgid
0736: return -1
0737: elif gid.isdigit():
0738: return int(gid)
0739: else:
*** 0740: return grp.getgrnam(gid).gr_gid
0741:
0742: # Use for debugging the entries
0743: def __str__(self):
0744: if self.link:
Exception: KeyError: "getgrnam(): name not found: 'utmp'"
ERROR: Logfile of failure stored in: /home/builder/yocto/output/build/tmp-glibc/work/aarch64-oe-linux/linux-libc-headers/5.2-r0/temp/log.do_package.84
ERROR: Task (/home/builder/yocto/output/build/../../input/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.2.bb:do_package) failed with exit code '1'
I found that 5.15.32 do not have CONFIG_USB_EHCI_MXC option and you set it in mx8mm_defconfig
Did you mean CONFIG_USB_EHCI_FSL ?
meta-karo-nxp/recipes-bsp/imx-mkimage/imx-boot_1.0.bb
requires recipes-bsp/imx-seco/imx-seco.inc
but I can't find this file in any of
LAYERDEPENDS_karo-nxp
When I try to build my Build Configuration : #1
ERROR: elfutils-native-0.170-r0 do_compile: oe_runmake failed
ERROR: elfutils-native-0.170-r0 do_compile: Function failed: do_compile (log file is located at /home/armsdk/KARO/YOCTO/karo/build-tx6s-8134/tmp/work/x86_64-linux/elfutils-native/0.170-r0/temp/log.do_compile.889320)
ERROR: Logfile of failure stored in: /home/armsdk/KARO/YOCTO/karo/build-tx6s-8134/tmp/work/x86_64-linux/elfutils-native/0.170-r0/temp/log.do_compile.889320
Information at the end of the terminal:
In file included from ../config.h:125,
| from ../../elfutils-0.170/libelf/elf32_fsize.c:31,
| from ../../elfutils-0.170/libelf/elf64_fsize.c:31:
| ../../elfutils-0.170/libelf/libelfP.h:47:30: error: ‘__elf64_msize’ specifies less restrictive attribute than its target ‘elf64_fsize’: ‘const’ [-Werror=missing-attributes]
| 47 | #define __elfw2_(Bits, Name) __elf##Bits##_##Name
| | ^~~~~
| ../../elfutils-0.170/lib/eu-config.h:60:26: note: in definition of macro ‘strong_alias’
| 60 | extern __typeof (name) aliasname __attribute__ ((alias (#name)));
| | ^~~~~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:68:1: note: in expansion of macro ‘local_strong_alias’
| 68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS, msize))
| | ^~~~~~~~~~~~~~~~~~
| ../../elfutils-0.170/libelf/libelfP.h:52:29: note: in expansion of macro ‘__elfw2_’
| 52 | #define __elfw2(Bits, Name) __elfw2_(Bits, Name)
| | ^~~~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:68:47: note: in expansion of macro ‘__elfw2’
| 68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS, msize))
| | ^~~~~~~
| In file included from ../../elfutils-0.170/libelf/elf32_fsize.c:35,
| from ../../elfutils-0.170/libelf/elf64_fsize.c:31:
| ../../elfutils-0.170/libelf/libelfP.h:48:28: note: ‘__elf64_msize’ target declared here
| 48 | #define elfw2_(Bits, Name) elf##Bits##_##Name
| | ^~~
| ../../elfutils-0.170/libelf/libelfP.h:53:27: note: in expansion of macro ‘elfw2_’
| 53 | #define elfw2(Bits, Name) elfw2_(Bits, Name)
| | ^~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:43:1: note: in expansion of macro ‘elfw2’
| 43 | elfw2(LIBELFBITS, fsize) (Elf_Type type, size_t count, unsigned int version)
| | ^~~~~
| In file included from ../config.h:125,
| from ../../elfutils-0.170/libelf/elf32_fsize.c:31:
| ../../elfutils-0.170/libelf/libelfP.h:47:30: error: ‘__elf32_msize’ specifies less restrictive attribute than its target ‘elf32_fsize’: ‘const’ [-Werror=missing-attributes]
| 47 | #define __elfw2_(Bits, Name) __elf##Bits##_##Name
| | ^~~~~
| ../../elfutils-0.170/lib/eu-config.h:60:26: note: in definition of macro ‘strong_alias’
| 60 | extern __typeof (name) aliasname __attribute__ ((alias (#name)));
| | ^~~~~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:68:1: note: in expansion of macro ‘local_strong_alias’
| 68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS, msize))
| | ^~~~~~~~~~~~~~~~~~
| ../../elfutils-0.170/libelf/libelfP.h:52:29: note: in expansion of macro ‘__elfw2_’
| 52 | #define __elfw2(Bits, Name) __elfw2_(Bits, Name)
| | ^~~~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:68:47: note: in expansion of macro ‘__elfw2’
| 68 | local_strong_alias (elfw2(LIBELFBITS, fsize), __elfw2(LIBELFBITS, msize))
| | ^~~~~~~
| In file included from ../../elfutils-0.170/libelf/elf32_fsize.c:35:
| ../../elfutils-0.170/libelf/libelfP.h:48:28: note: ‘__elf32_msize’ target declared here
| 48 | #define elfw2_(Bits, Name) elf##Bits##_##Name
| | ^~~
| ../../elfutils-0.170/libelf/libelfP.h:53:27: note: in expansion of macro ‘elfw2_’
| 53 | #define elfw2(Bits, Name) elfw2_(Bits, Name)
| | ^~~~~~
| ../../elfutils-0.170/libelf/elf32_fsize.c:43:1: note: in expansion of macro ‘elfw2’
| 43 | elfw2(LIBELFBITS, fsize) (Elf_Type type, size_t count, unsigned int version)
| | ^~~~~
| cc1: all warnings being treated as errors
| make[2]: *** [Makefile:712: elf64_fsize.o] Error 1
| make[2]: *** Waiting for unfinished jobs....
| cc1: all warnings being treated as errors
| make[2]: *** [Makefile:712: elf32_fsize.o] Error 1
| make[1]: *** [Makefile:478: all-recursive] Error 1
| make: *** [Makefile:394: all] Error 2
| ERROR: oe_runmake failed
| WARNING: /home/armsdk/KARO/YOCTO/karo/build-tx6s-8134/tmp/work/x86_64-linux/elfutils-native/0.170-r0/temp/run.do_compile.889320:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /home/armsdk/KARO/YOCTO/karo/build-tx6s-8134/tmp/work/x86_64-linux/elfutils-native/0.170-r0/temp/log.do_compile.889320)
ERROR: Task (virtual:native:/home/armsdk/KARO/YOCTO/karo/sources/poky/meta/recipes-devtools/elfutils/elfutils_0.170.bb:do_compile) failed with exit code '1'
To around the error use elfutils from Yocto-Poky, branch thud.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.