Re: [OE-core] [oe-core][PATCH 1/1] libtool: allow for use of reproducible_build bbclass
That's a question I have about things like this, where some information seems of minimal use, but is there and is now malignant. Chuck it or modify it to be benign. Joe -Original Message- From: Burton, Ross Sent: Thursday, July 11, 2019 2:56 PM To: Adrian Bunk Cc: Slater, Joseph ; OE-core Subject: Re: [OE-core] [oe-core][PATCH 1/1] libtool: allow for use of reproducible_build bbclass On Thu, 11 Jul 2019 at 21:45, Adrian Bunk wrote: > The Debian patch for the same purpose simply removes the problematic > line - a comment with the build host was anyways not important information. Agreed, it's just a comment, and replacing it with logic just means more effort when we need to rebase. Ideally, upstream remove that comment too, as it doesn't have much value at all. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] ninja: use Python 3
On Thu, Jul 11, 2019 at 4:55 PM Ross Burton wrote:
>
> As part of the mission to remove the use of Python 2, explicitly bootstrap
> Ninja
> with Python 3.
>
> Signed-off-by: Ross Burton
> ---
> meta/recipes-devtools/ninja/ninja_1.9.0.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/ninja/ninja_1.9.0.bb
> b/meta/recipes-devtools/ninja/ninja_1.9.0.bb
> index 1b063289614..f1236e8ac82 100644
> --- a/meta/recipes-devtools/ninja/ninja_1.9.0.bb
> +++ b/meta/recipes-devtools/ninja/ninja_1.9.0.bb
> @@ -17,11 +17,11 @@ S = "${WORKDIR}/git"
> do_configure[noexec] = "1"
>
> do_compile_class-native() {
> - ./configure.py --bootstrap
> + python3 ./configure.py --bootstrap
> }
>
> do_compile() {
> - ./configure.py
> + python3 ./configure.py
Maybe we should encode it in interpreter section inside configure.py
itself and upstream it.
> ninja
> }
>
> --
> 2.20.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] qemu: use Python 3 to build
As part of the mission to remove the use of Python 2, explicitly use Python 3
when building qemu.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/qemu/qemu-native.inc | 1 -
meta/recipes-devtools/qemu/qemu.inc| 2 ++
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/qemu/qemu-native.inc
b/meta/recipes-devtools/qemu/qemu-native.inc
index 34ab8e64011..c04297cad04 100644
--- a/meta/recipes-devtools/qemu/qemu-native.inc
+++ b/meta/recipes-devtools/qemu/qemu-native.inc
@@ -6,7 +6,6 @@ SRC_URI_append = " \
file://0011-fix-libcap-header-issue-on-some-distro.patch \
file://0012-cpus.c-Add-error-messages-when-qemi_cpu_kick_thread-.patch \
"
-EXTRA_OECONF_append = " --python=python2.7"
EXTRA_OEMAKE_append = " LD='${LD}' AR='${AR}' OBJCOPY='${OBJCOPY}'
LDFLAGS='${LDFLAGS}'"
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index ac475a8e2ae..c1c99cd8683 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -77,6 +77,8 @@ export LIBTOOL="${HOST_SYS}-libtool"
B = "${WORKDIR}/build"
+EXTRA_OECONF_append = " --python=${HOSTTOOLS_DIR}/python3"
+
do_configure_prepend_class-native() {
# Append build host pkg-config paths for native target since the host
may provide sdl
BHOST_PKGCONFIG_PATH=$(PATH=/usr/bin:/bin pkg-config --variable pc_path
pkg-config || echo "")
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] ninja: use Python 3
As part of the mission to remove the use of Python 2, explicitly bootstrap Ninja
with Python 3.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/ninja/ninja_1.9.0.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/ninja/ninja_1.9.0.bb
b/meta/recipes-devtools/ninja/ninja_1.9.0.bb
index 1b063289614..f1236e8ac82 100644
--- a/meta/recipes-devtools/ninja/ninja_1.9.0.bb
+++ b/meta/recipes-devtools/ninja/ninja_1.9.0.bb
@@ -17,11 +17,11 @@ S = "${WORKDIR}/git"
do_configure[noexec] = "1"
do_compile_class-native() {
- ./configure.py --bootstrap
+ python3 ./configure.py --bootstrap
}
do_compile() {
- ./configure.py
+ python3 ./configure.py
ninja
}
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] grub: build with python 3
As part of the mission to remove the use of Python 2, explicitly use Python 3
when building grub.
Signed-off-by: Ross Burton
---
meta/recipes-bsp/grub/grub2.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-bsp/grub/grub2.inc b/meta/recipes-bsp/grub/grub2.inc
index 20877e77355..c5ff10e5986 100644
--- a/meta/recipes-bsp/grub/grub2.inc
+++ b/meta/recipes-bsp/grub/grub2.inc
@@ -60,6 +60,8 @@ BUILD_CFLAGS = ""
BUILD_CXXFLAGS = ""
BUILD_LDFLAGS = ""
+export PYTHON = "python3"
+
CFLAGS_append = " -Wno-error"
do_configure_prepend() {
--
2.20.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] libpsl: update Upstream-Status
Signed-off-by: Ross Burton --- .../libpsl/0001-gtk-doc-do-not-include-tree_index.sgml.patch| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-support/libpsl/libpsl/0001-gtk-doc-do-not-include-tree_index.sgml.patch b/meta/recipes-support/libpsl/libpsl/0001-gtk-doc-do-not-include-tree_index.sgml.patch index 2331a766a16..c78d6fd981e 100644 --- a/meta/recipes-support/libpsl/libpsl/0001-gtk-doc-do-not-include-tree_index.sgml.patch +++ b/meta/recipes-support/libpsl/libpsl/0001-gtk-doc-do-not-include-tree_index.sgml.patch @@ -5,7 +5,7 @@ Subject: [PATCH] gtk-doc: do not include tree_index.sgml gtk-doc 1.30 no longer generates the file if the object tree is empty -Upstream-Status: Submitted [https://github.com/rockdaboot/libpsl/pull/137] +Upstream-Status: Backport [87d1add318b5e5d09977f7f374e923577b6ff3be] Signed-off-by: Alexander Kanavin --- docs/libpsl/libpsl-docs.sgml | 4 -- 2.20.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][PATCH 1/1] libtool: allow for use of reproducible_build bbclass
On Thu, 11 Jul 2019 at 21:45, Adrian Bunk wrote: > The Debian patch for the same purpose simply removes the problematic > line - a comment with the build host was anyways not important information. Agreed, it's just a comment, and replacing it with logic just means more effort when we need to rebase. Ideally, upstream remove that comment too, as it doesn't have much value at all. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][PATCH 1/1] libtool: allow for use of reproducible_build bbclass
On Thu, Jul 11, 2019 at 01:27:39PM -0700, Joe Slater wrote:
> In a reproducible build environment, do not put the build host
> name into libtool.
>...
> +Upstream-Status: Inappropriate [embedded specific]
>...
This is not specific to embedded.
> +--- a/m4/libtool.m4
> b/m4/libtool.m4
> +@@ -728,7 +728,17 @@ _LT_CONFIG_SAVE_COMMANDS([
> + cat <<_LT_EOF >> "$cfgfile"
> + #! $SHELL
> + # Generated automatically by $as_me ($PACKAGE) $VERSION
> ++_LT_EOF
> ++if test -n "${SOURCE_DATE_EPOCH}"; then
> ++cat <<_LT_EOF >> "$cfgfile"
> ++# Libtool was configured for a reproducible build: ${SOURCE_DATE_EPOCH}
> ++_LT_EOF
> ++else
> ++cat <<_LT_EOF >> "$cfgfile"
> + # Libtool was configured on host `(hostname || uname -n) 2>/dev/null | sed
> 1q`:
> ++_LT_EOF
> ++fi
> ++cat <<_LT_EOF >> "$cfgfile"
> + # NOTE: Changes made to this file will be lost: look at ltmain.sh.
> +
>...
The Debian patch for the same purpose simply removes the problematic
line - a comment with the build host was anyways not important information.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] RDEPENDS libstdc++ error
And this tool is provided to us as a pre-compiled binary. On Thu, 11 Jul 2019, 7:54 p.m. Ankur Tyagi, wrote: > Hi, > > I have a third party tool which I was packaging in my image based upon > Yocto 1.6 > > Now I am upgrading to Yocto 2.7 and the recipe which packages third > party tool is generating following error: > > requires libstdc++.so.6(CXXABI_1.3), but no providers found in > RDEPENDS_test-util? [file-rdeps] > requires libstdc++.so.6(GLIBCXX_3.4), but no providers found in > RDEPENDS_test-util? [file-rdeps] > > Is there a way to fix this without asking vendor to provide a new > version of tool? > > Thanks > Ankur > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [oe-core][PATCH 1/1] libtool: allow for use of reproducible_build bbclass
In a reproducible build environment, do not put the build host
name into libtool.
Signed-off-by: Joe Slater
---
.../libtool/libtool/reproducible_build.patch | 29 ++
meta/recipes-devtools/libtool/libtool_2.4.6.bb | 2 +-
2 files changed, 30 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-devtools/libtool/libtool/reproducible_build.patch
diff --git a/meta/recipes-devtools/libtool/libtool/reproducible_build.patch
b/meta/recipes-devtools/libtool/libtool/reproducible_build.patch
new file mode 100644
index 000..c770c24
--- /dev/null
+++ b/meta/recipes-devtools/libtool/libtool/reproducible_build.patch
@@ -0,0 +1,29 @@
+libtool: allow for reproducible build
+
+If we are in a reproducible build environment, do not put the build host
+name into libtool.
+
+Upstream-Status: Inappropriate [embedded specific]
+
+Signed-off-by: Joe Slater
+
+--- a/m4/libtool.m4
b/m4/libtool.m4
+@@ -728,7 +728,17 @@ _LT_CONFIG_SAVE_COMMANDS([
+ cat <<_LT_EOF >> "$cfgfile"
+ #! $SHELL
+ # Generated automatically by $as_me ($PACKAGE) $VERSION
++_LT_EOF
++if test -n "${SOURCE_DATE_EPOCH}"; then
++cat <<_LT_EOF >> "$cfgfile"
++# Libtool was configured for a reproducible build: ${SOURCE_DATE_EPOCH}
++_LT_EOF
++else
++cat <<_LT_EOF >> "$cfgfile"
+ # Libtool was configured on host `(hostname || uname -n) 2>/dev/null | sed
1q`:
++_LT_EOF
++fi
++cat <<_LT_EOF >> "$cfgfile"
+ # NOTE: Changes made to this file will be lost: look at ltmain.sh.
+
+ # Provide generalized library-building support services.
diff --git a/meta/recipes-devtools/libtool/libtool_2.4.6.bb
b/meta/recipes-devtools/libtool/libtool_2.4.6.bb
index f5fdd00..a67d6dd 100644
--- a/meta/recipes-devtools/libtool/libtool_2.4.6.bb
+++ b/meta/recipes-devtools/libtool/libtool_2.4.6.bb
@@ -1,6 +1,6 @@
require libtool-${PV}.inc
-SRC_URI += "file://multilib.patch"
+SRC_URI += "file://multilib.patch file://reproducible_build.patch"
RDEPENDS_${PN} += "bash"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [master][PATCH v5 0/3] Devtool: provide easy means of reconfiguring
This patch series provides support for the user to run menuconfig command in the devtool flow. This would allow the user to modify the current configurations and generate a config fragment to update the recipe using devtool finish. Devtool menuconfig command will work on all packages that contain menuconfig as a task. 1. The implementation checks if devtool menuconfig command is called for a valid package. 2. It checks for oe-local-files dir within source and creates one if needed, this directory is needed to store the final generated config fragment so that devtool finish can update the recipe. 3. Menuconfig command is called for users to make necessary changes. After saving the changes, diffconfig command is run to generate the fragment. Currently, when the user runs devtool modify command, it checks out the entire source tree which is a bit of an over head in time and space. This patch series also provides a way to create a copy(hard links) of the kernel source, if present, from work-shared to workspace to be more efficient . Also, if the kernel source is not present in the staging kernel dir and the user fetches the source tree in workspace using devtool modify, then this patch series creates a copy of source from workspace to work-shared. This is necessary for packages that may use the kernel source. [YOCTO #10416] --- changelog v2 1. Add a check to verify the set kernel version by user and kernel version present in work-shared before creating hard links to workspace. 2. Add a check to verify the set kernel version by user and kernel version present in workspace do not match, when placing a copy of kernel-source from workspace to work-shared. changelog v3 1. Use oe.path.copyhardlinktree() to create copy of source from work-shared to devtool workspace. 2. Split all the changes into appropriate patches. Move all menuconfig command specific changes under devtool menuconfig command patch (3/3). changelog v4 1. create a new function that implements the creation of symbolic links for oe-local-files to workspace within _extract_sourcei(). This avoids code duplication and allows the function to be reused within devtool modify when copying source from work-shared to devtool workspace. 2. use check_workspace_recipe() within menuconfig.py changelog v5 1. test against devtool oe-selftests and add missing function imports 2. rename function name from symblink_oelocal_files_srctree to symlink_oelocal_files_srctree 3. fix indendation Sai Hari Chandana Kalluri (3): devtool/standard.py: Update devtool modify to copy source from work-shared if its already downloaded devtool/standard.py: Create a copy of kernel source within work-shared if not present devtool: provide support for devtool menuconfig command scripts/lib/devtool/menuconfig.py | 79 scripts/lib/devtool/standard.py | 147 +++--- 2 files changed, 202 insertions(+), 24 deletions(-) create mode 100644 scripts/lib/devtool/menuconfig.py -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 6/6] waf: python2 -> python3
On Thu, 11 Jul 2019 at 11:26, Burton, Ross wrote: > > On Thu, 11 Jul 2019 at 03:59, Robert Yang wrote: > > On 6/28/19 8:15 PM, Burton, Ross wrote: > > > Did you just do the minimum required, or take a new copy of waf from > > > upstream? > > > > > > (https://gitlab.com/ita1024/waf/) > > > > I checked the one from upstream, it is still python2. The waf is the only > > one > > which still requires python2 in oe-core. We can get rid of python2 after > > this > > patch, what's your opinion, please? > > If that's the case then YES YES YES. :) Follow-up: do you mean remove python2 from HOSTTOOLS, or the recipe from oe-core? $ bitbake -g world $ grep -- '-> "python"' recipe-depends.dot "kernel-devsrc" -> "python" "ltp" -> "python" "meta-world-pkgdata" -> "python" "packagegroup-core-tools-profile" -> "python" "packagegroup-core-tools-testapps" -> "python" "packagegroup-self-hosted" -> "python" "perf" -> "python" "python-nose" -> "python" "python-numpy" -> "python" "python-scons" -> "python" "python-setuptools" -> "python" Nothing depends on the python-* in core, we can ignore the packagegroups, so that leaves kernel-devsrc, ltp, and perf. Also u-boot uses nativepython. HOSTTOOLS is more complicated and there's still plenty of pieces that use host python. I've an old poky-contrib:ross/nopy2 branch that fixes a few more users of host python2 that needs rebasing and retesting. Ross Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 6/6] waf: python2 -> python3
On Thu, 11 Jul 2019 at 03:59, Robert Yang wrote: > On 6/28/19 8:15 PM, Burton, Ross wrote: > > Did you just do the minimum required, or take a new copy of waf from > > upstream? > > > > (https://gitlab.com/ita1024/waf/) > > I checked the one from upstream, it is still python2. The waf is the only one > which still requires python2 in oe-core. We can get rid of python2 after this > patch, what's your opinion, please? If that's the case then YES YES YES. :) Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] u-boot: Provide tasks to generate default U-Boot environment(s) images
Hi,
> On 7/9/19 7:20 AM, Lukasz Majewski wrote:
> > This change provides tasks to generate default U-Boot environment
> > images from built U-Boot (via. get_default_envs.sh script).
> >
> > Those images then can be used to generate wic images (with e.g.
> > eMMC layout). With such approach the end user doesn't see the "CRC
> > environment" error after the first boot.
> >
> > Moreover, those are built per MACHINE (as u-boot itself is) so then
> > could be used in SWUpdate scenarios with single tar'ed archive with
> > multiple MACHINE specific *.swu images.
> I like this idea.
>
>
> >
> > It is also possible to adjust the *_ENVS_* variables in machine
> > specific conf file.
> Can you give an example on how that is done or what it would look
> like?
This code simply needs to have defined:
UBOOT_ENVS_SIZE in machine conf if two machines use different medium
for storing the envs (e.g. NAND vs SPI-NOR).
>
>
> I have been using this class I created a while back to do just that
>
> https://github.com/akuster/meta-odroid/blob/master/classes/uboot-boot-scr.bbclass
It seems like your class builds the envs from provided values.
Just a hint it is now possible with u-boot to "create" at build time
envs with data provided from a simple text file.
The patch here just extracts default envs from build u-boot.
Part of the wic script:
part u-boot-env --source rawcopy --sourceparams="file=u-boot-env.img"
--ondisk mmcblk --no-table --align 1024
part u-boot-env-r --source rawcopy
--sourceparams="file=u-boot-env.img_r" --ondisk mmcblk --no-table
--align
1032
>
> - armin
>
> > Test:
> > Newest master-next for poky repo - SHA1:
> > eb5b0a0b5e53a6e55a09e66489d3f24d0c6232ee MACHINE =
> > "beaglebone-yocto" in local.conf bitbake virtual/bootloader
> >
> >
> > As a result following links are available in deploy directory:
> > u-boot-env.img{_r}.
> >
> > Signed-off-by: Lukasz Majewski
> > ---
> > meta/recipes-bsp/u-boot/u-boot.inc | 41
> > ++ 1 file changed, 41
> > insertions(+)
> >
> > diff --git a/meta/recipes-bsp/u-boot/u-boot.inc
> > b/meta/recipes-bsp/u-boot/u-boot.inc index 9a754fd09b..e0ccf1ce1f
> > 100644 --- a/meta/recipes-bsp/u-boot/u-boot.inc
> > +++ b/meta/recipes-bsp/u-boot/u-boot.inc
> > @@ -331,3 +331,44 @@ do_deploy () {
> > }
> >
> > addtask deploy before do_build after do_compile
> > +
> > +# Extract default envs from build U-Boot
> > +DEFAULT_UBOOT_ENVS_FILE ?= "u-boot-env"
> > +DEFAULT_ENVS ?= "${DEFAULT_UBOOT_ENVS_FILE}.txt"
> > +UBOOT_ENVS_DEFAULT ?=
> > "${DEFAULT_UBOOT_ENVS_FILE}-${MACHINE}-${PV}-${PR}.img"
> > +UBOOT_ENVS_SIZE ?= "65536" +
> > +# Generate default environment
> > +do_gen_default_envs[doc] = "Generate image with default U-Boot
> > environment(s)" +do_gen_default_envs () {
> > +${B}/source/scripts/get_default_envs.sh ${B} >
> > ${B}/${DEFAULT_ENVS} +
> > +# Generate env image
> > +${B}/tools/mkenvimage -s ${UBOOT_ENVS_SIZE} -o
> > ${B}/${UBOOT_ENVS_DEFAULT} ${B}/${DEFAULT_ENVS} +
> > +# Generate redundant env image
> > +${B}/tools/mkenvimage -r -s ${UBOOT_ENVS_SIZE} -o
> > ${B}/${UBOOT_ENVS_DEFAULT}_r ${B}/${DEFAULT_ENVS} +
> > +rm ${B}/${DEFAULT_ENVS}
> > +}
> > +
> > +addtask gen_default_envs before do_deploy after do_compile
> > +
> > +# Deploy default environment
> > +do_deploy_default_envs[doc] = "Copy images with default U-Boot
> > environment to deployment directory" +do_deploy_default_envs () {
> > +
> > + install -d ${DEPLOYDIR}
> > +
> > + install ${B}/${UBOOT_ENVS_DEFAULT}
> > ${DEPLOYDIR}/${UBOOT_ENVS_DEFAULT}
> > + install ${B}/${UBOOT_ENVS_DEFAULT}_r
> > ${DEPLOYDIR}/${UBOOT_ENVS_DEFAULT}_r +
> > + cd ${DEPLOYDIR}
> > + ln -sf ${UBOOT_ENVS_DEFAULT} ${DEFAULT_UBOOT_ENVS_FILE}.img
> > + ln -sf ${UBOOT_ENVS_DEFAULT}_r
> > ${DEFAULT_UBOOT_ENVS_FILE}.img_r +
> > + rm ${B}/${UBOOT_ENVS_DEFAULT}
> > + rm ${B}/${UBOOT_ENVS_DEFAULT}_r
> > +}
> > +
> > +addtask deploy_default_envs before do_deploy after
> > do_gen_default_envs
>
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lu...@denx.de
pgp1nhur_fw8o.pgp
Description: OpenPGP digital signature
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] RDEPENDS libstdc++ error
Hi, I have a third party tool which I was packaging in my image based upon Yocto 1.6 Now I am upgrading to Yocto 2.7 and the recipe which packages third party tool is generating following error: requires libstdc++.so.6(CXXABI_1.3), but no providers found in RDEPENDS_test-util? [file-rdeps] requires libstdc++.so.6(GLIBCXX_3.4), but no providers found in RDEPENDS_test-util? [file-rdeps] Is there a way to fix this without asking vendor to provide a new version of tool? Thanks Ankur -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] nss:upgrade 3.44.1 -> 3.45
-Upgrade from nss_3.44.1.bb to nss_3.45.bb.
Signed-off-by: Zang Ruochen
---
meta/recipes-support/nss/{nss_3.44.1.bb => nss_3.45.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/nss/{nss_3.44.1.bb => nss_3.45.bb} (98%)
diff --git a/meta/recipes-support/nss/nss_3.44.1.bb
b/meta/recipes-support/nss/nss_3.45.bb
similarity index 98%
rename from meta/recipes-support/nss/nss_3.44.1.bb
rename to meta/recipes-support/nss/nss_3.45.bb
index acef0a6..e89e7d6 100644
--- a/meta/recipes-support/nss/nss_3.44.1.bb
+++ b/meta/recipes-support/nss/nss_3.45.bb
@@ -33,8 +33,8 @@ SRC_URI =
"http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/${VERSIO
file://system-pkcs11.txt \
"
-SRC_URI[md5sum] = "511a37f35650812283274694b98c20b2"
-SRC_URI[sha256sum] =
"fce4cb80c989cde35416ecbe55920856015a35151c4f21be64470e4dd4de12f8"
+SRC_URI[md5sum] = "f1752d7223ee9d910d551e57264bafa8"
+SRC_URI[sha256sum] =
"112f05223d1fde902c170966bfc6f011b24a838be16969b110ecf2bb7bc24e8b"
UPSTREAM_CHECK_URI =
"https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Releases;
UPSTREAM_CHECK_REGEX = "NSS_(?P.+)_release_notes"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
