[yocto] [meta-cgl][PATCH] openais: upgrade from 1.1.3 to 1.1.4
Signed-off-by: Lei Maohui
---
meta-cgl-common/recipes-cgl/openais/openais_1.1.3.bb | 19 ---
meta-cgl-common/recipes-cgl/openais/openais_1.1.4.bb | 18 ++
2 files changed, 18 insertions(+), 19 deletions(-)
delete mode 100644 meta-cgl-common/recipes-cgl/openais/openais_1.1.3.bb
create mode 100644 meta-cgl-common/recipes-cgl/openais/openais_1.1.4.bb
diff --git a/meta-cgl-common/recipes-cgl/openais/openais_1.1.3.bb
b/meta-cgl-common/recipes-cgl/openais/openais_1.1.3.bb
deleted file mode 100644
index f4563c9..000
--- a/meta-cgl-common/recipes-cgl/openais/openais_1.1.3.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-DESCRIPTION = "Implementation of the Service Availability Forum Application
Interface Specification (AIS)"
-LICENSE = "BSD"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=4cb00dd52a063edbece6ae248a2ba663"
-DEPENDS = "cluster-glue corosync"
-
-# ftp://f...@openais.org/downloads/openais-${PV}/openais-${PV}.tar.gz
-
-SRC_URI = " \
- ftp://f...@tux.rainside.sk/gentoo/distfiles/openais-${PV}.tar.gz \
- file://fix-lcrso-linkage.patch \
-file://build-cleanup-configure-ac.patch \
-file://openais-fix-bash.patch \
- "
-SRC_URI[md5sum] = "13d8d590f806fb396d750b086c6c0b78"
-SRC_URI[sha256sum] =
"eeef58dd2df3eb16ba68b3fbdc6f0d4dfb537443f1c091ec6f0431594f2f00b6"
-
-inherit autotools pkgconfig
-
-FILES_${PN}-dbg += "${libexecdir}/lcrso/.debug"
diff --git a/meta-cgl-common/recipes-cgl/openais/openais_1.1.4.bb
b/meta-cgl-common/recipes-cgl/openais/openais_1.1.4.bb
new file mode 100644
index 000..69934a5
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/openais/openais_1.1.4.bb
@@ -0,0 +1,18 @@
+DESCRIPTION = "Implementation of the Service Availability Forum Application
Interface Specification (AIS)"
+LICENSE = "BSD"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=4cb00dd52a063edbece6ae248a2ba663"
+DEPENDS = "cluster-glue corosync"
+
+
+SRC_URI = " \
+ftp://f...@tux.rainside.sk/gentoo/distfiles/openais-${PV}.tar.gz \
+file://fix-lcrso-linkage.patch \
+file://build-cleanup-configure-ac.patch \
+file://openais-fix-bash.patch \
+ "
+SRC_URI[md5sum] = "e500ad3c49fdc45d8653f864e80ed82c"
+SRC_URI[sha256sum] =
"974b4959f3c401c16156dab31e65a6d45bbf84dd85a88c2a362712e738c06934"
+
+inherit autotools pkgconfig
+
+FILES_${PN}-dbg += "${libexecdir}/lcrso/.debug"
--
1.8.4.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] glibc 2.22
Hi Khem, > glibc 2.22 will release end of this month. For some time I have put > together the update here > > http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/m > aster&id=0 > 2e73ea526d94f21c7ef82eb96b062eff8ebb825 > > It works pretty well for machines I have tested it on ( arm/x86 ) but > would be interested if more wider trial could be carried out and > issues reported between now and release can be addressed. > > Please give it a try if you have spare cycles I tested it on powerpc(e500v2),and did a ltp test. It does work well. Best Regards Lei Maohui > -Original Message- > From: openembedded-core-boun...@lists.openembedded.org > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > Khem Raj > Sent: Tuesday, July 14, 2015 1:37 AM > To: Patches and discussions about the oe-core layer; OpenEmbedded > Devel List; Yocto discussion list > Subject: [OE-core] glibc 2.22 > > Hi All > > glibc 2.22 will release end of this month. For some time I have put > together the update here > > http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/m > aster&id=0 > 2e73ea526d94f21c7ef82eb96b062eff8ebb825 > > It works pretty well for machines I have tested it on ( arm/x86 ) but > would be interested if more wider trial could be carried out and > issues reported between now and release can be addressed. > > Please give it a try if you have spare cycles > > Thanks > -Khem > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] plan about YP 2.0.1
Hello Yang Can you tell me the schedule about the YP 2.0.1? I want to know when YP 2.0.1 will be released and when the merge window will be closed? Best regards Lei -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] plan about YP 2.0.1
Hi Yang > We are targeting the build and ship to QA of YP 2.0.1 rc1 for 1/11. > > The merge window should be around Jan 6th. I got it. Thank you very much. Lei > -Original Message- > From: Robert Yang [mailto:liezhi.y...@windriver.com] > Sent: Tuesday, December 29, 2015 3:16 PM > To: Lei, Maohui > Cc: yocto@yoctoproject.org > Subject: Re: plan about YP 2.0.1 > > > On 12/21/2015 02:00 PM, Lei, Maohui wrote: > > Hello Yang > > > >Can you tell me the schedule about the YP 2.0.1? > >I want to know when YP 2.0.1 will be released and when the merge window > will be closed? > > We are targeting the build and ship to QA of YP 2.0.1 rc1 for 1/11. > > The merge window should be around Jan 6th. > > // Robert > > > > > > > Best regards > > Lei > > > > > > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/2] spdx:It is necessary to define source directory for spdx.
> On 22 September 2014 10:31, Burton, Ross [mailto:ross.bur...@intel.com] wrote:
> > To make sure that when S directory is changed, the spdx info of the package
> will not miss.
>
> It took me a few minutes and looking at the other patches to understand what
> this is doing.
Sorry，my summary is not easy to understand.
> A better summary would be:
> "Add SPDX-specific source tree variable for recipes where $S is a subdirectory
> of the source tree"
>
> To avoid polluting bitbake.bbclass this might work with SPDX_S ?= "${S}" in
> spdx.bbclass.
Thank you for your response.I will modify my patches ,and then re submit them
later.
Thanks,
Lei Maohui
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] question about toaster in yocto 1.7
Hi all I have read the "Toaster Manual 1.7" and have a question : The toaster still can't launch a build in yocto 1.7 ? Thanks, Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] question about toaster in yocto 1.7
Hi Belén > No, I am afraid Toaster still cannot launch builds in Yocto Project 1.7. > We are working on it though, so Toaster should be able to launch builds in > Yocto > Project 1.8. If you want to help us make it happen (contributions sorely > needed), > let me know. Thanks for your reply. Although I am very interested in Toaster, but I'm not sure there is enough time to do this. Cheers Lei Maohui > -Original Message- > From: Barros Pena, Belen [mailto:belen.barros.p...@intel.com] > Sent: Monday, November 10, 2014 7:09 PM > To: Lei, Maohui/雷 茂慧; yocto@yoctoproject.org > Subject: Re: [yocto] question about toaster in yocto 1.7 > > On 10/11/2014 10:23, "Lei, Maohui" wrote: > > >Hi all > > > > I have read the "Toaster Manual 1.7" and have a question : > > The toaster still can't launch a build in yocto 1.7 ? > > Hi Lei, > > No, I am afraid Toaster still cannot launch builds in Yocto Project 1.7. > We are working on it though, so Toaster should be able to launch builds in > Yocto > Project 1.8. If you want to help us make it happen (contributions sorely > needed), > let me know. > > Cheers > > Belén > > > > >Thanks, > > > >Lei Maohui > >-- > >___ > >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] FW: [OE-core][PATCH 1/2] spdx: Provide spdx file that meet SPDX 1.2 Version Specification
Hi all
How about this patch? I have submitted for days, but still no responds.
Cheers
Lei Maohui
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Lei,
> Maohui
> Sent: Tuesday, November 25, 2014 9:32 AM
> To: openembedded-c...@lists.openembedded.org
> Subject: Re: [OE-core] [oe-core][PATCH 1/2] spdx: Provide spdx file that meet
> SPDX 1.2 Version Specification
>
> Hi all
>
> Sorry, commit log is too simple.
>
> These two patches aim to make the spdx file meet the SPDX 1.2 Version
> Specification. The main changes are:
>
> 1. use "curl" command instead of "wget" when get spdx file from FOSSologySPDX
> instance server.
>
>Before apply these patches, the command is :
>wget -qO - --no-check-certificate --timeout=0
> --post-file=xxx/yyy/zzz.tar.gz
> http://localhost//?mod=spdx_license_once&noCopyright=${FOSS_COPYRIGHT}&rec
> ursiveUnpack=${FOSS_RECURSIVE_UNPACK}
>
>After apply these patches, the command is :
>curl http://127.0.0.1/repo/ --noproxy 127.0.0.1 -k -F
> "mod=spdx_license_once" -F "noCopyright=false" -F "jsonOutput=false" -F
> "fullSPDXFlag=true" -F "file=@ xxx/yyy/zzz.tar.gz" -o xxx/yyy/zzz.spdx
>
>Because if use "wget" command,the Mandatory fields of the SPDX
> Specification
> such as the following can't be obtained.
>1) PackageLicenseInfoFromFiles(Package Information)
>2) PackageLicenseDeclared(Package Information)
>3) LicenseID(License Information)
>4) ExtractedText(License Information)
>5) LicenseName(License Information)
>
> 2. In order to avoid the SPDX_S be polluted in the rebuild, I make
> ${WORKDIR}/${SPDX_TEMP_DIR} to save the source after do_patch.
>
> 3. In addition, this patch add some more info that meet the SPDX 1.2 Version
> Specification.
>
> After apply this patch, users only have to add " INHERIT += "spdx" in the
> local.conf file, they can get spdx file that meet the SPDX 1.2 Version
> Specification.
>
>
> Cheers
>
> Lei Maohui
>
>
>
> > -Original Message-
> > From: Lei, Maohui/雷 茂慧
> > Sent: Monday, November 24, 2014 9:49 PM
> > To: openembedded-c...@lists.openembedded.org
> > Cc: Lei, Maohui/雷 茂慧
> > Subject: [oe-core][PATCH 1/2] spdx: Provide spdx file that meet SPDX
> > 1.2 Version Specification
> >
> > Signed-off-by: leimaohui
> > ---
> > meta/classes/spdx.bbclass | 427
> > --
> > 1 file changed, 150 insertions(+), 277 deletions(-)
> >
> > diff --git a/meta/classes/spdx.bbclass b/meta/classes/spdx.bbclass
> > index
> > 454c53e..9f0f120 100644
> > --- a/meta/classes/spdx.bbclass
> > +++ b/meta/classes/spdx.bbclass
> > @@ -15,178 +15,179 @@
> > # SPDX file will be output to the path which is defined
> > as[SPDX_MANIFEST_DIR] # in ./meta/conf/licenses.conf.
> >
> > +SPDXOUTPUTDIR = "${WORKDIR}/spdx_output_dir"
> > SPDXSSTATEDIR = "${WORKDIR}/spdx_sstate_dir"
> >
> > # If ${S} isn't actually the top-level source directory, set SPDX_S
> > to point at # the real top-level directory.
> > +
> > SPDX_S ?= "${S}"
> >
> > python do_spdx () {
> > import os, sys
> > -import json, shutil
> > +import json
> >
> > info = {}
> > info['workdir'] = d.getVar('WORKDIR', True)
> > -info['sourcedir'] = d.getVar('SPDX_S', True)
> > -info['pn'] = d.getVar('PN', True)
> > -info['pv'] = d.getVar('PV', True)
> > +info['pn'] = d.getVar( 'PN', True )
> > +info['pv'] = d.getVar( 'PV', True )
> > +info['package_download_location'] = d.getVar( 'SRC_URI', True
> > + ).split()[0]
> > info['spdx_version'] = d.getVar('SPDX_VERSION', True)
> > info['data_license'] = d.getVar('DATA_LICENSE', True)
> > +info['creator'] = {}
> > +info['creator']['Tool'] = d.getVar('CREATOR_TOOL', True)
> > +info['license_list_version'] = d.getVar('LICENSELISTVERSION', True)
> > +info['package_homepage'] = d.getVar('HOMEPAGE', True)
> > +info['package_summary'] = d.getVar('SUMMARY', True)
> >
> > -sstatedir = d.getVar(&#x
[yocto] [meta-cgl][PATCH] cluster: add new recipe
This is the development site for several related linux clustering components.
Signed-off-by: Lei Maohui
---
.../recipes-cgl/cluster/cluster_3.2.0.bb | 63 ++
1 file changed, 63 insertions(+)
create mode 100644 meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
diff --git a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
new file mode 100644
index 000..2d6b49c
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
@@ -0,0 +1,63 @@
+Summanry = "Red Hat Cluster"
+DESCRIPTION = "Red Hat Cluster"
+SECTION = "libs"
+HOMEPAGE = "https://fedorahosted.org/cluster/wiki/HomePage";
+
+SRC_URI = "https://fedorahosted.org/releases/c/l/cluster/${BP}.tar.xz";
+
+SRC_URI[md5sum] = "3f496dbecaea367af5a5e81d2e8dcab8"
+
+LICENSE = "GPL-2.0 LGPL-2.0"
+LIC_FILES_CHKSUM =
"file://doc/README.licence;md5=ee8ae43af5ea09f12ca7f7a649764cb0"
+
+PR = "r1"
+
+DEPENDS = "corosync dbus openldap openais libxml2 ncurses perl zlib"
+
+FILES_${PN} += "/lib/udev/rules.d/51-dlm.rules \
+${localstatedir}/run "
+FILES_${PN}-doc += "/usr/share/man3/* /usr/share/man8/*"
+
+do_configure () {
+CFLAGS="${TARGET_CFLAGS}" \
+CCFLAGS="${TARGET_CFLAGS}" \
+CXXFLAGS="${TARGET_CFLAGS}" \
+./configure \
+--without_rgmanager \
+--disable_kernel_check \
+--without_cman \
+--without_fence \
+--without_bindings \
+--without_group \
+--without_config \
+2>&1
+}
+
+do_compile () {
+pwd
+CFLAGS="${TARGET_CFLAGS}" \
+make libdir=${STAGING_LIBDIR} incdir=${STAGING_INCDIR} \
+CC=${TARGET_SYS}-gcc
+}
+do_install () {
+rm -rf ${D}
+make install DESTDIR=${D} libdir=${D}/usr/lib sbindir=${D}/usr/sbin \
+ mandir=${D}/usr/share docdir=${D}/usr/share/doc
+
+## tree fix up
+# /etc/sysconfig/cman
+mkdir -p ${D}/etc/sysconfig
+
+# logrotate name
+mv ${D}/etc/logrotate.d/cluster ${D}/etc/logrotate.d/cman
+# fix library permissions or strip helpers won't work.
+find ${D} -name "lib*.so.*" -exec chmod 0755 {} \;
+# fix lcrso permissions or strip helpers won't work.
+find ${D} -name "*.lcrso" -exec chmod 0755 {} \;
+# remove docs
+rm -rf ${D}${datadir}/doc/cluster
+rm -rf ${D}${localstatedir}/run
+rm -rf ${D}${localstatedir}/lib
+rm -rf ${D}${localstatedir}/log
+rmdir --ignore-fail-on-non-empty ${D}${localstatedir}
+}
--
1.8.4.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format
Hi Alex > Lei Maohui did you experience this error when you tested the recipe? When I bitbake the cluster,I didn't met the error. Qian's target is x86_64, my target is x86, maybe it was the reason why I didn't meet the error. Cheers Lei Maohui > -Original Message- > From: Alexandru Vaduva [mailto:alexandru.vad...@enea.com] > Sent: Tuesday, January 20, 2015 7:10 PM > To: Qian, Lei > Cc: yocto@yoctoproject.org; Lei, Maohui > Subject: RE: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format > > Yes but openldap is a dependency brought up by the cluster recipe. > Proof: > DEPENDS = "corosync dbus openldap openais libxml2 ncurses perl zlib" > > Lei Maohui did you experience this error when you tested the recipe? > > > Alex Vaduva > > -Original Message- > From: Qian Lei [mailto:qianl.f...@cn.fujitsu.com] > Sent: Monday, January 19, 2015 2:58 PM > To: Alexandru Vaduva > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format > > On Mon, 19 Jan 2015 11:32:35 + > Alexandru Vaduva wrote: > > > Does this fix the error I encounter when building the package. > > The log is attached to this email and is also available in the > > bugzilla > > issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7176 > > Actually no. This patch use the kernel source in bitbake world instead of that > on the host. This error only appeared on my build enviroment. > > But your error is to build openldap, not cluster. > > > > > -Original Message- > > From: yocto-boun...@yoctoproject.org > > [mailto:yocto-boun...@yoctoproject.org] > > On Behalf Of Qian Lei Sent: Monday, January 19, 2015 12:08 PM > > To: yocto@yoctoproject.org > > Subject: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and > > format > > > > Use KERNEL_SRC instead of hardcode path in configure. Also fix license > > format. > > > > *** BLURB HERE *** > > > > Qian Lei (2): > > cluster: Fix license format > > cluster: Add a patch to fix the path of kernel source > > > > .../cluster/0001-Fix-the-kernel-source-patch.patch | 38 > > ++ .../recipes-cgl/cluster/cluster_3.2.0.bb > | > > 5 +-- 2 files changed, 41 insertions(+), 2 deletions(-) create mode > > 100644 > > meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source > > -patch.patch > > > > -- > > 1.8.3.1 > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > -- > Qian Lei -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] When I build kernel with toolchain comes from yocto, I met an issue
Hi all, I compiled my kernel by toolchain that supported by yocto 1.7. The following is my steps: 1. Run the following command to install the toolchain. # ./poky-lsb-glibc-x86_64-meta-toolchain-ppce500v2-toolchain-1.7.sh 2. Set up the cross-development environment: # . /opt/poky-lsb/1.7/environment-setup-ppce500v2-poky-linux-gnuspe And then, I compiled the kernel source. But an error occurred: powerpc-poky-linux-gnuspe-ld: unrecognized option '-Wl,-O1' powerpc-poky-linux-gnuspe-ld: use the --help option for usage information make[1]: *** [init/mounts.o] Error 1 make: *** [init] Error 2 I have to unset "LDFLAGS" to continue the build. Is there some wrong with my step? Is there some good method to build a kernel source by the toolchain? Cheers Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] libidn_0.6.14: fix the QA Issue
To fix the QA Issue as following:
ERROR: QA Issue: libidn: Files/directories were installed but not shipped
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/punycode.el
/usr/share/emacs/site-lisp/idna.el [installed-vs-shipped]
Signed-off-by: Lei Maohui
---
meta/recipes-extended/libidn/libidn_0.6.14.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/libidn/libidn_0.6.14.bb
b/meta/recipes-extended/libidn/libidn_0.6.14.bb
index ff8d345..4df1d08 100644
--- a/meta/recipes-extended/libidn/libidn_0.6.14.bb
+++ b/meta/recipes-extended/libidn/libidn_0.6.14.bb
@@ -29,4 +29,5 @@ do_configure_prepend() {
do_install_append() {
rm -rf ${D}${libdir}/Libidn.dll
+ rm -rf ${D}${datadir}/emacs
}
--
1.8.4.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] libidn_0.6.14: fix the QA Issue
Hi Ross
> Patches for oe-core should go to the openembedded-core@ mailing list, not
> yocto@. But thanks, I've queued this for master.
I got it. Thank you .
Lei
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, January 23, 2015 10:53 PM
To: Lei, Maohui/雷 茂慧
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [PATCH] libidn_0.6.14: fix the QA Issue
Hi Lei,
Patches for oe-core should go to the openembedded-core@ mailing list, not
yocto@. But thanks, I've queued this for master.
Ross
On 23 January 2015 at 04:15, Lei Maohui
mailto:leimao...@cn.fujitsu.com>> wrote:
To fix the QA Issue as following:
ERROR: QA Issue: libidn: Files/directories were installed but not shipped
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/punycode.el
/usr/share/emacs/site-lisp/idna.el [installed-vs-shipped]
Signed-off-by: Lei Maohui
mailto:leimao...@cn.fujitsu.com>>
---
meta/recipes-extended/libidn/libidn_0.6.14.bb<http://libidn_0.6.14.bb> | 1 +
1 file changed, 1 insertion(+)
diff --git
a/meta/recipes-extended/libidn/libidn_0.6.14.bb<http://libidn_0.6.14.bb>
b/meta/recipes-extended/libidn/libidn_0.6.14.bb<http://libidn_0.6.14.bb>
index ff8d345..4df1d08 100644
--- a/meta/recipes-extended/libidn/libidn_0.6.14.bb<http://libidn_0.6.14.bb>
+++ b/meta/recipes-extended/libidn/libidn_0.6.14.bb<http://libidn_0.6.14.bb>
@@ -29,4 +29,5 @@ do_configure_prepend() {
do_install_append() {
rm -rf ${D}${libdir}/Libidn.dll
+ rm -rf ${D}${datadir}/emacs
}
--
1.8.4.2
--
___
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] When I build kernel with toolchain comes from yocto, I met an issue
ping > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] > On Behalf Of Lei, Maohui > Sent: Friday, January 23, 2015 10:37 AM > To: yocto@yoctoproject.org > Subject: [yocto] When I build kernel with toolchain comes from yocto, I met > an issue > > Hi all, > > I compiled my kernel by toolchain that supported by yocto 1.7. > The following is my steps: > 1. Run the following command to install the toolchain. ># ./poky-lsb-glibc-x86_64-meta-toolchain-ppce500v2-toolchain-1.7.sh > > 2. Set up the cross-development environment: ># . /opt/poky-lsb/1.7/environment-setup-ppce500v2-poky-linux-gnuspe > > And then, I compiled the kernel source. But an error occurred: > -- > -- > powerpc-poky-linux-gnuspe-ld: unrecognized option '-Wl,-O1' > powerpc-poky-linux-gnuspe-ld: use the --help option for usage information > make[1]: *** [init/mounts.o] Error 1 > make: *** [init] Error 2 > -- > -- > > I have to unset "LDFLAGS" to continue the build. > > Is there some wrong with my step? Is there some good method to build a kernel > source by the toolchain? > > Cheers > > Lei Maohui > -- > ___ > 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] Help -- Where can I get the LSB test log
Hi all Was LSB test executed in yocto 1.7.1 release？ Where can I get the LSB test log and result? Best Regards, Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help -- Where can I get the LSB test log
Hi Yi > The log should be in /var/opt/lsb/test/manager/results/ > sorry，my expression is not very clear。 >From https://wiki.yoctoproject.org/wiki/Yocto_1.7_Overall_Test_Plan , I knew >LSB test was executed on target that made by yocto 1.7.1 release. So , I want to get the LSB test history of the yocto 1.7.1 release. Lei > -Original Message- > From: Yi Zhao [mailto:yi.z...@windriver.com] > Sent: Thursday, January 29, 2015 10:34 AM > To: Lei, Maohui/雷 茂慧; yocto@yoctoproject.org > Subject: Re: [yocto] Help -- Where can I get the LSB test log > > The log should be in /var/opt/lsb/test/manager/results/ > > Yi > > 在 2015年01月29日 10:04, Lei, Maohui 写道: > > Hi all > > > > Was LSB test executed in yocto 1.7.1 release？ Where can I get the LSB test > log and result? > > > > Best Regards, > > Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] When I build kernel with toolchain comes from yocto, I met an issue
Hi Paul I got it. Thank you very much. Cheers Lei > -Original Message- > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] > Sent: Tuesday, January 27, 2015 8:15 PM > To: Lei, Maohui/雷 茂慧 > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] When I build kernel with toolchain comes from yocto, I > met an issue > > On Friday 23 January 2015 02:36:30 Lei, Maohui wrote: > > I compiled my kernel by toolchain that supported by yocto 1.7. > > The following is my steps: > > 1. Run the following command to install the toolchain. > ># ./poky-lsb-glibc-x86_64-meta-toolchain-ppce500v2-toolchain-1.7.sh > > > > 2. Set up the cross-development environment: > ># . /opt/poky-lsb/1.7/environment-setup-ppce500v2-poky-linux-gnuspe > > > > And then, I compiled the kernel source. But an error occurred: > > -- > > -- > > powerpc-poky-linux-gnuspe-ld: unrecognized option '-Wl,-O1' > > powerpc-poky-linux-gnuspe-ld: use the --help option for usage > > information > > make[1]: *** [init/mounts.o] Error 1 > > make: *** [init] Error 2 > > -- > > -- > > > > I have to unset "LDFLAGS" to continue the build. > > > > Is there some wrong with my step? Is there some good method to build a > > kernel source by the toolchain? > > We generally expect the linker to be gcc rather than ld, hence our default > value > of LDFLAGS, so I think for building those bits of software that use ld > directly > (such as the kernel) it is expected that you need to either unset LDFLAGS or > set it to a value that is appropriate for passing directly to ld (i.e. by > removing > -Wl, prefixes from all options). > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help -- Where can I get the LSB test log
Hi Yi > There is a wiki page for it: https://wiki.yoctoproject.org/wiki/LSB_Result Thank you. But this is too old. I want the log of yocto 1.7.1 release. Cheers Lei > -Original Message- > From: Yi Zhao [mailto:yi.z...@windriver.com] > Sent: Thursday, January 29, 2015 11:32 AM > To: Lei, Maohui/雷 茂慧 > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Help -- Where can I get the LSB test log > > Hi Maohui, > > There is a wiki page for it: https://wiki.yoctoproject.org/wiki/LSB_Result > > Yi > > 在 2015年01月29日 11:11, Lei, Maohui 写道: > > Hi Yi > > > >> The log should be in /var/opt/lsb/test/manager/results/ > >> > > sorry，my expression is not very clear。 > > > > >From https://wiki.yoctoproject.org/wiki/Yocto_1.7_Overall_Test_Plan , I > knew LSB test was executed on target that made by yocto 1.7.1 release. > > > > So , I want to get the LSB test history of the yocto 1.7.1 release. > > > > Lei > > > > > >> -Original Message- > >> From: Yi Zhao [mailto:yi.z...@windriver.com] > >> Sent: Thursday, January 29, 2015 10:34 AM > >> To: Lei, Maohui/雷 茂慧; yocto@yoctoproject.org > >> Subject: Re: [yocto] Help -- Where can I get the LSB test log > >> > >> The log should be in /var/opt/lsb/test/manager/results/ > >> > >> Yi > >> > >> 在 2015年01月29日 10:04, Lei, Maohui 写道: > >>> Hi all > >>> > >>> Was LSB test executed in yocto 1.7.1 release？ Where can I get the LSB > test > >> log and result? > >>> Best Regards, > >>> Lei Maohui > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] samhain: Avoid empty source archiver
It is better to put necessary work into do_patch task than add a new task.
Otherwise,you can not get correct source code in some functions(such as
archiver.bbclass).
Signed-off-by: Lei Maohui
---
recipes-security/samhain/samhain.inc | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/recipes-security/samhain/samhain.inc
b/recipes-security/samhain/samhain.inc
index 23bc8f5..5c0142b 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -25,17 +25,14 @@ INITSCRIPT_PARAMS ?= "defaults"
PACKAGECONFIG ??= ""
-# We have to unpack the tar ball twice to get to the source.
-# Also as soon as OE gets the tar ball it unpacks and
-# proceeds to apply the patches. But what you still have after
-# the first unpack is another tar ball. So we do a do_unpack_extra()
-# and tell OE to do the second unpack before do_patch(), otherwise
-# do_patch() will fail when trying to apply the patches.
-do_unpack_extra () {
- cd ${WORKDIR}
- tar -xzvf samhain-${PV}.tar.gz
+do_unpack_samhain() {
+cd ${WORKDIR}
+tar -xzvf samhain-${PV}.tar.gz
+}
+
+python do_unpack_append() {
+bb.build.exec_func('do_unpack_samhain', d)
}
-addtask unpack_extra after do_unpack before do_patch
do_configure_prepend_arm() {
export sh_cv___va_copy=yes
--
1.8.4.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH] ocfs2-tools: uppgrade from 1.8.4 to 1.8.5
Signed-off-by: Lei Maohui
---
.../distro/include/cgl_common_security_flags.inc | 4 +++
.../disable-ocfs2-stack-user-support.patch | 42 --
.../ocfs2-tools-1.8.5-format-fortify.patch | 13 +++
.../{ocfs2-tools_1.8.4.bb => ocfs2-tools_1.8.5.bb} | 8 ++---
4 files changed, 21 insertions(+), 46 deletions(-)
delete mode 100644
meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/disable-ocfs2-stack-user-support.patch
create mode 100644
meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/ocfs2-tools-1.8.5-format-fortify.patch
rename meta-cgl-common/recipes-cgl/ocfs2-tools/{ocfs2-tools_1.8.4.bb =>
ocfs2-tools_1.8.5.bb} (94%)
diff --git a/meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc
b/meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc
index 42c612c..a2f9857 100644
--- a/meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc
+++ b/meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc
@@ -1 +1,5 @@
SECURITY_LDFLAGS_remove_pn-audit = "-fstack-protector-strong"
+
+SECURITY_CFLAGS_pn-ocfs2-tools = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_LDFLAGS_pn-ocfs2-tools = ""
+
diff --git
a/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/disable-ocfs2-stack-user-support.patch
b/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/disable-ocfs2-stack-user-support.patch
deleted file mode 100644
index 8d92f0c..000
---
a/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/disable-ocfs2-stack-user-support.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-Only support stack 'o2cb' in init script o2cb.
-
-Source file /etc/init.d/functions rather than /lib/lsb/init-functions which
-doesn't exist in wrlinux. /etc/init.d/functions provides functions killproc
-and pidofproc, and doesn't provides function start_daemon. It doesn't matter
-that start_daemon is used by stack 'user' only.
-
-Upstream-Status: Pending
-
-Signed-off-by: Kai Kang
-diff --git a/vendor/common/o2cb.init.sh b/vendor/common/o2cb.init.sh
-index 2e73108..926e61e 100755
a/vendor/common/o2cb.init.sh
-+++ b/vendor/common/o2cb.init.sh
-@@ -18,11 +18,11 @@
- # Force LC_ALL=C
- export LC_ALL=C
-
--# Let's try to use the LSB functions
--. /lib/lsb/init-functions
-+# Let's try to use the init scripts functions
-+. /etc/init.d/functions
- if [ $? != 0 ]
- then
--echo "Unable to load LSB init functions" >&2
-+echo "Unable to load init scripts functions" >&2
- exit 1
- fi
-
-@@ -72,6 +72,11 @@ VERSION=@@VERSION@@
- # Need this default
- [ -z "$O2CB_STACK" ] && O2CB_STACK=o2cb
-
-+if [ "$O2CB_STACK" != "o2cb" ]; then
-+echo "Invalid cluster stack name \"$O2CB_STACK\""
-+exit 1
-+fi
-+
- configfs_path()
- {
- # Note that this is only valid *after* configfs is loaded
diff --git
a/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/ocfs2-tools-1.8.5-format-fortify.patch
b/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/ocfs2-tools-1.8.5-format-fortify.patch
new file mode 100644
index 000..f8ab313
--- /dev/null
+++
b/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools/ocfs2-tools-1.8.5-format-fortify.patch
@@ -0,0 +1,13 @@
+diff --git a/tunefs.ocfs2/op_query.c b/tunefs.ocfs2/op_query.c
+index 295c185b..40394d15 100644
+--- a/tunefs.ocfs2/op_query.c
b/tunefs.ocfs2/op_query.c
+@@ -339,7 +339,7 @@ static int query_run(struct tunefs_operation *op,
ocfs2_filesys *fs,
+ register_printf_function('O', handle_ro_compat, handle_arginfo);
+
+ query_fs = fs;
+- fprintf(stdout, fmt);
++ fprintf(stdout, fmt, "dummy");
+ query_fs = NULL;
+
+ ocfs2_free(&fmt);
diff --git a/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.4.bb
b/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.5.bb
similarity index 94%
rename from meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.4.bb
rename to meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.5.bb
index 9098fbf..946423e 100644
--- a/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.4.bb
+++ b/meta-cgl-common/recipes-cgl/ocfs2-tools/ocfs2-tools_1.8.5.bb
@@ -12,19 +12,19 @@ SECTION = "System Environment/Base"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-SRC_URI = "git://oss.oracle.com/git/ocfs2-tools.git \
+SRC_URI = "git://github.com/markfasheh/ocfs2-tools \
file://0003-vendor-common-o2cb.ocf-add-new-conf-file.patch \
-file://disable-ocfs2-stack-user-support.patch \
file://ocfs2-fix-compile-error-when-glibc-upgrade.patch \
+file://ocfs2-tools-1.8.5-format-fortify.patch \
file://o2cb.service \
file://ocfs2.service \
"
-SRCREV = "0b8be47d61dbdcd08d21c83f0b3993735b884ef9"
+SRCREV = "f1b4d073f08679f97
[yocto] [meta-cgl][PATCH]heartbeat: Added dependences to fix build error.
Signed-off-by: Lei Maohui
---
meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb
b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb
index cc2643c..35fee43 100644
--- a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb
+++ b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb
@@ -39,7 +39,7 @@ SRC_URI = " \
SRC_URI[md5sum] = "101c8f507b1f407468d5ef15ae6719da"
SRC_URI[sha256sum] =
"851d2add2c129fef9fede764fec80229e1f6e7295e0e979950d10258648b462c"
S = "${WORKDIR}/Heartbeat-3-0-958e11be8686/"
-DEPENDS = "cluster-glue corosync gnutls"
+DEPENDS = "cluster-glue corosync gnutls libxslt-native xmlto-native
docbook-xml-dtd4-native docbook-xsl-stylesheets-native intltool"
RDEPENDS_${PN} += "python"
inherit autotools-brokensep pkgconfig useradd
EXTRA_OECONF = " \
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Why didn't deploy source archive by license from yocto-1.6
Hi, I found that before yocto-1.6, source archives were deployed by license. The following commit changed the directory for deploying source archives: cbcf5b219858b58c4429ee87444eaacc5a7cfa3e But from commit log, there is no explaining about this change. Are there someone who can tell me why. Best regards Lei -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] a new layer that support spdx
Hi all I have submitted a new layer named meta-spdxscanner that can be used to create spdx files to the OpenEmbedded layer index. Compared to the spdx module in oe-core, this layer has features as following: * Easy to use Dosocs2-native has been add into this meta, there is no need to install anything in build server. * Good performance It has better performance than the spdx module in current oe-core, especially in rebuilding. Best regards Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of xrange.
NameError: name 'xrange' is not defined
Signed-off-by: Lei Maohui
---
.../files/0001-To-fix-build-error-of-xrang.patch | 28 ++
.../fail2ban/python3-fail2ban_0.10.4.0.bb | 4
2 files changed, 32 insertions(+)
create mode 100644
recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
diff --git
a/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
new file mode 100644
index 000..7f0812c
--- /dev/null
+++ b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
@@ -0,0 +1,28 @@
+From fe3436d65518099d35c643848cba50253abc249c Mon Sep 17 00:00:00 2001
+From: Lei Maohui
+Date: Thu, 9 May 2019 14:44:51 +0900
+Subject: [PATCH] To fix build error of xrange.
+
+NameError: name 'xrange' is not defined
+
+Signed-off-by: Lei Maohui
+---
+ fail2ban/__init__.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/fail2ban/__init__.py b/fail2ban/__init__.py
+index fa6dcf7..61789a4 100644
+--- a/fail2ban/__init__.py
b/fail2ban/__init__.py
+@@ -82,7 +82,7 @@ strptime("2012", "%Y")
+
+ # short names for pure numeric log-level ("Level 25" could be truncated by
short formats):
+ def _init():
+- for i in xrange(50):
++ for i in range(50):
+ if logging.getLevelName(i).startswith('Level'):
+ logging.addLevelName(i, '#%02d-Lev.' % i)
+ _init()
+--
+2.7.4
+
diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
index 5c887e8..23ef027 100644
--- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
+++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
@@ -2,3 +2,7 @@ inherit setuptools3
require python-fail2ban.inc
RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules
python3-fail2ban"
+
+SRC_URI += " \
+file://0001-To-fix-build-error-of-xrang.patch \
+"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of xrange.
ping
> -Original Message-
> From: Lei, Maohui
> Sent: Friday, April 19, 2019 11:59 AM
> To: yocto@yoctoproject.org
> Cc: Lei, Maohui
> Subject: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of
> xrange.
>
> NameError: name 'xrange' is not defined
>
> Signed-off-by: Lei Maohui
> ---
> .../files/0001-To-fix-build-error-of-xrang.patch | 28
> ++
> .../fail2ban/python3-fail2ban_0.10.4.0.bb | 4
> 2 files changed, 32 insertions(+)
> create mode 100644
> recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
>
> diff --git a/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
> new file mode 100644
> index 000..7f0812c
> --- /dev/null
> +++ b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
> @@ -0,0 +1,28 @@
> +From fe3436d65518099d35c643848cba50253abc249c Mon Sep 17 00:00:00 2001
> +From: Lei Maohui
> +Date: Thu, 9 May 2019 14:44:51 +0900
> +Subject: [PATCH] To fix build error of xrange.
> +
> +NameError: name 'xrange' is not defined
> +
> +Signed-off-by: Lei Maohui
> +---
> + fail2ban/__init__.py | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/fail2ban/__init__.py b/fail2ban/__init__.py
> +index fa6dcf7..61789a4 100644
> +--- a/fail2ban/__init__.py
> b/fail2ban/__init__.py
> +@@ -82,7 +82,7 @@ strptime("2012", "%Y")
> +
> + # short names for pure numeric log-level ("Level 25" could be truncated by
> short formats):
> + def _init():
> +-for i in xrange(50):
> ++for i in range(50):
> + if logging.getLevelName(i).startswith('Level'):
> + logging.addLevelName(i, '#%02d-Lev.' % i)
> + _init()
> +--
> +2.7.4
> +
> diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb b/recipes-
> security/fail2ban/python3-fail2ban_0.10.4.0.bb
> index 5c887e8..23ef027 100644
> --- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> +++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> @@ -2,3 +2,7 @@ inherit setuptools3
> require python-fail2ban.inc
>
> RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules python3-
> fail2ban"
> +
> +SRC_URI += " \
> +file://0001-To-fix-build-error-of-xrang.patch \
> +"
> --
> 2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of xrange.
Hi,
Please merge this patch to warrior branch.
Best regards
Lei
> -Original Message-
> From: Lei, Maohui
> Sent: Friday, April 19, 2019 11:59 AM
> To: yocto@yoctoproject.org
> Cc: Lei, Maohui
> Subject: [yocto] [meta-security][PATCH] python3-fail2ban: Fix build error of
> xrange.
>
> NameError: name 'xrange' is not defined
>
> Signed-off-by: Lei Maohui
> ---
> .../files/0001-To-fix-build-error-of-xrang.patch | 28
> ++
> .../fail2ban/python3-fail2ban_0.10.4.0.bb | 4
> 2 files changed, 32 insertions(+)
> create mode 100644
> recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
>
> diff --git a/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-
> xrang.patch
> new file mode 100644
> index 000..7f0812c
> --- /dev/null
> +++ b/recipes-security/fail2ban/files/0001-To-fix-build-error-of-xrang.patch
> @@ -0,0 +1,28 @@
> +From fe3436d65518099d35c643848cba50253abc249c Mon Sep 17 00:00:00 2001
> +From: Lei Maohui
> +Date: Thu, 9 May 2019 14:44:51 +0900
> +Subject: [PATCH] To fix build error of xrange.
> +
> +NameError: name 'xrange' is not defined
> +
> +Signed-off-by: Lei Maohui
> +---
> + fail2ban/__init__.py | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/fail2ban/__init__.py b/fail2ban/__init__.py
> +index fa6dcf7..61789a4 100644
> +--- a/fail2ban/__init__.py
> b/fail2ban/__init__.py
> +@@ -82,7 +82,7 @@ strptime("2012", "%Y")
> +
> + # short names for pure numeric log-level ("Level 25" could be truncated by
> short formats):
> + def _init():
> +-for i in xrange(50):
> ++for i in range(50):
> + if logging.getLevelName(i).startswith('Level'):
> + logging.addLevelName(i, '#%02d-Lev.' % i)
> + _init()
> +--
> +2.7.4
> +
> diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb b/recipes-
> security/fail2ban/python3-fail2ban_0.10.4.0.bb
> index 5c887e8..23ef027 100644
> --- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> +++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb
> @@ -2,3 +2,7 @@ inherit setuptools3
> require python-fail2ban.inc
>
> RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules python3-
> fail2ban"
> +
> +SRC_URI += " \
> +file://0001-To-fix-build-error-of-xrang.patch \
> +"
> --
> 2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cgl][PATCH 3/3] libhtml-tagset-perl: remove recipe
Hi
I met a depend error when I built meta-cgl(warrior branch) with meta-oe(warrior
branch).
ERROR: Nothing PROVIDES 'libhtml-tagset-perl-native'...
I don't think this patch should be merged to warrior branch, because
libhtml-tagset-perl hasn't been added into meta-oe's warrior branch.
Best regards
Lei
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On
> Behalf Of Yi Zhao
> Sent: Thursday, June 27, 2019 8:39 AM
> To: yocto@yoctoproject.org; adrian.du...@enea.com; alexandru.vad...@linux.com
> Subject: [yocto] [meta-cgl][PATCH 3/3] libhtml-tagset-perl: remove recipe
>
> The libhtml-tagset-perl recipe was added to meta-perl layer with commit:
> 4058e65f3c4e17ad04423f4c9edf8607fe6fdb4f
> We can drop this duplicate recipe.
>
> Signed-off-by: Yi Zhao
> ---
> .../recipes-perl/perl/libhtml-tagset-perl_3.20.bb | 17
> -
> 1 file changed, 17 deletions(-)
> delete mode 100644 meta-cgl-common/recipes-perl/perl/libhtml-tagset-
> perl_3.20.bb
>
> diff --git a/meta-cgl-common/recipes-perl/perl/libhtml-tagset-perl_3.20.bb
> b/meta-cgl-common/recipes-perl/perl/libhtml-tagset-perl_3.20.bb
> deleted file mode 100644
> index 2765cd2..000
> --- a/meta-cgl-common/recipes-perl/perl/libhtml-tagset-perl_3.20.bb
> +++ /dev/null
> @@ -1,17 +0,0 @@
> -DESCRIPTION = "HTML Tagset bits."
> -HOMEPAGE = "http://search.cpan.org/dist/HTML-Tagset/";
> -SECTION = "libs"
> -LICENSE = "Artistic-1.0 | GPL-1.0+"
> -LIC_FILES_CHKSUM =
> "file://README;beginline=60;md5=16ddda2d845a5546f615e6b122d1dbad"
> -PR = "r4"
> -
> -SRC_URI = "http://search.cpan.org/CPAN/authors/id/P/PE/PETDANCE/HTML-Tagset-
> ${PV}.tar.gz"
> -
> -S = "${WORKDIR}/HTML-Tagset-${PV}"
> -
> -inherit cpan
> -
> -BBCLASSEXTEND="native"
> -
> -SRC_URI[md5sum] = "d2bfa18fe1904df7f683e96611e87437"
> -SRC_URI[sha256sum] =
> "adb17dac9e36cd011f5243881c9739417fd102fce760f8de4e9be4c7131108e2"
> --
> 2.7.4
>
> --
> ___
> 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-cgl][PATCH] heartbeat:Update the patch for new version.
To fix the patch error as follwing: WARNING: heartbeat-3.0.6-r0 do_patch: QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz Signed-off-by: Lei Maohui --- ...mbership-ccm-Makefile.am-fix-warning.patch | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch index 19691db..e27ed79 100644 --- a/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch +++ b/meta-cgl-common/recipes-cgl/heartbeat/heartbeat/membership-ccm-Makefile.am-fix-warning.patch @@ -1,9 +1,10 @@ -From 30ee44e75da1bc86901b546ea14233d288ce2309 Mon Sep 17 00:00:00 2001 -From: Li xin -Date: Tue, 9 Dec 2014 18:15:51 +0900 +From a5e1060c233513cdfc494be410032e6d4ed6f916 Mon Sep 17 00:00:00 2001 +From: Lei Maohui +Date: Mon, 30 Sep 2019 12:42:41 +0900 Subject: [PATCH] membership/ccm/Makefile.am: fix warning -The compile log indicates that host include and/or library paths were used +The compile log indicates that host include and/or library paths were +used Upstream-Status: pending @@ -13,18 +14,18 @@ Signed-off-by: Li Xin 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/membership/ccm/Makefile.am b/membership/ccm/Makefile.am -index 105069a..2a89de1 100644 +index eeb8eee..47a6452 100644 --- a/membership/ccm/Makefile.am +++ b/membership/ccm/Makefile.am @@ -22,7 +22,7 @@ MAINTAINERCLEANFILES= Makefile.in - INCLUDES= -I$(top_builddir)/include -I$(top_srcdir)/include \ + AM_CPPFLAGS = -I$(top_builddir)/include -I$(top_srcdir)/include \ -I$(top_builddir)/linux-ha -I$(top_srcdir)/linux-ha \ -I$(top_builddir)/libltdl -I$(top_srcdir)/libltdl \ --I$(includedir)/clplumbing +-I$(lt_sysroot)$(includedir)/clplumbing - hadir = $(sysconfdir)/ha.d - halibdir = $(libdir)/@HB_PKG@ + halibexecdir = $(libexecdir)/@HB_PKG@ + ccmlibdir = $(halibexecdir) -- -1.8.4.2 +2.17.1 -- 2.17.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
