Re: [yocto] Git tool/command problems with YOCTO Open Source repos
Hello to all, After some time I sorted out some of the confusion about git tool. The tags I requested to be added to the repos, this could be done by using git clone, combined with git branch -a command and customized script (adding git tags), which could be added to additional configuration of the local repo to add customized tags. As for KAS tool, the latest kas-bbb-thud.yml file is added for whoever uses KAS tool, for the quick building of the whole BBB repos with thud repos' commits. File is verified, it clones repos, and then bitbakes all of them (for two basic builds, core-image-minimal and core-image-base). This is ONLY applicable for Beagle Bone Black platform, one widely used as Open Source referent platform. Thank you all, Zoran Stojsavljevic ___ On Wed, Nov 28, 2018 at 1:51 PM Burton, Ross wrote: > > On Wed, 28 Nov 2018 at 12:42, Zoran Stojsavljevic > wrote: > > > What can you not do with Yocto's git repositories? > > > > Please, refer to my initial email. Not referring to Poky, I guess, the > > Poky repo is equivalent to kernel.org. In other words, everything with > > it can be done with git tool. > > > > I am referring to many others, associated with github. Maybe it is > > ONLY github, which does not support git tool in full extend. > > > > So, as I said/wrote in the initial email. The concrete meta-bbb does > > not support git tag, git describe. > > > > Once I have no tags, I could not do anything with git log. And... You > > can imagine. > > Why does the lack of tags mean you can't do anything with git log? > > Tags are simply a way of naming arbitrary commits, typically "This is > version 1.0". If a repository doesn't make releases then it doesn't > need to use tags. This isn't a problem. > > Ross kas-bbb-thud.yml Description: application/yaml -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Enable PACKAGECONFIG Feature
On Wed, 12 Dec 2018 at 03:42, Mohamed Youseif wrote: > I'm asking about how to enable PACKAGECONFIG feature from local.conf file, > let's say that i have the following pacakgeconfig in a recipe > PACKAGECONFIG = " f1 f2 " > PACKAGECONFIG[f1] = "-DENABLE_f1=ON,-DENABLE_f1=OFF,f1," > > so i need to add line in local.conf file to enable this feature for my image? > I tried to use the following line to loca.conf but it does not help: > > PACKAGECONFIG_pn-_append = "-DENABLE_f1=ON" This is covered in the documentation: https://www.yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#var-PACKAGECONFIG Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][thud][PATCH] tpm2-abrmd: Fix QA error
QA Issue: tpm2-abrmd: Files/directories were installed but not
shipped in any package:
/usr/share/dbus-1
/usr/share/dbus-1/system-services
/usr/share/dbus-1/system-services/com.intel.tss2.Tabrmd.service
Signed-off-by: Daniel Dragomir
---
meta-tpm/recipes-tpm/tpm2-abrmd/tpm2-abrmd_2.0.2.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta-tpm/recipes-tpm/tpm2-abrmd/tpm2-abrmd_2.0.2.bb
b/meta-tpm/recipes-tpm/tpm2-abrmd/tpm2-abrmd_2.0.2.bb
index 951556d..6347379 100644
--- a/meta-tpm/recipes-tpm/tpm2-abrmd/tpm2-abrmd_2.0.2.bb
+++ b/meta-tpm/recipes-tpm/tpm2-abrmd/tpm2-abrmd_2.0.2.bb
@@ -46,7 +46,8 @@ do_install_append() {
install -m 0644 "${WORKDIR}/tpm2-abrmd.default"
"${D}${sysconfdir}/default/tpm2-abrmd"
}
-FILES_${PN} += "${libdir}/systemd/system-preset"
+FILES_${PN} += "${libdir}/systemd/system-preset \
+ ${datadir}/dbus-1"
RDEPENDS_${PN} += "tpm2.0-tss"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Quick confirmation about multilib
Hello, I'm trying to build a 32-bit toolchain for my 64-bit image using multilib and was hoping someone could confirm something for me. I am seeing issues when building lib32-glibc, and I can't tell if it's attempting to build properly. The resulting build files are created in a folder called "x86_64-oemllib32-..." - is this correct? Or should it be "x86-oemllib32" being that it's a 32-bit library? Based on the build errors I'm seeing I'm getting the feeling that it's trying to build a 64-bit toolchain in a 32-bit environment, so if someone could clear this up I would really appreciate it. Thanks, --Niko -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Quick confirmation about multilib
On Wed, 12 Dec 2018 at 16:59, Nicholas Tsirakis wrote: > I'm trying to build a 32-bit toolchain for my 64-bit image using multilib and > was hoping someone could confirm something for me. I am seeing issues when > building lib32-glibc, and I can't tell if it's attempting to build properly. > The resulting build files are created in a folder called > "x86_64-oemllib32-..." - is this correct? Or should it be "x86-oemllib32" > being that it's a 32-bit library? Can you clarify here was should be 32-bit and what should be 64-bit? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Quick confirmation about multilib
Sure, thanks for the reply. The image itself should is 64 bit and I want to add an additional toolchain to my image that can run 32-bit binaries. I am trying to build a 32-bit glibc that will be part of this toolchain. Now, when I go to build, there is a new folder that got created in tmp-glibc for the lib32-* files: tmp-glibc/work/x86-oemllib32-linux/lib32-* and upon entering the lib32-glibc folder, I'm seeing this: tmp-glibc/work/x86-oemllib32-linux/lib32-glibc/2.25-r0/build-x86_64-oemllib32-linux/ I'm just not sure if that "x86_64" in the build folder name is correct. I may be doing something entirely wrong as well; this is my first time using multilib. As an FYI, I have the following to my local.conf: require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" Any clarification is appreciated. On Wed, Dec 12, 2018 at 12:04 PM Burton, Ross wrote: > On Wed, 12 Dec 2018 at 16:59, Nicholas Tsirakis > wrote: > > I'm trying to build a 32-bit toolchain for my 64-bit image using > multilib and was hoping someone could confirm something for me. I am seeing > issues when building lib32-glibc, and I can't tell if it's attempting to > build properly. The resulting build files are created in a folder called > "x86_64-oemllib32-..." - is this correct? Or should it be "x86-oemllib32" > being that it's a 32-bit library? > > Can you clarify here was should be 32-bit and what should be 64-bit? > > Ross > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-kernel-tools][PATCH] tools/kconf_check: modify grep pattern
On 12/11/18 5:12 AM, Hongzhi.Song wrote:
The cmd line, , can't
match all expect config options.
This is because that it is not always space after 'config'
This should say "not always one space". There really should
always just be a single space, but typos do sneak in. I'll
queue the patch shortly.
Bruce
in kernel-source/*/.../Kconfig.
e.g. "config IP_VS_IPV6" in net/netfilter/ipvs/Kconfig
So we should change the cmd to grep '^[ ]*\(menu\)*config\s'.
Signed-off-by: Hongzhi.Song
---
tools/kconf_check | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kconf_check b/tools/kconf_check
index aa86180..20b49cd 100755
--- a/tools/kconf_check
+++ b/tools/kconf_check
@@ -241,7 +241,7 @@ find ${kernel_source} \
# known list of all Kconfig* files. Again, must filter dups.
rm -f ${LOGDIR}/all.cfg
for i in `cat ${LOGDIR}/all.kcf` ; do
-cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config ' | \
+cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config\s' | \
awk '{print "CONFIG_"$2}' >> ${LOGDIR}/all.cfg
done
mv -f ${LOGDIR}/all.cfg ${LOGDIR}/all.cfg~
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-kernel-tools][PATCH] tools/kconf_check: modify grep pattern
Thanks.
So would you help to remedy the commit log while merging the patch?
--Hongzhi
On 12/13/2018 02:45 AM, Bruce Ashfield wrote:
On 12/11/18 5:12 AM, Hongzhi.Song wrote:
The cmd line, , can't
match all expect config options.
This is because that it is not always space after 'config'
This should say "not always one space". There really should
always just be a single space, but typos do sneak in. I'll
queue the patch shortly.
Bruce
in kernel-source/*/.../Kconfig.
e.g. "config IP_VS_IPV6" in net/netfilter/ipvs/Kconfig
So we should change the cmd to grep '^[ ]*\(menu\)*config\s'.
Signed-off-by: Hongzhi.Song
---
tools/kconf_check | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kconf_check b/tools/kconf_check
index aa86180..20b49cd 100755
--- a/tools/kconf_check
+++ b/tools/kconf_check
@@ -241,7 +241,7 @@ find ${kernel_source} \
# known list of all Kconfig* files. Again, must filter dups.
rm -f ${LOGDIR}/all.cfg
for i in `cat ${LOGDIR}/all.kcf` ; do
- cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config ' | \
+ cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config\s' | \
awk '{print "CONFIG_"$2}' >> ${LOGDIR}/all.cfg
done
mv -f ${LOGDIR}/all.cfg ${LOGDIR}/all.cfg~
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
