Re: How to enable graphics acceleration on qemux86-64?
Manuel Wagesreither
Hi Alex, Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin:
Interesting. Things don't work on both my Debian Buster machines. How does opengl get set in qemu-system-native? Am Yocto novice and don't speak Python. Am using poky repo on tag dunfell-23.0.10 = 2a848e9507. Here's my complete test results: * `runqemu kvm slirp core-image-weston` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting` * `runqemu kvm slirp sdl core-image-minimal` fails with `Failed to run qemu: Could not initialize SDL(x11 not available) - exiting` * `runqemu kvm slirp sdl gl core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: OpenGL support is disabled` * `runqemu kvm slirp gtk core-image-minimal` fails with `Failed to run qemu: qemu-system-x86_64: Display 'gtk' is not available.` How would I enable gtk frontend in poky? Thanks, Manuel
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.3.3 (hardknott-25.0.3) is Released --> When is hardknott's final release: 3.3.4 ?
Sending to Stephen's gmail address.
toggle quoted messageShow quoted text
On 2021-10-13 12:52 p.m., Randy MacLeod wrote:
When will we be doing hardknott's final release: 3.3.4 ? --
# Randy MacLeod # Wind River Linux
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Anything ?, I have yet to resolve this.
toggle quoted messageShow quoted text
-----Original Message-----
From: Monsees, Steven C (US) Sent: Wednesday, October 13, 2021 9:03 AM To: 'Mittal, Anuj' <anuj.mittal@...>; 'yocto@...' <yocto@...> Subject: RE: [yocto] #zeus meta-intel Are there any patches required for these components (igc, opencl-clang, and intel-compute-runtime) ? -----Original Message----- From: Monsees, Steven C (US) Sent: Wednesday, October 13, 2021 7:13 AM To: 'Mittal, Anuj' <anuj.mittal@...>; yocto@... Subject: RE: [yocto] #zeus meta-intel Anuj: I rebuilt the entire image (but did not delete the state_cache)... I am building meta-clang (zeus based, I believe it is 9.0.1). Steve -----Original Message----- From: Mittal, Anuj <anuj.mittal@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... Subject: Re: [yocto] #zeus meta-intel External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang? Thanks, Anuj On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.3.3 (hardknott-25.0.3) is Released --> When is hardknott's final release: 3.3.4 ?
When will we be doing hardknott's final release: 3.3.4 ?
Is this info documented in the wiki: I don't see it in either of these links: https://wiki.yoctoproject.org/wiki/Releases https://wiki.yoctoproject.org/wiki/Special:RecentChanges ../Randy
|
|
[PATCH yocto-autobuilder-helper] scripts/collect-results: publish everything in tmp/log/oeqa/
Alexander Kanavin
From: Alexander Kanavin <alex@...>
In addition to the testresult json, testimage class now also provides the testimage task log and qemu console output log which can be useful for debugging test failures or even checking qemu test runs when failures did not happen. Rather than duplicate specific file/folder names, let's copy all that is available, and define what is published in the testimage class itself (with appropriate folder structure if/when needed). At the moment there's just three files, and they are copied into folders named after image names, so there's no clutter or risk of mixing them up with unrelated logs. [YOCTO #14518] Signed-off-by: Alexander Kanavin <alex@...> --- scripts/collect-results | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/scripts/collect-results b/scripts/collect-results index 93834d6..3663330 100755 --- a/scripts/collect-results +++ b/scripts/collect-results @@ -3,11 +3,9 @@ WORKDIR=$1 DEST=$2 target=$3 -RESFILE=$WORKDIR/tmp/log/oeqa/testresults.json - -if [ -e $RESFILE ]; then - mkdir -p $DEST/$target - cp $WORKDIR/tmp/log/oeqa/testresults.json $DEST/$target/ +mkdir -p $DEST +if [ -e $WORKDIR/tmp/log/oeqa/ ]; then + cp -rf $WORKDIR/tmp/log/oeqa/ $DEST/$target fi if [ -e $WORKDIR/buildhistory ]; then -- 2.31.1
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Are there any patches required for these components (igc, opencl-clang, and intel-compute-runtime) ?
toggle quoted messageShow quoted text
-----Original Message-----
From: Monsees, Steven C (US) Sent: Wednesday, October 13, 2021 7:13 AM To: 'Mittal, Anuj' <anuj.mittal@...>; yocto@... Subject: RE: [yocto] #zeus meta-intel Anuj: I rebuilt the entire image (but did not delete the state_cache)... I am building meta-clang (zeus based, I believe it is 9.0.1). Steve -----Original Message----- From: Mittal, Anuj <anuj.mittal@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... Subject: Re: [yocto] #zeus meta-intel External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang? Thanks, Anuj On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Anuj:
toggle quoted messageShow quoted text
I rebuilt the entire image (but did not delete the state_cache)... I am building meta-clang (zeus based, I believe it is 9.0.1). Steve
-----Original Message-----
From: Mittal, Anuj <anuj.mittal@...> Sent: Tuesday, October 12, 2021 10:10 PM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... Subject: Re: [yocto] #zeus meta-intel External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. Did you build everything with this compiler from start? Is opencl-clang building with the right LLVM lib from meta-clang? Thanks, Anuj On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:
|
|
[meta-security][PATCH] sssd: re-package to fix QA issues
kai
From: Kai Kang <kai.kang@...>
It packages all file in ${libdir} to package sssd, including the .so symlink files. Then it causes QA issues: | ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps] | ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps] So re-package sssd then the .so symlink files and .pc files are packaged to sssd-dev which should be. File ${libdir}/libsss_sudo.so is not a symlink file but packaged to sssd-dev too. Then causes another QA issue: | ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: -dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf] So create a new sub-package libsss_sudo to package file libsss_sudo.so and make sssd rdepends on it. Signed-off-by: Kai Kang <kai.kang@...> --- recipes-security/sssd/sssd_2.5.2.bb | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb index 76d6e03..da1a5c3 100644 --- a/recipes-security/sssd/sssd_2.5.2.bb +++ b/recipes-security/sssd/sssd_2.5.2.bb @@ -125,10 +125,12 @@ SYSTEMD_SERVICE:${PN} = " \ " SYSTEMD_AUTO_ENABLE = "disable" -FILES:${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss*.so" -FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la" - -# The package contains symlinks that trip up insane -INSANE_SKIP:${PN} = "dev-so" - -RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam" +PACKAGES =+ "libsss_sudo" +FILES:${PN} += "${base_libdir}/security/pam_sss*.so \ + ${datadir}/dbus-1/system-services/*.service \ + ${libdir}/krb5/* \ + ${libdir}/ldb/* \ + " +FILES:libsss_sudo = "${libdir}/libsss_sudo.so" + +RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam libsss_sudo" -- 2.17.1
|
|
Re: Node-red and Wifi
Josef Holzmayr
Brutally honest: Yes it can. No you won't be able to do it without reading the docs. <donald@...> schrieb am Mi., 13. Okt. 2021, 08:51:
I am looking at various distributions to move to from my existing one - without wanting to wade through another lots of documentation - can the Yocto buid
|
|
Node-red and Wifi
donald@...
I am looking at various distributions to move to from my existing one - without wanting to wade through another lots of documentation - can the Yocto buid
1) be configured to act as a WiFi access point - with natting 2) run node-red I will be running on an Armbian quadcore.
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.rc1)
Teoh, Jay Shen
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion is next Monday, Oct 18. Thanks, Jay
-----Original Message-----
|
|
Re: util-linux and --enable-raw with recent kernels
Federico Pellegrin
Thanks Khem! Indeed I checked on master but got cheated by the web git interface and I was looking at an older commit :-/ Glad it is the right way to go and already solved on master! Cheers, Federico
Il giorno mar 12 ott 2021 alle ore 18:55 Khem Raj <raj.khem@...> ha scritto:
|
|
Re: #zeus meta-intel
#zeus
Anuj Mittal
Did you build everything with this compiler from start? Is opencl-clang
toggle quoted messageShow quoted text
building with the right LLVM lib from meta-clang? Thanks, Anuj
On Tue, 2021-10-12 at 17:15 +0000, Monsees, Steven C (US) wrote:
|
|
Re: #zeus meta-intel
#zeus
Monsees, Steven C (US)
Anuj:
toggle quoted messageShow quoted text
I picked up the tarball for for the baseline dunfell tools platform to update host tools... I am seeing it compile cleaner but for one issue causng ld to fail: /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >' Isn't LLVM brought in along with clang under meta-clang ? Is there a missing build dependency ? Thanks, Steve Build excerpt showing multiple " undefined reference to `vtable " errors... /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::~opt()': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::OptionValue()': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601: undefined reference to `vtable for llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::opt<llvm::cl::FormattingFlags, llvm::cl::desc, llvm::cl::initializer<char [2]> >(llvm::cl::FormattingFlags const&, llvm::cl::desc const&, llvm::cl::initializer<char [2]> const&)': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::parser(llvm::cl::Option&)': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072: undefined reference to `vtable for llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::~opt()': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1331: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::OptionValue()': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601: undefined reference to `vtable for llvm::cl::OptionValue<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >::opt<char [9], llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407: undefined reference to `vtable for llvm::cl::opt<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, false, llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >' /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld: IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function `llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::parser(llvm::cl::Option&)': /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072: undefined reference to `vtable for llvm::cl::parser<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >' collect2: error: ld returned 1 exit status
-----Original Message-----
From: yocto@... <yocto@...> On Behalf Of Anuj Mittal Sent: Tuesday, October 12, 2021 10:43 AM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... Subject: Re: [yocto] #zeus meta-intel External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote: g++: error: unrecognized command line option ‘-std=c++14’It looks like the gcc version is too old on your host for this to work. Thanks, Anuj
|
|
Re: util-linux and --enable-raw with recent kernels
On 10/12/21 9:27 AM, Federico Pellegrin wrote:
Hello,you might want to use latest master, fix that you might find useful is https://git.openembedded.org/openembedded-core/commit/?id=7f577c10913104860121f682b9b3754870c4db23 After a bit or research I believe it is due to:
|
|
util-linux and --enable-raw with recent kernels
Federico Pellegrin
Hello, Running on a quite recent kernel (5.14.10 from Fedora 34) I've came across a problem when building util-linux (2.35.2) native, namely in the configure phase: configure: error: raw selected, but required raw.h header file not available After a bit or research I believe it is due to: Which is related to the change in the recent kernels here: where the raw.h file was indeed removed. As per first link it may not be obvious to fix, and don't see an upstream fix for it, but from the Yocto perspective my current workaround is basically just to remove "--enable-raw" from the EXTRA_OECONF to disable the raw feature. While the whole image seemed to build fine with this, I'm not very sure if that configuration option had a precise use (which maybe it's being skipping in my specific build) or not, so I wanted to ask the experts if there is any opinion on this and/or should I do a merge request that removes it to handle this problem, at least until there is a better solution upstream in util-linux? Many thanks, Federico
|
|
Yocto Project Status WW41`21
Stephen Jolley
Current Dev Position: YP 3.4 M4 Next Deadline: 29th Oct. 2021 YP 3.4 M4 release
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.4 Milestone Dates:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
Re: #zeus meta-intel
#zeus
Anuj Mittal
On Tue, 2021-10-12 at 12:43 +0000, Monsees, Steven C (US) wrote:
g++: error: unrecognized command line option ‘-std=c++14’It looks like the gcc version is too old on your host for this to work. Thanks, Anuj
|
|
Re: How to include PostgreSQL development stuff in SDK?
tboeckel
Can anybody please help me with this issue? I am completely out of ideas what I am missing or doing wrong.
Mit freundlichem Gruß
best regards iNOEX GmbH Thore Böckelmann Software Design Mit
freundlichen Grüßen / Kind regards
iNOEX GmbH | Maschweg 70 | 49324 Melle | Germany | www.inoex.de
FON +49 5422 60507-958 | FAX +49 5422 60507-101
iNOEX GmbH
Geschaeftsfuehrer / Managing Director: Martin Deters, Jan
Lohoff Bitte beachten Sie die Datenschutzinformationen Von: Böckelmann, Thore <thore.boeckelmann@...>
Gesendet: Samstag, 2. Oktober 2021 17:10 An: yocto@... <yocto@...> Betreff: How to include PostgreSQL development stuff in SDK?
Hi everybody!
I successfully built an image for an ARM based system running a PostgreSQL server and client by adding the packages "postgresql" and "postgresql-client". However, so far I failed to make the development stuff (libpq-fe.h, pg_config, etc) available in the generated
SDK.
Usuallly one uses pg_config to obtain the required include path (pg_config --includedir), the required compiler flags for C and C++ (pg_config --cflags and pg_config --cppflags) as well as the required linker flags (pg_config --libdir and pg_config --ldflags).
However, I get the warning during compilation of my own programs:
cc1plus: warning: include location "/usr/include/postgresql" is unsafe for cross-compilation [-Wpoison-system-directories]
Obviously the native pg_config binary of my Ubuntu system is called and hence causes references to the local installation of the libpq-dev package of my Ubuntu system
instead of a pg_config binary provided by the SDK. Even worse, the SDK just includes the pg_config binary for the ARM platform, but not for x86_64.
The only way to silence these warnings is to include -Wno-poison-system-directories in my compiler flags. But this is something I really like to avoid. Who knows
whether the PostgreSQL development stuff of my local Ubuntu system will always be compatible to the one for the ARM system?
Unfortunately I had no luck including the PostgreSQL development stuff in the SDK. I already tried 'TOOLCHAIN_HOST_TASK_append
= " nativesdk-postgresql"', but this ends in an error message like this:
ERROR: Nothing RPROVIDES 'nativesdk-postgresql' (but /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/meta/buildtools-tarball.bb, /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/meta/uninative-tarball.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'nativesdk-postgresql' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nativesdk-postgresql']
ERROR: Required build target 'fsl-image-qt5' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-qt5', 'buildtools-tarball', 'nativesdk-postgresql']
Adding 'PACKAGECONFIG_append_pn-nativesdk += " postgresql"' also does not cause the x86_64 binary of pg_config to be included in the SDK. I assume this causes
the ARM binary to be included, but this cannot be used on an x86_64 system.
I searched lots of sites for a solution already, but so far I only found hints how to add packages in general, but nothing in respect to this specific issue.
Can anybody please point out what I am doing wrong or what I need to change to solve this issue?
Many thanks in advance!
Mit freundlichem Gruß
best regards iNOEX GmbH Thore Böckelmann Software Design
Mit freundlichen Grüßen / Kind regards
iNOEX GmbH | Maschweg 70 | 49324 Melle | Germany | www.inoex.de
FON +49 5422 60507-958 | FAX +49 5422 60507-101
iNOEX GmbH
Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff Bitte beachten Sie die Datenschutzinformationen
|
|
Re: building the kernel's usbipd daemon
Bruce Ashfield
On Tue, Oct 12, 2021 at 12:33 AM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...> wrote: My intent was just to show how you'd get the source from whatever kernel you are building, meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bbAssuming that you don't need to patch the sources directly, any of those would likely work ... depending on the dependencies and options of what tool you are building. Bruce
-- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
|
|