Re: [yocto] do_configure for socketcand package failed
That configure script is looking for libconfig.
You need DEPENDS = "libconfig"
On Mon, Jul 30, 2018 at 4:20 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Seems, that this does work?!
> ___
>
> SUMMARY = "Socketcand ..."
> SECTION = "socketcan"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
> PR = "r0"
>
> RDEPENDS_${PN}-dev += "${PN}-staticdev"
>
> SRCREV = "df7fb4ff8a4439d7737fe2df3540e1ab7465721a"
> SRC_URI = "git://github.com/dschanoeh/socketcand.git;protocol=http"
>
> S = "${WORKDIR}/git"
>
> EXTRA_OECONF = "
> --without-config
> "
>
> inherit autotools update-alternatives
> inherit autotools-brokensep
> ___
>
> Any additional comments?
>
> Thank you,
> Zoran
>
> On Mon, Jul 30, 2018 at 8:40 AM, Zoran Stojsavljevic
> wrote:
> > Hello,
> >
> > I am writing the recipe for the socketcand package. It looks so far very
> simple:
> >
> > PR = "r0"
> >
> > RDEPENDS_${PN}-dev += "${PN}-staticdev"
> >
> > SRCREV = "df7fb4ff8a4439d7737fe2df3540e1ab7465721a"
> >
> > SRC_URI = "git://github.com/dschanoeh/socketcand.git;protocol=http"
> >
> > S = "${WORKDIR}/git"
> >
> > inherit autotools
> > ___
> >
> > I did install the following:
> > sudo apt-get install autoconf
> > sudo apt-get install libconfig-dev
> >
> > The error is in do_config():
> >
> > | checking for config_init in -lconfig... no
> > | configure: error: in
> >
> `/home/netmodule.intranet/stojsavljevic/projects/beaglebone-black/yocto-rocko/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/socketcand/1.0-r0/build':
> > | configure: error: config test failed (--without-config to disable)
> >
> > What should I include in the recipe to make it work (the both autoconf
> > and ./configure work normally for the normal installation)???
> >
> > Thank you,
> > Zoran
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-gplv2][PATCH] gnutls: update 3.3.29 -> 3.3.30
* Version 3.3.30 (released 2018-07-16) ** libgnutls: Corrected infinite loop when an incorrect PIN was provided via pin-value or pin-source. ** gnutls-cli: backported the --sni-hostname option. This allows overriding the hostname advertised to the peer. ** Improved counter-measures for TLS CBC record padding. Kenny Paterson, Eyal Ronen and Adi Shamir reported that the existing counter-measures had certain issues and were insufficient when the attacker has additional access to the CPU cache and performs a chosen-plaintext attack. This affected the legacy CBC ciphersuites. [CVSS: medium] ** The ciphers utilizing HMAC-SHA384 and SHA256 have been removed from the default priority strings. They are not necessary for compatibility or other purpose and provide no advantage over their SHA1 counter-parts, as they all depend on the legacy TLS CBC block mode. ** API and ABI modifications: No changes since last version. Signed-off-by: Andre McCurdy --- recipes-support/gnutls/gnutls_3.3.29.bb | 8 recipes-support/gnutls/gnutls_3.3.30.bb | 8 2 files changed, 8 insertions(+), 8 deletions(-) delete mode 100644 recipes-support/gnutls/gnutls_3.3.29.bb create mode 100644 recipes-support/gnutls/gnutls_3.3.30.bb diff --git a/recipes-support/gnutls/gnutls_3.3.29.bb b/recipes-support/gnutls/gnutls_3.3.29.bb deleted file mode 100644 index 21099eb..000 --- a/recipes-support/gnutls/gnutls_3.3.29.bb +++ /dev/null @@ -1,8 +0,0 @@ -require gnutls.inc - -SRC_URI += " \ -file://configure.ac-fix-sed-command.patch \ -file://use-pkg-config-to-locate-zlib.patch \ -" -SRC_URI[md5sum] = "de7a58232d42b1d71baf38a06dc34412" -SRC_URI[sha256sum] = "fa9d13f1bc35b81fac85152906b8d4950f4f5a90d76d5b406c1167728770c94a" diff --git a/recipes-support/gnutls/gnutls_3.3.30.bb b/recipes-support/gnutls/gnutls_3.3.30.bb new file mode 100644 index 000..6e9f026 --- /dev/null +++ b/recipes-support/gnutls/gnutls_3.3.30.bb @@ -0,0 +1,8 @@ +require gnutls.inc + +SRC_URI += " \ +file://configure.ac-fix-sed-command.patch \ +file://use-pkg-config-to-locate-zlib.patch \ +" +SRC_URI[md5sum] = "748f4c194a51ca9f2c02d9b7735262c2" +SRC_URI[sha256sum] = "41d70107ead3de2f12390909a05eefc9a88def6cd1f0d90ea82a7dac8b8effee" -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing syslogd form busybox
On Mon, Jul 30, 2018 at 10:53 AM, Simon Chamlian wrote: > So what you are saying is I need to update busybox to be able to remove > syslog from it? Depends on what you mean by "update". Backporting a patch is generally considered updating, but I guess you could argue either way. What I'm saying is that upstream oe-core contains a change to the busybox recipe which makes it easier to disable busybox syslog. It's up to you whether you try to backport that change or whether you come up with your own solution. Both ways can be made to work. > Also I noticed 2 syslogd: > /sbin/syslogd > /usr/lib/opkg/alternatives/syslogd > > /sbin/syslogd is a link to busybox. > > What is /usr/lib/opkg/alternatives/syslogd ? > > > > On Fri, Jul 27, 2018 at 4:47 PM, Andre McCurdy wrote: >> >> On Fri, Jul 27, 2018 at 1:07 PM, Simon Chamlian >> wrote: >> > Hi, >> > >> > When I removing syslogd from busybox, I can compile with no error >> > >> > $ bitbake -c compile busybox >> > Loading cache: 100% || Time: 0:00:01 >> > Loaded 3082 entries from dependency cache. >> > WARNING: No bb files matched BBFILE_PATTERN_phytec >> > '^/opt/PHYTEC_BSPs/yocto_imx7/sources/meta-phytec/common/' >> > NOTE: Resolving any missing task queue dependencies >> > >> > Build Configuration: >> > BB_VERSION= "1.32.0" >> > BUILD_SYS = "x86_64-linux" >> > NATIVELSBSTRING = "Ubuntu-16.04" >> > TARGET_SYS= "arm-poky-linux-gnueabi" >> > MACHINE = "imx7d-phyboard-zeta-001" >> > DISTRO= "fsl-imx-x11" >> > DISTRO_VERSION= "4.9.11-1.0.0" >> > TUNE_FEATURES = "arm armv7ve vfp neoncallconvention-hard >> > cortexa7" >> > TARGET_FPU= "hard" >> > meta >> > meta-poky = "HEAD:78890ea22750804e3e9113e76f7ca3d7234c8342" >> > meta-oe >> > meta-multimedia >> > meta-webserver= "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e" >> > meta-freescale= "HEAD:a398b50b7fc084a9e68cc3000c218d5028522a25" >> > meta-freescale-3rdparty = >> > "HEAD:68314612e236cab1da82d72a0da62635a3523f84" >> > meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390" >> > meta-bsp >> > meta-sdk = "HEAD:daba3340ecd8b358e0c6c415baeee0fcae95c525" >> > meta-browser = "HEAD:10f6e3778d823ee1be106c126216c6f941088fbf" >> > meta-gnome >> > meta-networking >> > meta-python >> > meta-filesystems = "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e" >> > meta-qt5 = "HEAD:ff073f04109900fc07bf81e2f1df63c626caf342" >> > meta-phytec >> > meta-phytec-fsl = "HEAD:f9897a4e06f43184a71d315cec4a412a28baa59b" >> > >> > WARNING: >> > >> > /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/busybox/busybox_1.24.1.bb.do_compile >> > is tainted from a forced run >> > | ETA: 0:00:01 >> > Initialising tasks: 100% >> > >> > |###| >> > Time: 0:00:01 >> > NOTE: Executing SetScene Tasks >> > NOTE: Executing RunQueue Tasks >> > NOTE: Tasks Summary: Attempted 234 tasks of which 232 didn't need to be >> > rerun and all succeeded. >> > >> > Summary: There were 2 WARNING messages shown. >> > >> > >> > When I build my image for my machine, I am getting the following error: >> > >> > >> > WARNING: busybox-1.24.1-r0 do_package: busybox: alternative target >> > (/etc/syslog.conf or /etc/syslog.conf.busybox) does not exist, >> > skipping... >> > WARNING: busybox-1.24.1-r0 do_package: busybox: NOT adding alternative >> > provide /etc/syslog.conf: /etc/syslog.conf.busybox does not exist >> > ERROR: busybox-1.24.1-r0 do_package: SYSTEMD_SERVICE_busybox-syslog >> > value >> > busybox-syslog.service does not exist >> > ERROR: busybox-1.24.1-r0 do_package: Function failed: >> > systemd_populate_packages >> > ERROR: Logfile of failure stored in: >> > >> > /opt/PHYTEC_BSPs/yocto_imx7/build/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/busybox/1.24.1-r0/temp/log.do_package.30442 >> > ERROR: Task >> > >> > (/opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/busybox/busybox_1.24.1.bb:do_package) >> > failed with exit code '1' >> > >> > Any hints? >> >> It looks like you're using morty, which pre-dates busybox syslog >> "officially" being made optional: >> >> >> http://git.openembedded.org/openembedded-core/commit/?id=9732a2ba2edf2607e61ae4fe0d65a02b7918cfe7 >> >> If you can't update to a newer release you could try backporting the >> above commit. > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing syslogd form busybox
So what you are saying is I need to update busybox to be able to remove syslog from it? Also I noticed 2 syslogd: /sbin/syslogd /usr/lib/opkg/alternatives/syslogd /sbin/syslogd is a link to busybox. What is /usr/lib/opkg/alternatives/syslogd ? On Fri, Jul 27, 2018 at 4:47 PM, Andre McCurdy wrote: > On Fri, Jul 27, 2018 at 1:07 PM, Simon Chamlian > wrote: > > Hi, > > > > When I removing syslogd from busybox, I can compile with no error > > > > $ bitbake -c compile busybox > > Loading cache: 100% || Time: 0:00:01 > > Loaded 3082 entries from dependency cache. > > WARNING: No bb files matched BBFILE_PATTERN_phytec > > '^/opt/PHYTEC_BSPs/yocto_imx7/sources/meta-phytec/common/' > > NOTE: Resolving any missing task queue dependencies > > > > Build Configuration: > > BB_VERSION= "1.32.0" > > BUILD_SYS = "x86_64-linux" > > NATIVELSBSTRING = "Ubuntu-16.04" > > TARGET_SYS= "arm-poky-linux-gnueabi" > > MACHINE = "imx7d-phyboard-zeta-001" > > DISTRO= "fsl-imx-x11" > > DISTRO_VERSION= "4.9.11-1.0.0" > > TUNE_FEATURES = "arm armv7ve vfp neoncallconvention-hard > > cortexa7" > > TARGET_FPU= "hard" > > meta > > meta-poky = "HEAD:78890ea22750804e3e9113e76f7ca3d7234c8342" > > meta-oe > > meta-multimedia > > meta-webserver= "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e" > > meta-freescale= "HEAD:a398b50b7fc084a9e68cc3000c218d5028522a25" > > meta-freescale-3rdparty = "HEAD:68314612e236cab1da82d72a0da626 > 35a3523f84" > > meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390" > > meta-bsp > > meta-sdk = "HEAD:daba3340ecd8b358e0c6c415baeee0fcae95c525" > > meta-browser = "HEAD:10f6e3778d823ee1be106c126216c6f941088fbf" > > meta-gnome > > meta-networking > > meta-python > > meta-filesystems = "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e" > > meta-qt5 = "HEAD:ff073f04109900fc07bf81e2f1df63c626caf342" > > meta-phytec > > meta-phytec-fsl = "HEAD:f9897a4e06f43184a71d315cec4a412a28baa59b" > > > > WARNING: > > /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes- > core/busybox/busybox_1.24.1.bb.do_compile > > is tainted from a forced run > > | ETA: 0:00:01 > > Initialising tasks: 100% > > |### > > | > > Time: 0:00:01 > > NOTE: Executing SetScene Tasks > > NOTE: Executing RunQueue Tasks > > NOTE: Tasks Summary: Attempted 234 tasks of which 232 didn't need to be > > rerun and all succeeded. > > > > Summary: There were 2 WARNING messages shown. > > > > > > When I build my image for my machine, I am getting the following error: > > > > > > WARNING: busybox-1.24.1-r0 do_package: busybox: alternative target > > (/etc/syslog.conf or /etc/syslog.conf.busybox) does not exist, > skipping... > > WARNING: busybox-1.24.1-r0 do_package: busybox: NOT adding alternative > > provide /etc/syslog.conf: /etc/syslog.conf.busybox does not exist > > ERROR: busybox-1.24.1-r0 do_package: SYSTEMD_SERVICE_busybox-syslog value > > busybox-syslog.service does not exist > > ERROR: busybox-1.24.1-r0 do_package: Function failed: > > systemd_populate_packages > > ERROR: Logfile of failure stored in: > > /opt/PHYTEC_BSPs/yocto_imx7/build/tmp/work/cortexa7hf- > neon-poky-linux-gnueabi/busybox/1.24.1-r0/temp/log.do_package.30442 > > ERROR: Task > > (/opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes- > core/busybox/busybox_1.24.1.bb:do_package) > > failed with exit code '1' > > > > Any hints? > > It looks like you're using morty, which pre-dates busybox syslog > "officially" being made optional: > > http://git.openembedded.org/openembedded-core/commit/?id= > 9732a2ba2edf2607e61ae4fe0d65a02b7918cfe7 > > If you can't update to a newer release you could try backporting the > above commit. > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] devtool add recipe with no srctree / fetchuri?
Got it. Thank you for the prompt response. On Mon, Jul 30, 2018 at 10:18 AM Burton, Ross wrote: > devtool add's primary convenience is how it can examine the source and > write the LICENSE correctly, the correct inherits, etc. If you're > just going to install a few files then just write a recipe from > scratch. > > Ross > > On 30 July 2018 at 15:10, Adam Lee wrote: > > Is it possible to run 'devtool add [recipe-name]' without 'srctree' or > > 'fetchuri'? > > I just want to add a simple recipe with a few files to be installed on > the > > target file system. > > I can directly add a file in my meta-layer, but devtool is probably the > more > > correct approach. > > > > Adam > > > > -- > > ___ > > Openembedded-core mailing list > > openembedded-c...@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] devtool add recipe with no srctree / fetchuri?
devtool add's primary convenience is how it can examine the source and write the LICENSE correctly, the correct inherits, etc. If you're just going to install a few files then just write a recipe from scratch. Ross On 30 July 2018 at 15:10, Adam Lee wrote: > Is it possible to run 'devtool add [recipe-name]' without 'srctree' or > 'fetchuri'? > I just want to add a simple recipe with a few files to be installed on the > target file system. > I can directly add a file in my meta-layer, but devtool is probably the more > correct approach. > > Adam > > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] devtool add recipe with no srctree / fetchuri?
Is it possible to run 'devtool add [recipe-name]' without 'srctree' or 'fetchuri'? I just want to add a simple recipe with a few files to be installed on the target file system. I can directly add a file in my meta-layer, but devtool is probably the more correct approach. Adam -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What are the differences among libconfig8-dev, libconfig-dev and libconfig???
On 30 July 2018 at 14:28, Zoran Stojsavljevic wrote: > Anybody knows? > > Do all three exist in YOCTO as different libraries, or these are > variations/the same as libconfig? Context is useful but they all sound like various distribution names for libconfig. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Intel machine with 64 Bit kernel and 32 Bit user space
I just realized that SDK generation does not include the lib32 libraries !
I run for that :
$ MACHINE=my-machine bitbake -c pouplate_sdk my-image
On Mon, Jul 30, 2018 at 2:51 PM, Ayoub Zaki
wrote:
> Hi all,
>
> I added to my image: IMAGE_INSTALL_append = " lib32-glibc" and it solved
> the build problem !
>
> now I can build a mixed image (64 Bit kernel, 32 Bit) user space using
> multilib :
>
> $ MACHINE =mymachine bitbake lib32-my-image
>
> Thank you all for your inputs.
>
> best regards
>
> On Fri, Jul 27, 2018 at 1:19 PM, Martin Jansa
> wrote:
>
>> Check with bitbake -g what's pulling gcc-runtime into the image, if your
>> whole userspace should be 32bit, then lib32-gcc-runtime will be enough.
>>
>> My multilib builds contain only following 64bit builds:
>> defaultpkgname depmodwrapper-cross linux-yocto lttng-modules
>> make-mod-scripts qemuwrapper-cross vboxguestdrivers
>> the rest is 32bit
>>
>> On Fri, Jul 27, 2018 at 12:23 PM Ayoub Zaki
>> wrote:
>>
>>> Hello all,
>>>
>>> thanks for the suggestions: I tried the multilib concept of yocto but as
>>> Martin already wrote is not that simple, my build is breaking during wic
>>> image generation as follow:
>>>
>>> zaki@xps:/opt/build/poky/build$ MACHINE=nx bitbake lib32-my-image
>>> Loading cache: 100% |#
>>>
>>> ###|
>>> Time: 0:00:00
>>> Loaded 4968 entries from dependency cache.
>>> NOTE: Resolving any missing task queue dependencies
>>>
>>> Build Configuration:
>>> BB_VERSION = "1.38.0"
>>> BUILD_SYS= "x86_64-linux"
>>> NATIVELSBSTRING = "universal"
>>> TARGET_SYS = "x86_64-poky-linux"
>>> MACHINE = "nx"
>>> DISTRO = "poky"
>>> DISTRO_VERSION = "V00.00.00.00+20180727100935"
>>> TUNE_FEATURES= "m64 core2"
>>> TARGET_FPU = ""
>>> meta
>>> meta-poky
>>> meta-yocto-bsp = "sumo:90f7edb32ac2500d93bb7ca5045a9d048f551223"
>>> meta-intel = "sumo:2430f73ee06f3315ebebe69899f1977f9a09e29f"
>>> meta-oe
>>> meta-networking
>>> meta-webserver
>>> meta-python = "sumo:b0950aeff5b630256bb5e25ca15f4d59c115e7c1"
>>>
>>> Initialising tasks: 100% |#
>>>
>>> ##|
>>> Time: 0:00:02
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> WARNING: lib32-my-image-1.0-r0 do_rootfs: lib32-systemd.postinst
>>> returned 1, marking as unpacked only, configuration required on target.
>>> WARNING: lib32-my-image-1.0-r0 do_rootfs: Intentionally failing
>>> postinstall scriptlets of ['lib32-systemd'] to defer them to first boot is
>>> deprecated. Please place them into pkg_postinst_ontarget_${PN} ().
>>> If deferring to first boot wasn't the intent, then scriptlet failure may
>>> mean an issue in the recipe, or a regression elsewhere.
>>> Details of the failure are in /opt/build/poky/build/tmp/work
>>> /nx-pokymllib32-linux/lib32-my-image/1.0-r0/temp/log.do_rootfs.
>>> WARNING: lib32-my-image-1.0-r0 do_rootfs: [log_check] lib32-my-image:
>>> found 1 warning message in the logfile:
>>> [log_check] WARNING: Intentionally failing postinstall scriptlets of
>>> ['lib32-systemd'] to defer them to first boot is deprecated. Please place
>>> them into pkg_postinst_ontarget_${PN} ().
>>> ERROR: lib32-my-image-1.0-r0 do_image_wic: The file
>>> /usr/share/gcc-7.3.0/python/libstdcxx/__init__.py is installed by both
>>> lib32-gcc-runtime and gcc-runtime, aborting
>>> ERROR: lib32-my-image-1.0-r0 do_image_wic: Function failed:
>>> extend_recipe_sysroot
>>> ERROR: Logfile of failure stored in: /opt/build/poky/build/tmp/work
>>> /nx-pokymllib32-linux/lib32-my-image/1.0-r0/temp/log.do_image_wic.16922
>>> ERROR: Task (virtual:multilib:lib32:/opt/build/poky/meta-poky/recipes-co
>>> re/images/my-image.bb:do_image_wic) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 3460 tasks of which 3445 didn't need to
>>> be rerun and 1 failed.
>>>
>>> Summary: 1 task failed:
>>> virtual:multilib:lib32:/opt/build/poky/meta-poky/recipes-cor
>>> e/images/my-image.bb:do_image_wic
>>> Summary: There were 3 WARNING messages shown.
>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>>> code.
>>>
>>>
>>> The ERROR: lib32-my-image-1.0-r0 do_image_wic: The file
>>> /usr/share/gcc-7.3.0/python/libstdcxx/__init__.py is installed by both
>>> lib32-gcc-runtime and gcc-runtime, aborting is not self-explanatory!
>>>
>>> gcc-runtime is anyway not part of the image ?!
>>>
>>> any suggestions ?
>>>
>>>
>>> thank you
>>>
>>>
>>> Best regards
>>>
>>> On Thu, Jul 26, 2018 at 8:12 PM, Martin Jansa
>>> wrote:
>>>
It's not as simple as that in some cases, there are some components
which are pulled in 64bit version
[yocto] What are the differences among libconfig8-dev, libconfig-dev and libconfig???
Anybody knows? Do all three exist in YOCTO as different libraries, or these are variations/the same as libconfig? Thank you, Zoran -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Intel machine with 64 Bit kernel and 32 Bit user space
Hi all,
I added to my image: IMAGE_INSTALL_append = " lib32-glibc" and it solved
the build problem !
now I can build a mixed image (64 Bit kernel, 32 Bit) user space using
multilib :
$ MACHINE =mymachine bitbake lib32-my-image
Thank you all for your inputs.
best regards
On Fri, Jul 27, 2018 at 1:19 PM, Martin Jansa
wrote:
> Check with bitbake -g what's pulling gcc-runtime into the image, if your
> whole userspace should be 32bit, then lib32-gcc-runtime will be enough.
>
> My multilib builds contain only following 64bit builds:
> defaultpkgname depmodwrapper-cross linux-yocto lttng-modules
> make-mod-scripts qemuwrapper-cross vboxguestdrivers
> the rest is 32bit
>
> On Fri, Jul 27, 2018 at 12:23 PM Ayoub Zaki
> wrote:
>
>> Hello all,
>>
>> thanks for the suggestions: I tried the multilib concept of yocto but as
>> Martin already wrote is not that simple, my build is breaking during wic
>> image generation as follow:
>>
>> zaki@xps:/opt/build/poky/build$ MACHINE=nx bitbake lib32-my-image
>> Loading cache: 100% |#
>>
>> ###|
>> Time: 0:00:00
>> Loaded 4968 entries from dependency cache.
>> NOTE: Resolving any missing task queue dependencies
>>
>> Build Configuration:
>> BB_VERSION = "1.38.0"
>> BUILD_SYS= "x86_64-linux"
>> NATIVELSBSTRING = "universal"
>> TARGET_SYS = "x86_64-poky-linux"
>> MACHINE = "nx"
>> DISTRO = "poky"
>> DISTRO_VERSION = "V00.00.00.00+20180727100935"
>> TUNE_FEATURES= "m64 core2"
>> TARGET_FPU = ""
>> meta
>> meta-poky
>> meta-yocto-bsp = "sumo:90f7edb32ac2500d93bb7ca5045a9d048f551223"
>> meta-intel = "sumo:2430f73ee06f3315ebebe69899f1977f9a09e29f"
>> meta-oe
>> meta-networking
>> meta-webserver
>> meta-python = "sumo:b0950aeff5b630256bb5e25ca15f4d59c115e7c1"
>>
>> Initialising tasks: 100% |#
>>
>> ##|
>> Time: 0:00:02
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> WARNING: lib32-my-image-1.0-r0 do_rootfs: lib32-systemd.postinst returned
>> 1, marking as unpacked only, configuration required on target.
>> WARNING: lib32-my-image-1.0-r0 do_rootfs: Intentionally failing
>> postinstall scriptlets of ['lib32-systemd'] to defer them to first boot is
>> deprecated. Please place them into pkg_postinst_ontarget_${PN} ().
>> If deferring to first boot wasn't the intent, then scriptlet failure may
>> mean an issue in the recipe, or a regression elsewhere.
>> Details of the failure are in /opt/build/poky/build/tmp/
>> work/nx-pokymllib32-linux/lib32-my-image/1.0-r0/temp/log.do_rootfs.
>> WARNING: lib32-my-image-1.0-r0 do_rootfs: [log_check] lib32-my-image:
>> found 1 warning message in the logfile:
>> [log_check] WARNING: Intentionally failing postinstall scriptlets of
>> ['lib32-systemd'] to defer them to first boot is deprecated. Please place
>> them into pkg_postinst_ontarget_${PN} ().
>> ERROR: lib32-my-image-1.0-r0 do_image_wic: The file
>> /usr/share/gcc-7.3.0/python/libstdcxx/__init__.py is installed by both
>> lib32-gcc-runtime and gcc-runtime, aborting
>> ERROR: lib32-my-image-1.0-r0 do_image_wic: Function failed:
>> extend_recipe_sysroot
>> ERROR: Logfile of failure stored in: /opt/build/poky/build/tmp/
>> work/nx-pokymllib32-linux/lib32-my-image/1.0-r0/temp/
>> log.do_image_wic.16922
>> ERROR: Task (virtual:multilib:lib32:/opt/build/poky/meta-poky/recipes-
>> core/images/my-image.bb:do_image_wic) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 3460 tasks of which 3445 didn't need to be
>> rerun and 1 failed.
>>
>> Summary: 1 task failed:
>> virtual:multilib:lib32:/opt/build/poky/meta-poky/recipes-
>> core/images/my-image.bb:do_image_wic
>> Summary: There were 3 WARNING messages shown.
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>> code.
>>
>>
>> The ERROR: lib32-my-image-1.0-r0 do_image_wic: The file
>> /usr/share/gcc-7.3.0/python/libstdcxx/__init__.py is installed by both
>> lib32-gcc-runtime and gcc-runtime, aborting is not self-explanatory!
>>
>> gcc-runtime is anyway not part of the image ?!
>>
>> any suggestions ?
>>
>>
>> thank you
>>
>>
>> Best regards
>>
>> On Thu, Jul 26, 2018 at 8:12 PM, Martin Jansa
>> wrote:
>>
>>> It's not as simple as that in some cases, there are some components
>>> which are pulled in 64bit version even when building lib32-foo-image.
>>>
>>> Some are easy to override from the config e.g.:
>>> ROOTFS_PKGMANAGE = "${LIB32_PREFIX}opkg"
>>> SPLASH = "${LIB32_PREFIX}psplash"
>>>
>>> but to prevent building e.g. syslinux in 64bit version is a bit more
>>> tricky.
>>>
>>> syslinux.bbclass was fixed long time ago:
>>> commit
Re: [yocto] do_configure for socketcand package failed
Seems, that this does work?!
___
SUMMARY = "Socketcand ..."
SECTION = "socketcan"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
PR = "r0"
RDEPENDS_${PN}-dev += "${PN}-staticdev"
SRCREV = "df7fb4ff8a4439d7737fe2df3540e1ab7465721a"
SRC_URI = "git://github.com/dschanoeh/socketcand.git;protocol=http"
S = "${WORKDIR}/git"
EXTRA_OECONF = "
--without-config
"
inherit autotools update-alternatives
inherit autotools-brokensep
___
Any additional comments?
Thank you,
Zoran
On Mon, Jul 30, 2018 at 8:40 AM, Zoran Stojsavljevic
wrote:
> Hello,
>
> I am writing the recipe for the socketcand package. It looks so far very
> simple:
>
> PR = "r0"
>
> RDEPENDS_${PN}-dev += "${PN}-staticdev"
>
> SRCREV = "df7fb4ff8a4439d7737fe2df3540e1ab7465721a"
>
> SRC_URI = "git://github.com/dschanoeh/socketcand.git;protocol=http"
>
> S = "${WORKDIR}/git"
>
> inherit autotools
> ___
>
> I did install the following:
> sudo apt-get install autoconf
> sudo apt-get install libconfig-dev
>
> The error is in do_config():
>
> | checking for config_init in -lconfig... no
> | configure: error: in
> `/home/netmodule.intranet/stojsavljevic/projects/beaglebone-black/yocto-rocko/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/socketcand/1.0-r0/build':
> | configure: error: config test failed (--without-config to disable)
>
> What should I include in the recipe to make it work (the both autoconf
> and ./configure work normally for the normal installation)???
>
> Thank you,
> Zoran
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] do_configure for socketcand package failed
Hello,
I am writing the recipe for the socketcand package. It looks so far very simple:
PR = "r0"
RDEPENDS_${PN}-dev += "${PN}-staticdev"
SRCREV = "df7fb4ff8a4439d7737fe2df3540e1ab7465721a"
SRC_URI = "git://github.com/dschanoeh/socketcand.git;protocol=http"
S = "${WORKDIR}/git"
inherit autotools
___
I did install the following:
sudo apt-get install autoconf
sudo apt-get install libconfig-dev
The error is in do_config():
| checking for config_init in -lconfig... no
| configure: error: in
`/home/netmodule.intranet/stojsavljevic/projects/beaglebone-black/yocto-rocko/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/socketcand/1.0-r0/build':
| configure: error: config test failed (--without-config to disable)
What should I include in the recipe to make it work (the both autoconf
and ./configure work normally for the normal installation)???
Thank you,
Zoran
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
