Re: [yocto] [OE-core] QA cycle report for 2.7 RC2
Hi Armin, From: akuster808 Sent: Friday, 26 April, 2019 10:30 PM To: Jain, Sangeeta ; 'yocto@yoctoproject.org' ; Eggleton, Paul ; 'richard.pur...@linuxfoundation.org' ; 'Michael Halstead' ; Erway, Tracey M ; 'sjolley.yp...@gmail.com' ; openembedded-c...@lists.openembedded.org Subject: Re: [OE-core] QA cycle report for 2.7 RC2 Sangeeta, On 4/25/19 11:27 PM, Jain, Sangeeta wrote: QA cycle report for 2.7 RC2: 1. No high milestone defects. 2. Test results are available at following location: *For results of all automated tests, please refer to results at public AB [1]. *For other test results, refer to attachment [2]. *For test report for test cases run by Intel and WR team, refer attachment [3] Since "compliance-test.compliance-test.LSB_subset_test_suite" was run, can you share the changes made to /opt/lsb-test/session file? For "compliance-test.compliance-test.LSB_subset_test_suite", we follow the procedure as mentioned at https://wiki.yoctoproject.org/wiki/BSP_Test_Plan Under compliance section. Changes to /opt/lsb-test/session file are also handled by script "compliance_test.py" (link to which you can find in wiki page mentioned) Can I get clarification on how "compliance-test.compliance-test.stress_test_-_ltp_-Beaglebone" was run? To run stress test, we use "./runltp -f crashme" command. Stress test for Beaglebone is run by Windriver team. Adding Yi Zhao in mail. Regards, Armin *For full test report, refer attachment [4] 1. No new defects are found in this cycle. 2. No existing issues observed in this release 3. No ptests are failing in this release which were passing in previous release. No timeout issues. QA Hint: One failure was observed on public AB: testseries | result_id : qemuppc | oeselftest_centos-7_qemuppc_20190414221329 runqemu.QemuTest.test_qemu_can_shutdown No bug filed for this issue, as it appears to be an intermittent failure and worked on rc1 test run. === Links Link to testresults: [1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2/testresults/ [2] - 2.7_RC2_results_merged.zip [3] - 2.7_ rc2_intel_wr_merged_report [4] - 2.7 _rc2_full_report Thanks & Regards, Sangeeta Jain -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
Thank you very much Andreas, that fixed it, so much to learn :-).
Appreciate your helps.
- jupiter
On 5/2/19, Andreas Müller wrote:
> On Thu, May 2, 2019 at 12:32 AM JH wrote:
>>
>> Hi Andreas,
>>
>> It was my program, it has been compiled for weeks without any issues
>> until I added an #include , despite the glib-2.0 was defined
>> in the recipe, the do_compile() stopped at following errors, I can see
>> glib-2.0 was built in build and image directory, I can see glib.h was
>> in build and image directory, is it a basic principle if a package
>> library was defined in DEPENDS, the bitback should automatically find
>> the header files and library links? Why it still complained no such
>> file?
>>
>> DEPENDS += "glib-2.0"
>> RDEPENDS += "glib-2.0"
> ^ In case your program links successfully this can go
>
> you could write
>
> do_compile() {
> CFLAGS="${CFLAGS} `pkg-config --cflags glib-2.0`"
> LDFLAGS="${LDFLAGS} `pkg-config --libs glib-2.0`"
> oe_runmake -e
> }
>
> Or similar in your Makefile
>
> And and don't forget
>
> inherit pkgconfig
>
> in your recipe
>
> Andreas
>
>
>>
>> do_compile() {
>> oe_runmake -e
>> }
>>
>>
>> fatal error: glib.h: No such file or directory #include
>>
>>^~~~
>> compilation terminated.
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jupiter
>>
>>
>>
>>
>> On 5/1/19, Andreas Müller wrote:
>> > On Wed, May 1, 2019 at 12:35 PM JH wrote:
>> >>
>> >> Thanks Richard, where to run pkg-config? If I run pkg-config in the
>> >> host, it pointed to host Ubuntu package which is different to the
>> >> cross compiler.
>> >>
>> >> On 5/1/19, Richard Purdie wrote:
>> >> > On Wed, 2019-05-01 at 10:43 +1000, JH wrote:
>> >> >> Hi,
>> >> >>
>> >> >> I added glib-2.0 to DEPENDS but it still could find the glib.h,
>> >> >> what
>> >> >> I
>> >> >> could be missing here?
>> >> >>
>> >> >> fatal error: glib.h: No such file or directory
>> >> >> > #include
>> >> >> > ^~~~
>> >> >> > compilation terminated.
>> >> >
>> >> > You probably need to use pkg-config to find out which CFLAGS to use
>> >> > for
>> >> > glib-2.0...
>> >> >
>> > Maybe I missed something but there is not much information about what
>> > you are trying to build. Starts with build system: autotools / cmake /
>> > meson / qmake / waf?
>> >
>> > Is there a place to look into the recipe? That might make support
>> > easier.
>> >
>> > Andreas
>> >
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH] layer.conf: Add LAYERSERIES_COMPAT for warrior
From: Armin Kuster Signed-off-by: Armin Kuster --- meta-cgl-common/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/conf/layer.conf b/meta-cgl-common/conf/layer.conf index bf2c93e..894d6c4 100644 --- a/meta-cgl-common/conf/layer.conf +++ b/meta-cgl-common/conf/layer.conf @@ -13,6 +13,6 @@ BBFILE_PRIORITY_cgl-common = "7" LAYERDEPENDS_cgl-common = "core openembedded-layer networking-layer perl-layer filesystems-layer security selinux" -LAYERSERIES_COMPAT_cgl-common = "thud" +LAYERSERIES_COMPAT_cgl-common = "warrior" require conf/distro/include/cgl_common_security_flags.inc -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
On Thu, May 2, 2019 at 12:32 AM JH wrote:
>
> Hi Andreas,
>
> It was my program, it has been compiled for weeks without any issues
> until I added an #include , despite the glib-2.0 was defined
> in the recipe, the do_compile() stopped at following errors, I can see
> glib-2.0 was built in build and image directory, I can see glib.h was
> in build and image directory, is it a basic principle if a package
> library was defined in DEPENDS, the bitback should automatically find
> the header files and library links? Why it still complained no such
> file?
>
> DEPENDS += "glib-2.0"
> RDEPENDS += "glib-2.0"
^ In case your program links successfully this can go
you could write
do_compile() {
CFLAGS="${CFLAGS} `pkg-config --cflags glib-2.0`"
LDFLAGS="${LDFLAGS} `pkg-config --libs glib-2.0`"
oe_runmake -e
}
Or similar in your Makefile
And and don't forget
inherit pkgconfig
in your recipe
Andreas
>
> do_compile() {
> oe_runmake -e
> }
>
>
> fatal error: glib.h: No such file or directory #include
>
>^~~~
> compilation terminated.
>
> Thank you.
>
> Kind regards,
>
> - jupiter
>
>
>
>
> On 5/1/19, Andreas Müller wrote:
> > On Wed, May 1, 2019 at 12:35 PM JH wrote:
> >>
> >> Thanks Richard, where to run pkg-config? If I run pkg-config in the
> >> host, it pointed to host Ubuntu package which is different to the
> >> cross compiler.
> >>
> >> On 5/1/19, Richard Purdie wrote:
> >> > On Wed, 2019-05-01 at 10:43 +1000, JH wrote:
> >> >> Hi,
> >> >>
> >> >> I added glib-2.0 to DEPENDS but it still could find the glib.h, what
> >> >> I
> >> >> could be missing here?
> >> >>
> >> >> fatal error: glib.h: No such file or directory
> >> >> > #include
> >> >> > ^~~~
> >> >> > compilation terminated.
> >> >
> >> > You probably need to use pkg-config to find out which CFLAGS to use for
> >> > glib-2.0...
> >> >
> > Maybe I missed something but there is not much information about what
> > you are trying to build. Starts with build system: autotools / cmake /
> > meson / qmake / waf?
> >
> > Is there a place to look into the recipe? That might make support easier.
> >
> > Andreas
> >
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
On Wed, 1 May 2019 at 23:33, JH wrote: > It was my program, it has been compiled for weeks without any issues > until I added an #include , despite the glib-2.0 was defined > in the recipe, the do_compile() stopped at following errors, I can see > glib-2.0 was built in build and image directory, I can see glib.h was > in build and image directory, is it a basic principle if a package > library was defined in DEPENDS, the bitback should automatically find > the header files and library links? Why it still complained no such > file? Because that's not how glib works. https://developer.gnome.org/glib/stable/glib-compiling.html Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto-announce] [ANNOUNCEMENT] Yocto Project 2.7 (warrior 21.0.0) Released
Hello, We are pleased to announce the latest release of the Yocto Project 2.7 (warrior-21.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/RELEASENOTES Full test report is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/testreport.txt Thank you for everyone's contributions to this release. Sincerely, Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com --- yocto-2.7 Release Notes --- -- Downloads -- Release Name: poky-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 0e392026ffefee098a890c39bc3ca1f697bacb52 md5: 5b9ea9d4017f85148b1476e026ac8544 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 Release Name: oecore-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: f571b188177788d8ed0a7f3efe3569f153b1b0d3 md5: cb1eafef6c055838afddc505e6df7a74 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/oecore-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/oecore-warrior-21.0.0.tar.bz2 Release Name: meta-mingw-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 10695afe8cd406844e0d0dd868c11677e07557d4 md5: d69c92745ea9959f3bb7a5d35f4b9fbc Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-mingw-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-mingw-warrior-21.0.0.tar.bz2 Release Name: meta-intel-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: cd2c3bfca97655999cbde645b73be712675dba92 md5: 3c300918d246c9902150dc2e2b9dd756 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-intel-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-intel-warrior-21.0.0.tar.bz2 Release Name: meta-gplv2-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 106ba6d2a4d08a276205c305f8485d701fe8a8f3 md5: 94bb8a8ed9b11d2693aaa373f93625dd Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-gplv2-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-gplv2-warrior-21.0.0.tar.bz2 Release Name: bitbake-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: cb185efe9e88cfb12b7a3fd08f3086ca0b69c8e2 md5: 4c69bb5e8ffb29bb40bb105920838441 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/bitbake-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/bitbake-warrior-21.0.0.tar.bz2 --- New Features / Enhancements --- * Linux kernel 5.0/4.19, gcc 8.3, glibc 2.29 and ~230 other recipe upgrades * Added support for virgl GL acceleration within QEMU / runqemu * Added support SLiRP user-space networking in runqemu for easier networking within containers * New "packagegroup-core-base-utils" packagegroup to easily bring in full-featured versions of standard system utilities * New "ccmake" class to enable the CMake curses UI * New "mcextend" class to enable easily creating multiconfig recipe variants * New "xmlcatalog" class to update the XML catalogue * New recipes: eglinfo-wayland, inetutils, libdazzle, libjitterentropy, libmodulemd, libpsl, vim, virglrenderer * Architecture-specific changes: - linux-yocto: add baseline ARC support - qemuarm64: Add graphics support - qemuarm: Swap for an arm7ve (A15) configuration - qemumips64: change tune to mips64r2 - qemumips: Enable the poweroff driver - arch-armv7*.inc: Add Cortex vfpv4-d16 support - arch-armv8a.inc: add tune include for armv8 - arm-tunes: Remove -march option if mcpu is already added - ThunderX: update the armv8a rules - tune-cortexa32: add tunes for ARM Cortex-A32 - tune-cortexa35: add tunes for ARM Cortex-A35 - tune-cortexa53: add tunes for ARM Cortex-A53 - tune-cortexa5.inc: Add tune options for vfpv4 - tune-cortexa72: add tunes for ARM Cortex-A72 - linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions - gcc: Enable secureplt for powerpc64 target too - goarch: Add riscv64 - gstreamer: Add RISC-V support - kernel-fitimage: support RISC-V - lib/oe/elf.py: Add powerpc64 architecture definition for musl - webkitgtk: Enable building for ARC architecture - linux-yocto: pinctrl config change for cannonlake - mdadm: add mdmon service to support Intel VROC - mesa: Allow building the r600 driver - locale: Allow usage of cross-localedef for ARC - Added armeb support to meson class * Kernel-related changes: - kernel: defaults for KBUILD_BUILD_USER and KBUILD_BUILD_HOST are now soft - kernel-fitimage: Introduce a
[yocto] [ANNOUNCEMENT] Yocto Project 2.7 (warrior 21.0.0) Released
Hello, We are pleased to announce the latest release of the Yocto Project 2.7 (warrior-21.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/RELEASENOTES Full test report is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/testreport.txt Thank you for everyone's contributions to this release. Sincerely, Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com --- yocto-2.7 Release Notes --- -- Downloads -- Release Name: poky-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 0e392026ffefee098a890c39bc3ca1f697bacb52 md5: 5b9ea9d4017f85148b1476e026ac8544 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/poky-warrior-21.0.0.tar.bz2 Release Name: oecore-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: f571b188177788d8ed0a7f3efe3569f153b1b0d3 md5: cb1eafef6c055838afddc505e6df7a74 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/oecore-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/oecore-warrior-21.0.0.tar.bz2 Release Name: meta-mingw-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 10695afe8cd406844e0d0dd868c11677e07557d4 md5: d69c92745ea9959f3bb7a5d35f4b9fbc Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-mingw-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-mingw-warrior-21.0.0.tar.bz2 Release Name: meta-intel-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: cd2c3bfca97655999cbde645b73be712675dba92 md5: 3c300918d246c9902150dc2e2b9dd756 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-intel-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-intel-warrior-21.0.0.tar.bz2 Release Name: meta-gplv2-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: 106ba6d2a4d08a276205c305f8485d701fe8a8f3 md5: 94bb8a8ed9b11d2693aaa373f93625dd Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/meta-gplv2-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/meta-gplv2-warrior-21.0.0.tar.bz2 Release Name: bitbake-warrior-21.0.0 Branch: warrior Tag: warrior-21.0.0 Hash: cb185efe9e88cfb12b7a3fd08f3086ca0b69c8e2 md5: 4c69bb5e8ffb29bb40bb105920838441 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/bitbake-warrior-21.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.7/bitbake-warrior-21.0.0.tar.bz2 --- New Features / Enhancements --- * Linux kernel 5.0/4.19, gcc 8.3, glibc 2.29 and ~230 other recipe upgrades * Added support for virgl GL acceleration within QEMU / runqemu * Added support SLiRP user-space networking in runqemu for easier networking within containers * New "packagegroup-core-base-utils" packagegroup to easily bring in full-featured versions of standard system utilities * New "ccmake" class to enable the CMake curses UI * New "mcextend" class to enable easily creating multiconfig recipe variants * New "xmlcatalog" class to update the XML catalogue * New recipes: eglinfo-wayland, inetutils, libdazzle, libjitterentropy, libmodulemd, libpsl, vim, virglrenderer * Architecture-specific changes: - linux-yocto: add baseline ARC support - qemuarm64: Add graphics support - qemuarm: Swap for an arm7ve (A15) configuration - qemumips64: change tune to mips64r2 - qemumips: Enable the poweroff driver - arch-armv7*.inc: Add Cortex vfpv4-d16 support - arch-armv8a.inc: add tune include for armv8 - arm-tunes: Remove -march option if mcpu is already added - ThunderX: update the armv8a rules - tune-cortexa32: add tunes for ARM Cortex-A32 - tune-cortexa35: add tunes for ARM Cortex-A35 - tune-cortexa53: add tunes for ARM Cortex-A53 - tune-cortexa5.inc: Add tune options for vfpv4 - tune-cortexa72: add tunes for ARM Cortex-A72 - linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions - gcc: Enable secureplt for powerpc64 target too - goarch: Add riscv64 - gstreamer: Add RISC-V support - kernel-fitimage: support RISC-V - lib/oe/elf.py: Add powerpc64 architecture definition for musl - webkitgtk: Enable building for ARC architecture - linux-yocto: pinctrl config change for cannonlake - mdadm: add mdmon service to support Intel VROC - mesa: Allow building the r600 driver - locale: Allow usage of cross-localedef for ARC - Added armeb support to meson class * Kernel-related changes: - kernel: defaults for KBUILD_BUILD_USER and KBUILD_BUILD_HOST are now soft - kernel-fitimage: Introduce a
Re: [yocto] Could not find glib.h
Hi Andreas,
It was my program, it has been compiled for weeks without any issues
until I added an #include , despite the glib-2.0 was defined
in the recipe, the do_compile() stopped at following errors, I can see
glib-2.0 was built in build and image directory, I can see glib.h was
in build and image directory, is it a basic principle if a package
library was defined in DEPENDS, the bitback should automatically find
the header files and library links? Why it still complained no such
file?
DEPENDS += "glib-2.0"
RDEPENDS += "glib-2.0"
do_compile() {
oe_runmake -e
}
fatal error: glib.h: No such file or directory #include
^~~~
compilation terminated.
Thank you.
Kind regards,
- jupiter
On 5/1/19, Andreas Müller wrote:
> On Wed, May 1, 2019 at 12:35 PM JH wrote:
>>
>> Thanks Richard, where to run pkg-config? If I run pkg-config in the
>> host, it pointed to host Ubuntu package which is different to the
>> cross compiler.
>>
>> On 5/1/19, Richard Purdie wrote:
>> > On Wed, 2019-05-01 at 10:43 +1000, JH wrote:
>> >> Hi,
>> >>
>> >> I added glib-2.0 to DEPENDS but it still could find the glib.h, what
>> >> I
>> >> could be missing here?
>> >>
>> >> fatal error: glib.h: No such file or directory
>> >> > #include
>> >> > ^~~~
>> >> > compilation terminated.
>> >
>> > You probably need to use pkg-config to find out which CFLAGS to use for
>> > glib-2.0...
>> >
> Maybe I missed something but there is not much information about what
> you are trying to build. Starts with build system: autotools / cmake /
> meson / qmake / waf?
>
> Is there a place to look into the recipe? That might make support easier.
>
> Andreas
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
On Wed, May 1, 2019 at 12:35 PM JH wrote: > > Thanks Richard, where to run pkg-config? If I run pkg-config in the > host, it pointed to host Ubuntu package which is different to the > cross compiler. > > On 5/1/19, Richard Purdie wrote: > > On Wed, 2019-05-01 at 10:43 +1000, JH wrote: > >> Hi, > >> > >> I added glib-2.0 to DEPENDS but it still could find the glib.h, what > >> I > >> could be missing here? > >> > >> fatal error: glib.h: No such file or directory > >> > #include > >> > ^~~~ > >> > compilation terminated. > > > > You probably need to use pkg-config to find out which CFLAGS to use for > > glib-2.0... > > Maybe I missed something but there is not much information about what you are trying to build. Starts with build system: autotools / cmake / meson / qmake / waf? Is there a place to look into the recipe? That might make support easier. Andreas -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Boost build failure for x32 target in thud
I'm trying to upgrade my project from sumo to thud. I'm targeting an x86_64 machine with the x32 ABI. Boost do_compile() fails with several instances like the following. | /home/mabnhdev/boost-issue-x32-repro/build/tmp/work/x86_64_x32-poky-linux-gnux32/boost/1.68.0-r0/recipe-sysroot/usr/include/bits/long-double.h:60:10: fatal error: bits/long-double-64.h: No such file or directory | #include | ^~~ | compilation terminated. | ...failed updating 6 targets... | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /home/mabnhdev/boost-issue-x32-repro/build/tmp/work/x86_64_x32-poky-linux-gnux32/boost/1.68.0-r0/temp/log.do_compile.15399) ERROR: Task (/home/mabnhdev/boost-issue-x32-repro/meta/recipes-support/boost/boost_1.68.0.bb:do_compile) failed with exit code '1' The failure can be reproduced by trying to build boost for an 'intel-corei7-64' machine with 'x86-64-x32' default tuning. The attached simple bash script will reproduce the problem. https://gist.github.com/mabnhdev/42d4775f51df4bbe675ce0a0c9c4c4b0 I'd appreciate some guidance towards fixing this issue. Regards, Mike -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
Thanks Richard, where to run pkg-config? If I run pkg-config in the host, it pointed to host Ubuntu package which is different to the cross compiler. On 5/1/19, Richard Purdie wrote: > On Wed, 2019-05-01 at 10:43 +1000, JH wrote: >> Hi, >> >> I added glib-2.0 to DEPENDS but it still could find the glib.h, what >> I >> could be missing here? >> >> fatal error: glib.h: No such file or directory >> > #include >> > ^~~~ >> > compilation terminated. > > You probably need to use pkg-config to find out which CFLAGS to use for > glib-2.0... > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Could not find glib.h
On Wed, 2019-05-01 at 10:43 +1000, JH wrote: > Hi, > > I added glib-2.0 to DEPENDS but it still could find the glib.h, what > I > could be missing here? > > fatal error: glib.h: No such file or directory > > #include > > ^~~~ > > compilation terminated. You probably need to use pkg-config to find out which CFLAGS to use for glib-2.0... Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
