Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt
On Thu, 04 Feb 2016 07:31:32 shubham.kum...@wipro.com wrote: > That entry is already there in "/conf/local.conf " file as follows:- > > # We default to enabling the debugging tweaks. > EXTRA_IMAGE_FEATURES = "debug-tweaks" > > In addition to the above, I have also added "tools-sdk" and "tools-debug" as > follows in the same file :- > > #Other packages > EXTRA_IMAGE_FEATURES = "tools-sdk" > EXTRA_IMAGE_FEATURES = "tools-debug" > > Is there anything else I'm missing? Er... is that exactly how you are setting the EXTRA_IMAGE_FEATURES value? If it is, = sets the value, it does not add to it, so you're wiping out the previous items. You presumably want to be using += rather than = . Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set
I just checked your master branch and saw the updates on the pkgconfig and cmake files generation. Either we make meta-qt5 look for the GLESv2 package config file to update properly the QMAKE_LIBS_EGL variable. Otherwise we check in meta-raspberrypi that the meta-qt5 is enabled to feed EXTRA_QMAKEVARS_PRE. Let's say that both options should work. The first option could bring some patches to Qt mainstream. The second is quite clean and easy to try. I'll fork your branch and try out the second option. - Have a nice day -Message d'origine- De : Khem Raj [mailto:raj.k...@gmail.com] Envoyé : jeudi 4 février 2016 05:38 À : GUEYTAT Julien Cc : Yannick Kiekens; yocto@yoctoproject.org Objet : Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set On Wed, Feb 3, 2016 at 6:54 AM, GUEYTAT Julien wrote: > Setting properly the variable PACKAGECONFIG_GL to gles2 does NOT update > properly the variable QMAKE_LIBS_EGL. > By default QMAKE_LIBS_EGL = -lEGL > And depending on hardware... it might be something like QMAKE_LIBS_EGL = > -lEGL -lGLESv2 for instance. > And this specific line... "-lEGL -lGLESv2" is only know in the provider of > virtual/libglesv2 ... in this case meta-raspberry. > The BSP layer could provide a package config file which will be read to set > QMAKE_LIBS_EGL properly. > > => Which means we would need each package providing virtual/libglesv2 ... to > provide also a package config file. > > I hope it's clear now. Tell me if I missed something. you can try my fork of meta-raspberrypi I am carrying few patches which fix pkgconfig stuff along with wayland support (wip) > > -Message d'origine- > De : Khem Raj [mailto:raj.k...@gmail.com] Envoyé : mercredi 3 février > 2016 15:45 À : GUEYTAT Julien Cc : Yannick Kiekens; > yocto@yoctoproject.org Objet : Re: [yocto] > [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set > > On Wed, Feb 3, 2016 at 3:46 AM, GUEYTAT Julien > wrote: >> Hi everyone, >> >> >> >> I understand that you are all rewriting the qtbase rule to include at >> least the modification to the QMAKE_LIBS_EGL variable. >> >> The question is: >> >> Could we make somehow some work in meta-qt5 or meta-raspberrypi to >> not have to overwrite the qtbase rule. > > > I dont understand. PAKCAGECONFIGS are specifically desined for this kind of > scenario what problems are you seeing. > >> >> For instance… meta-raspberrypi is providing a package config file for EGL. >> May be you could have meta-qt5 read this package config. >> >> >> >> That’s the question. I’d like to know what the maintainers of those >> two layers think about that. >> >> >> >> Best Regards, >> >> >> >> De : Yannick Kiekens [mailto:yannickkiek...@gmail.com] Envoyé : >> mercredi 3 février 2016 08:41 À : Khem Raj Cc : GUEYTAT Julien; >> yocto@yoctoproject.org Objet : Re: [yocto] >> [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set >> >> >> >> Have a look at this git repo: >> https://github.com/YannickKiekens/meta-qt5-pi >> >> I have build a qt5 eglfs with raspberry pi2 backend on master branch >> yesterday evening >> >> >> >> On Wed, Feb 3, 2016 at 7:08 AM, Khem Raj wrote: >> >> >> >> On Feb 2, 2016, at 8:50 AM, GUEYTAT Julien >> >> wrote: >> >> >> >> Hi, >> >> >> >> It seems that there are some stiff missing between meta-qt5 or >> meta-raspberrypi. >> >> When we set the option gles… to qtbase we don’t get the >> QMAKE_LIBS_EGL set properly. >> >> We can compare a working set of variables in the qt mkspecs directory of qt. >> >> There is one dedicated file for the RaspberryPi2. May be one also for >> RaspberryPi. >> >> Anyway! >> >> How could we set those *_EGL variables properly? And… If they are >> properly set, will qtbase will take them into account? >> >> >> >> I will be happy to propose a patch but I need to get more precision first. >> >> >> >> Firstly show the DISTRO_FEATURES may be you are missing some >> important knobs for EGL >> >> like openGL and gles2 etc. >> >> >> >> Thanks in advance, >> >> >> >> >> >> >> >> Julien GUEYTAT >> >> Ingénieur Informatique >> >> >> >> 1027, avenue du Docteur Julien Lefebre BP27 >> >> 06271 Villeneuve-Loubet Cedex >> >> Fixe : +33 (0) 492 024 545 >> Mob : +33(0) 617 980 383 >> Fax :+33(0) 492 024 546 >> Email : j.guey...@cdssoft.studiel.fr >> >> www : www.studiel.fr >> >> P Pensez Environnement, imprimez seulement si nécessaire >> >> >> >> -- >> ___ >> 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] formfactor: add machconfig for Beaglebone
We need machconfig file to automatically choose between physical and virtual keyboards. [YOCTO #9027] Signed-off-by: Maxin B. John --- meta-yocto-bsp/recipes-bsp/formfactor/formfactor/beaglebone/machconfig | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 meta-yocto-bsp/recipes-bsp/formfactor/formfactor/beaglebone/machconfig diff --git a/meta-yocto-bsp/recipes-bsp/formfactor/formfactor/beaglebone/machconfig b/meta-yocto-bsp/recipes-bsp/formfactor/formfactor/beaglebone/machconfig new file mode 100644 index 000..ffce012 --- /dev/null +++ b/meta-yocto-bsp/recipes-bsp/formfactor/formfactor/beaglebone/machconfig @@ -0,0 +1,3 @@ +# Assume a USB mouse and keyboard are connected +HAVE_TOUCHSCREEN=0 +HAVE_KEYBOARD=1 -- 2.4.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?
I will check that out, thanks! Kind regards, Bartosz Woronicz Engineer, Software Configuration (SCM) NSN - PL/Wroclaw On 03.02.2016 16:40, EXT Burton, Ross wrote: On 3 February 2016 at 14:16, Woronicz, Bartosz ( NSN - PL/Wroclaw) mailto:bartosz.woron...@nokia.com>> wrote: But I need to the sysroot cleanup deliberately, right ? No, that happens on startup (in master and the jethro release). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?
Whoa,
That's great! However I modified it, so the link will be relative
The problem is that it works until you have sstate cache empty, because
after that it doesn't fetch and unpack when already have it in
do_latest_link() {
if [ -n "${WORKDIR}" ]; then
linkname="$(basename $(dirname ${WORKDIR}))/latest"
rm -f $linkname
ln -s ${WORKDIR} $linkname
fi
}
addtask latest_link after do_unpack
Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
NSN - PL/Wroclaw
On 03.02.2016 12:05, EXT Maciek Borzecki wrote:
On śro, 2016-02-03 at 11:13 +0100, Woronicz, Bartosz ( NSN - PL/Wroclaw) wrote:
Let's say I have my package at
host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/
I would like to have symlink created
host-64/tmp/work/x86_64-poky-linux/mypackage/latest -> 1.2.3-r4/
each time the new version is fetched and unpacked. How can I achieve
that ? Which class, task should I append, extend ?
Optionally, I would like to have that for all packages or at least
packages in my meta.
P.S. I asked the same question here:
http://stackoverflow.com/questions/35158764/where-should-i-append-yocto-bitbake-task-to-
create-work-folder-symlink
Put that into a class in your layer, ex. latest-link.bbclass (untested):
do_latest_link() {
if [ -n "${WORKDIR}" ]; then
linkname="$(dirname ${WORKDIR})/latest"
rm -f $linkname
ln -s ${WORKDIR} $linkname
fi
}
addtask latest_link after do_unpack
If you want that applied to all the recipes then add INHERIT += "latest-link"
in your
local.conf. The other way is just to 'inherit latest-link' in individual
recipes.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt
On Thu, 04 Feb 2016 07:31:32 shubham.kum...@wipro.com wrote: > >That entry is already there in "/conf/local.conf " file as follows:- >> > ># We default to enabling the debugging tweaks. > >EXTRA_IMAGE_FEATURES = "debug-tweaks" >> > >In addition to the above, I have also added "tools-sdk" and "tools-debug" as > >follows in the same file :- >> > >#Other packages > >EXTRA_IMAGE_FEATURES = "tools-sdk" > >EXTRA_IMAGE_FEATURES = "tools-debug" >> > >Is there anything else I'm missing? >Er... is that exactly how you are setting the EXTRA_IMAGE_FEATURES value? If >it is, = sets the value, it does not add to it, so you're wiping out the >previous items. You presumably want to be using += rather than = . >Cheers, >Paul Thanks Paul. The issue is solved now. You pointed out the correct mistake :). However, I had been doing the same mistake while building extra packages for qemux86. But it didn't throw any such error, and the virtual machine worked just perfectly fine. However, It was not the same with Galileo. But I would take care of these issues in future. Thanks Paul , Thanks Maciej. Have a Great day ahead !! Thanks, Shubham_K The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto and linux mint 17.3
Up ! nobodies have an idea ? Le Thu, 04 Feb 2016 13:08:00 +0100, a écrit: Hi all, i'm new on yocto and i have a problem to start a buil with my host pc. My pc is under linux mint 17.3 (cinnamon) 64 bits. When i launch a bitbake, i >have this error : ImportError: No module named pysqlite2 /home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/event.py:107: RuntimeWarning: Parent module 'bb' not found while handling absolute >import from bb.msg import BBLogFormatter Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/local/lib/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/event.py", line 107, in print_ui_queue from bb.msg import BBLogFormatter File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/__init__.py", line 77, in from bb import fetch2 as fetch File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/fetch2/__init__.py", line 37, in import bb.persist_data, bb.utils File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/persist_data.py", line 35, in from pysqlite2 import dbapi2 as sqlite3 ImportError: No module named pysqlite2 Error in sys.exitfunc: Traceback (most recent call last): File "/usr/local/lib/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/event.py", line 107, in print_ui_queue from bb.msg import BBLogFormatter File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/__init__.py", line 77, in from bb import fetch2 as fetch File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/fetch2/__init__.py", line 37, in import bb.persist_data, bb.utils File "/home/mls/bin/fsl-release-bsp/sources/poky/bitbake/lib/bb/persist_data.py", line 35, in from pysqlite2 import dbapi2 as sqlite3 ImportError: No module named pysqlite2 apparently bb can't import pysqlite2 ? I already install pip install pysqlite libsqlite3-dev but nothing to solve my problem ... An idea to >resolve this please ? --Utilisant le logiciel de courrier d'Opera : http://www.opera.com/mail/ -- Utilisant le logiciel de courrier d'Opera : http://www.opera.com/mail/-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto and linux mint 17.3
On 4 February 2016 at 12:09, idealsim wrote: > apparently bb can't import pysqlite2 ? I already install pip install > pysqlite libsqlite3-dev but nothing to solve my problem ... An idea to > resolve this please ? > Did that install a pysqlite for python 3? bitbake uses python2. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto and linux mint 17.3
I don't think, probably install by default ! do you think i can remove python 3 to solve the problem ? Le Thu, 04 Feb 2016 13:32:10 +0100, Burton, Ross a écrit: On 4 February 2016 at 12:09, idealsim wrote: apparently bb can't import pysqlite2 ? I already install pip install pysqlite libsqlite3-dev but nothing to solve my problem ... An idea to >>resolve this please ? Did that install a pysqlite for python 3? bitbake uses python2. Ross -- Utilisant le logiciel de courrier d'Opera : http://www.opera.com/mail/-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto and linux mint 17.3
On 4 February 2016 at 12:49, idealsim wrote: > I don't think, probably install by default ! do you think i can remove > python 3 to solve the problem ? > You can if you want, but there's no need. You just need to ensure the required libraries are available to python2. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux 1/2] audit: create audit-go package
This version of audit installs go bindings which are not shipped and
trigger QA warnings. Put them in their own package just like python.
Signed-off-by: Ioan-Adrian Ratiu
---
recipes-security/audit/audit_2.4.4.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes-security/audit/audit_2.4.4.bb
b/recipes-security/audit/audit_2.4.4.bb
index 55a5b12..f512cbc 100644
--- a/recipes-security/audit/audit_2.4.4.bb
+++ b/recipes-security/audit/audit_2.4.4.bb
@@ -55,7 +55,7 @@ like relay events to remote machines or analyze events for
suspicious \
behavior."
PACKAGES =+ "audispd-plugins"
-PACKAGES += "auditd ${PN}-python"
+PACKAGES += "auditd ${PN}-python ${PN}-go"
FILES_${PN} = "${sysconfdir}/libaudit.conf ${base_libdir}/libaudit.so.1*
${base_libdir}/libauparse.so.*"
FILES_auditd += "${bindir}/* ${base_sbindir}/* ${sysconfdir}/*"
@@ -65,6 +65,7 @@ FILES_audispd-plugins +=
"${sysconfdir}/audisp/audisp-remote.conf \
"
FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug"
FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}"
+FILES_${PN}-go = "${libdir}/golang"
FILES_${PN}-dev += "${base_libdir}/*.so ${base_libdir}/*.la
${base_libdir}/pkgconfig/*"
CONFFILES_auditd += "${sysconfdir}/audit/audit.rules"
--
2.7.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux 2/2] libselinux: backport procfs mount fix
libselinux 20160107 ships this change (git commit id 9df49888)
Signed-off-by: Ioan-Adrian Ratiu
---
.../libselinux-mount-procfs-before-check.patch | 74 ++
recipes-security/selinux/libselinux_2.4.bb | 1 +
recipes-security/selinux/libselinux_git.bb | 1 +
3 files changed, 76 insertions(+)
create mode 100644
recipes-security/selinux/libselinux/libselinux-mount-procfs-before-check.patch
diff --git
a/recipes-security/selinux/libselinux/libselinux-mount-procfs-before-check.patch
b/recipes-security/selinux/libselinux/libselinux-mount-procfs-before-check.patch
new file mode 100644
index 000..dc27aaa
--- /dev/null
+++
b/recipes-security/selinux/libselinux/libselinux-mount-procfs-before-check.patch
@@ -0,0 +1,74 @@
+commit 9df498884665d79474b79f0f30d1cd67df11bd3e
+Author: Ben Shelton
+Date: Wed Apr 15 15:56:57 2015 -0500
+
+libselinux: Mount procfs before checking /proc/filesystems
+
+In the case where the SELinux security module is not loaded in the
+kernel and it's early enough in the boot process that /proc has not yet
+been mounted, selinuxfs_exists() will incorrectly return 1, and
+selinux_init_load_policy() will print a message like this to the
+console:
+
+Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory
+
+To fix this, mount the procfs before attempting to open
+/proc/filesystems, and unmount it when done if it was initially not
+mounted. This is the same thing that selinux_init_load_policy() does
+when reading /proc/cmdline.
+
+Signed-off-by: Ben Shelton
+
+Upstream-Status: Accepted
+
+diff --git a/src/init.c b/src/init.c
+index 6d1ef33..179e0d0 100644
+--- a/src/init.c
b/src/init.c
+@@ -11,6 +11,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include "dso.h"
+ #include "policy.h"
+@@ -54,15 +55,20 @@ static int verify_selinuxmnt(const char *mnt)
+
+ int selinuxfs_exists(void)
+ {
+- int exists = 0;
++ int exists = 0, mnt_rc = 0;
+ FILE *fp = NULL;
+ char *buf = NULL;
+ size_t len;
+ ssize_t num;
+
++ mnt_rc = mount("proc", "/proc", "proc", 0, 0);
++
+ fp = fopen("/proc/filesystems", "r");
+- if (!fp)
+- return 1; /* Fail as if it exists */
++ if (!fp) {
++ exists = 1; /* Fail as if it exists */
++ goto out;
++ }
++
+ __fsetlocking(fp, FSETLOCKING_BYCALLER);
+
+ num = getline(&buf, &len, fp);
+@@ -76,6 +82,14 @@ int selinuxfs_exists(void)
+
+ free(buf);
+ fclose(fp);
++
++out:
++#ifndef MNT_DETACH
++#define MNT_DETACH 2
++#endif
++ if (mnt_rc == 0)
++ umount2("/proc", MNT_DETACH);
++
+ return exists;
+ }
+ hidden_def(selinuxfs_exists)
diff --git a/recipes-security/selinux/libselinux_2.4.bb
b/recipes-security/selinux/libselinux_2.4.bb
index e084df2..86ff44c 100644
--- a/recipes-security/selinux/libselinux_2.4.bb
+++ b/recipes-security/selinux/libselinux_2.4.bb
@@ -12,4 +12,5 @@ SRC_URI += "\
file://libselinux-make-SOCK_CLOEXEC-optional.patch \
file://libselinux-define-FD_CLOEXEC-as-necessary.patch \
file://libselinux-get-pywrap-depends-on-selinux.py.patch \
+file://libselinux-mount-procfs-before-check.patch \
"
diff --git a/recipes-security/selinux/libselinux_git.bb
b/recipes-security/selinux/libselinux_git.bb
index 4efab86..33d9e00 100644
--- a/recipes-security/selinux/libselinux_git.bb
+++ b/recipes-security/selinux/libselinux_git.bb
@@ -12,4 +12,5 @@ SRC_URI += "\
file://libselinux-make-SOCK_CLOEXEC-optional.patch \
file://libselinux-define-FD_CLOEXEC-as-necessary.patch \
file://libselinux-get-pywrap-depends-on-selinux.py.patch \
+ file://libselinux-mount-procfs-before-check.patch \
"
--
2.7.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to enable php5 (php_5.5.22.bb) support for postgresql
Hi all!
I´m new to yocto recipes and never posted to this mail list.
I´m trying to include postgresql PDO in PHP.
Something like what is informed using ./configure --help in php source:
-with-pdo-pgsql[=DIR]PDO: PostgreSQL support
My recipe file is php_5.5.21.bb and here are some default config lines:
PACKAGECONFIG[mysql] = "--with-mysql=${STAGING_DIR_TARGET}${prefix} \
--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config \
--with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config \
,--without-mysql --without-mysqli
--without-pdo-mysql \
,mysql5"
PACKAGECONFIG[sqlite3] = "--with-sqlite3=${STAGING_LIBDIR}/.. \
--with-pdo-sqlite=${STAGING_LIBDIR}/.. \
, \
,sqlite3"
PACKAGECONFIG[pgsql] =
"--with-pgsql=${STAGING_DIR_TARGET}${exec_prefix},--without-pgsql,postgresql"
Could somebody tell me how to configure this recipe?
Best regards
Fabiano
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] libQt5Network.so.5 - How does one get that please?
Hi My application has a dependency on libQt5Network.so.5. I have my build configured here: https://github.com/DevOps4Networks/iox-yocto-build/tree/master/conf I expect that some combination of the BBLAYERS and the IMAGE_INSTALL_append should allow me to get that library in my Yocto image. I am not sure which layer has the qtnetwork recipe in it, as I can’t find that here: http://layers.openembedded.org/layerindex/branch/master/layers/ Any ideas gratefully received. Many thanks Nathan — Nathan John Sowatskey Consulting Engineer - Programmable Infrastructure, DevOps, IoT and SDN nat...@nathan.to www.linkedin.com/in/nathandevops XMPP: nathando...@im.koderoot.net Google: nathanjohnsowats...@gmail.com Skype: nathan_sowatskey Twitter: NathanDotTo GitHub: https://github.com/DevOps4Networks http://www.kipling.org.uk/poems_if.htm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Signed RPMs
Hi,
I have been testing out the facility for generating signed RPMs.
It's currently failing to find
'build/tmp/sysroots/x86_64-linux/etc/RPM-GPG-PUBKEY', log listed at end.
I couldn't find a lot of documentation but from what I could find, I added the
following to local.conf:
INHERIT += " sign_rpm"RPM_GPG_NAME = "chris"RPM_GPG_PUBKEY =
"/home/chris/mykey.pub"RPM_GPG_PASSPHRASE_FILE = "/home/chris/mypassphrase"
It needed 'python-pexpect' installing (fedora 22) to run at all but after that
it worked to an extent as I had to correct the stored passphrase to correct
other errors.
At this stage of the build there is very little in
'build/tmp/sysroots/x86_64-linux/etc/' (just quilt related) but I also find it
curious that it is looking for the variable name rather than it value.
Now I was following the the Aug patch notes "'RPM_GPG_PUBKEY =
"" in bitbake config pointing to the public key (in "armor"
format).".
Since then there was a patch "Automatically export public keys used for
package(feed) signing" that obsoletes RPM_GPG_PUBKEY (and overwrites it) but
I'm still not clear how/where to put the public key so it will end up in the
staging directory. Also, 'package_manager.py' copies the file named by
RPM_GPG_PUBKEY to the location os.path.join(self.deploy_dir, 'RPM-GPG-KEY-%s' %
distro_version). I presume this copies from the staging directory to the
deployment directory.
So what I would like to know is where to put the RPM GPG public key so that it
gets copied to the staging directory?
For the time being, I have copied it in by hand.
Thanks,Chris
Summary: 1 task failed:poky/meta/recipes-core/os-release/os-release.bb,
do_compile
DEBUG: Executing python function do_compileERROR: Error executing a python
function in /home/chris/yocto/poky/meta/recipes-core/os-release/os-release.bb:
The stack trace of python calls that resulted in this exception/failure
was:File: '/home/chris/yocto/poky/meta/recipes-core/os-release/os-release.bb',
lineno: 16, function: 0012:distro_version =
d.getVar('DISTRO_VERSION', True) or "oe.0" 0013:
shutil.copy2(rpm_gpg_pubkey,
d.expand('/home/chris/yocto/build/tmp/work/all-poky-linux/os-release/1.0-r0/os-release-1.0/rpm-gpg/RPM-GPG-KEY-%s'
% distro_version)) 0014: 0015: *** 0016:do_compile(d) 0017:File:
'/home/chris/yocto/poky/meta/recipes-core/os-release/os-release.bb', lineno:
13, function: do_compile 0009:do_fetch[noexec] = "1"
0010:do_unpack[noexec] = "1" 0011:do_patch[noexec] = "1"
0012:do_configure[noexec] = "1" *** 0013: 0014:# Other valid fields:
BUILD_ID ID_LIKE ANSI_COLOR CPE_NAME 0015:# HOME_URL
SUPPORT_URL BUG_REPORT_URL 0016:OS_RELEASE_FIELDS = "ID ID_LIKE NAME
VERSION VERSION_ID PRETTY_NAME" 0017:File:
'/usr/lib64/python2.7/shutil.py', lineno: 130, function: copy2 0126:
0127:""" 0128:if os.path.isdir(dst): 0129:dst =
os.path.join(dst, os.path.basename(src)) *** 0130:copyfile(src, dst)
0131:copystat(src, dst) 0132: 0133:def ignore_patterns(*patterns):
0134:"""Function that can be used as copytree() ignore parameter.File:
'/usr/lib64/python2.7/shutil.py', lineno: 82, function: copyfile 0078:
# XXX What about other special files? (sockets, devices...) 0079:
if stat.S_ISFIFO(st.st_mode): 0080:raise
SpecialFileError("`%s` is a named pipe" % fn) 0081: *** 0082:with
open(src, 'rb') as fsrc: 0083:with open(dst, 'wb') as fdst:
0084:copyfileobj(fsrc, fdst) 0085: 0086:def copymode(src,
dst):Exception: IOError: [Errno 2] No such file or directory:
'/home/chris/yocto/build/tmp/sysroots/x86_64-linux/etc/RPM-GPG-PUBKEY'
DEBUG: Python function do_compile finishedERROR: Function failed: do_compile
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH][yocto-autobuilder] nightly-musl: also build core-image-weston
Signed-off-by: Ross Burton
---
buildset-config.controller/nightly-musl.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/buildset-config.controller/nightly-musl.conf
b/buildset-config.controller/nightly-musl.conf
index 9a82e6b..5da90c3 100644
--- a/buildset-config.controller/nightly-musl.conf
+++ b/buildset-config.controller/nightly-musl.conf
@@ -12,7 +12,7 @@ steps: [{'SetDest':{}},
'buildhistory' : False, 'distro': 'poky',
'atextappend' : '\nTCLIBC="musl"\n' }},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
-{'BuildImages': {'images': 'core-image-minimal
core-image-full-cmdline core-image-sato'}},
+{'BuildImages': {'images': 'core-image-minimal
core-image-full-cmdline core-image-sato core-image-weston'}},
{'SendErrorReport': {}},
{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
--
2.7.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][yocto-autobuilder] nightly-musl: also build core-image-weston
> On Feb 4, 2016, at 2:27 PM, Ross Burton wrote:
>
> Signed-off-by: Ross Burton
> ---
> buildset-config.controller/nightly-musl.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/buildset-config.controller/nightly-musl.conf
> b/buildset-config.controller/nightly-musl.conf
> index 9a82e6b..5da90c3 100644
> --- a/buildset-config.controller/nightly-musl.conf
> +++ b/buildset-config.controller/nightly-musl.conf
> @@ -12,7 +12,7 @@ steps: [{'SetDest':{}},
> 'buildhistory' : False, 'distro': 'poky’,
one generic problem I see is that poky packages rpm and rpm does not work with
musl.
when I build core-image-sato with OE-Core it works out fine.
fixing rpm with musl will need some some patching. I was wondering we could use
poky-tiny + opkg combo
for musl.
> 'atextappend' : '\nTCLIBC="musl"\n' }},
> {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
> -{'BuildImages': {'images': 'core-image-minimal
> core-image-full-cmdline core-image-sato'}},
> +{'BuildImages': {'images': 'core-image-minimal
> core-image-full-cmdline core-image-sato core-image-weston'}},
> {'SendErrorReport': {}},
> {'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
>
> --
> 2.7.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Problem solved: succeed in building the image ! Re:RE: Re:RE: [meta-raspberrypi] errors when I "bitbake" animage formyrpi2 B+ board
Hi, everyone: I have spent about 3 days in figuring out this meta-raspberrypi building problem. And today, fortunately, and finally, I figure it out!I should say thanks to everyone that has helped me to work with it. It's because of the internet speed. After connecting the ethernet cable to laptop(rather than use "wifi"),and "bitbake", it's ok to build the image. (though,it took a long time,nearly 8 hours to build,but it doesn't matter!) There is still something not perfect,when I inserted the sd card to my rpi2 B+ board,boot process went wrong,pls refer to the link for detailed informations(http://www.cnblogs.com/tianya-lemon/p/5183008.html) . Maybe it's the reason of vga monitor, so I will try on another monitor when I go to the lab. Again,thank you all who helped me. To geeks. The following is the console informations of the last successful build : == jackzhang1992@ubuntu:~/poky/build$ bitbake rpi-hwup-image Parsing recipes: 100% |#| Time: 00:01:10 Parsing of 921 .bb files complete (0 cached, 921 parsed). 1352 targets, 61 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION= "1.28.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "raspberrypi2" DISTRO= "poky" DISTRO_VERSION= "2.0.1" TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7" TARGET_FPU= "vfp-vfpv4-neon" meta meta-yocto meta-yocto-bsp= "jethro:2fb7ee2628e23d7efc9b041bb9daae7c4a8de541" meta-raspberrypi = "master:6314f668fa14473463bb777ffaf778333fea16eb" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL ftp://invisible-island.net/ncurses/current/ncurses-5.9-20150329.tgz, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.openssl.org/source/openssl-1.0.2d.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL ftp://xmlsoft.org/libxslt//libxslt-1.1.28.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/Pyrex-0.9.9.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL http://freedesktop.org/~hadess/shared-mime-info-1.4.tar.xz, attempting MIRRORS if available WARNING: Failed to fetch URL https://github.com/dosfstools/dosfstools/releases/download/v3.0.28/dosfstools-3.0.28.tar.xz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 1971 tasks of which 9 didn't need to be rerun and all succeeded. Summary: There were 6 WARNING messages shown. jackzhang1992@ubuntu:~/poky/build$ = -- Original -- From: "Karim ATIKI"; Date: Thu, Feb 4, 2016 04:37 PM To: "JackZhang"; Cc: "yocto"; Subject: RE: Re:RE: [yocto] [meta-raspberrypi] errors when I "bitbake" animage formyrpi2 B+ board Hi Jack, Could you provide the content of a log file ? /home/jackzhang1992/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/bcm2835-bootfiles/20151021-r3/temp/log.do_fetch.9874 Karim De : 张健 Envoyé : jeudi 4 février 2016 05:25 À : Karim ATIKI Cc : yocto Objet : Re:RE: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formyrpi2 B+ board Hi, Karim, I have tried "sudo apt-get install curl", then do the "bitbake". But there are stiill many errors. detailed build logs are as follows: "http://www.cnblogs.com/tianya-lemon/p/5179160.html"; Thank you so much for your ideas. Jack Shanghai -- Original -- From: "Karim ATIKI"; Date: Wed, Feb 3, 2016 04:28 PM To: "JackZhang"; Cc: "yocto"; Subject: RE: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formyrpi2 B+ board Hi Jack, I recently had a similar issue, until I realize that "curl" was not installed on my Debian Jessie... K. De : yocto-boun...@yoctoproject.org de la part de 张健 Envoyé : mercredi 3 février 2016 07:33 À : SIVA SUBRAMANIAN.P Cc : yocto Objet : Re: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formy rpi2 B+ board Hi, Sivasubramanian: Yes, I am able to reach it by using my firefox browser to reach it, It works. And that's the most werid thing. I'v asked this question on the '#yocto' IRC channel after I sent the first mail. Someone in the channel told me to use the command: " bitbake kconfig-frontends-native -c fetch" to fetch . then use "bitbake rpi-hwup-image". My computer is building now, and I'm waiting to see the results. Another possible reason is maybe the speed of the internet. I used "wifi" and the linux is run under the VMware; Now I connect the cable to
[yocto] plan-list for porting linux Re: About how port yocto to a customized MIPS cpu
Hi,everyone: For now, I have finished the yocto qurk_start document, and succeeded in building the yocto-raspberrypi image for my rpi2 B+ board. I beleive it's a good start! But after that, I still wish to figure out how to port a linux system to my fpga board with a "mips32" cpu. In the future, I will look into how to write the bsp of yocto project by refering to the poky reference distribution, the meta-raspberrypi as well as the document "yocto project BSP devellops' guide2.0" . This is my plan lists: 01. to write a yocto bsp for my device 02.learn to use qemu 03.learn to use uboo 04.learn to use archlinux for a general understanding of how a linux system runs and it's mechanisms. ... If anyone gets some ideas,pls feel free to contact with me Thank you,and best regards Jack Shanghai -- Original -- From: "Khem Raj"; Date: Thu, Jan 28, 2016 03:10 AM To: "JackZhang"; Cc: "yocto"; Subject: Re: [yocto] About how port yocto to a customized MIPS cpu On Tue, Jan 26, 2016 at 7:09 PM, 张健 wrote: But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. So this is reason why I'm here to ask you guys for some help. And wish to know if it is possible to port the "yocto" to my own project. image files are generated in several formats. There is option to generate tarballs. You can always take the tarball and untar it and look what inside secondly, for your FPGA to understand this, you probably will need tools to download the binary to memory which is visitible to FPGA if I assume FPGA is sitting along with a application processor which can then help you to flash it to relevant memory parts. if your application processor has a bootloader e.g. uboot which can use SD cards as boot media then you can use wic tool to generate SD card images directly from yocto. wic is documented in dev manual so please look there on how to set it up. Or you can look at some other BSPs like beaglebone ( angstrom ) or raspberrypi or freescale layer for scripts to generate the SD card images and model your using those. == On Tue, Jan 26, 2016 at 7:09 PM, 张健 wrote: hi,everyone: This is Jack from Shanghai, in my first year in graduate school. I'm sending email here to asking for some help about "how to port linux on a customized cpu run on FPGA board". Before I have been working on how to use "verilog" to make a cpu (based on MIPS32 ISA) on a FPGA board, and for now I could form a set of cpu code, and use assembly on it. The following is my tetris demo,which is written in assembly language and run on the MPIS32 CPU (written in verilog on FPGA board). http://www.tudou.com/programs/view/e-E5lVrQfTw/ These days, I start to think the question about how to port linux on my tiny "cpu". So I find "yocto",which seems the thing that could help me. I have finished the "yocto project quick start" document online yesterday. (http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html) and was very happy to see that it could "boot" on the qemu simulator. and I found the following are the boot image files: bzImage; bzImgage.bin; core-imgae-sato-qemux86.ext4;core-image-sato-qemux86.tar.bz2;modules-qemux86.tgz ...etc In some embedded boards, they usually write a linux image file(.img ) to a sd card. Then plug in to the board. Finally it boots. But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. So this is reason why I'm here to ask you guys for some help. And wish to know if it is possible to port the "yocto" to my own project. Thank you and Best wishes ! To geeks :) Jack-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Execute recipe only after kernel is built and rootfs file is created in deploy folder
Hi guys,
I’m trying to run a recipe that has dependencies in the generation of the
roofts and kernel image files. Without those two files already in the deploy
folder, I cannot start running my recipe.
Some suggested that I should add the task in a class and make that dependent of
do_rootfs. Then, inherit that class in a recipe. But I haven’t been successful
with that. Here’s what I have:
myclass.bbclass:
do_work() {
#main work done here
}
addtask work after do_rootfs
# end of class
myrecipe.bb:
inherit myclass
do_deploy() {
do_work
}
addtask do_deploy
# end of recipe
This must be very wrong, as the do_deploy task of my recipe is being executed
before do_rootfs happens, so it fails because do_work needs files that haven’t
been created in the deploy folder yet.
How can I fix this? Do I really need a class and recipe, or can I get away with
just having one or the other?
Thanks,
Josias--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Execute recipe only after kernel is built and rootfs file is created in deploy folder
> On Feb 4, 2016, at 10:07 PM, Josias Inacio da Silva Filho
> wrote:
>
> Hi guys,
>
> I’m trying to run a recipe that has dependencies in the generation of the
> roofts and kernel image files. Without those two files already in the deploy
> folder, I cannot start running my recipe.
>
> Some suggested that I should add the task in a class and make that dependent
> of do_rootfs. Then, inherit that class in a recipe. But I haven’t been
> successful with that. Here’s what I have:
>
> myclass.bbclass:
>
> do_work() {
> #main work done here
> }
> addtask work after do_rootfs
>
> # end of class
>
> myrecipe.bb:
>
> inherit myclass
>
> do_deploy() {
> do_work
> }
> addtask do_deploy
>
> # end of recipe
>
>
> This must be very wrong, as the do_deploy task of my recipe is being executed
> before do_rootfs happens, so it fails because do_work needs files that
> haven’t been created in the deploy folder yet.
>
> How can I fix this? Do I really need a class and recipe, or can I get away
> with just having one or the other?
actually its better for you to latch onto image recipe via additional task
defined in bbappend
something like below
addtask mytask after do_rootfs before do_build
do_mytask[depends] += "${PN}:do_rootfs"
do_mytask[depends] += "virtual/kernel:do_deploy"
# We want to build updater everytime we build image
do_mytask[nostamp] = “1"
do_mytask() {
}
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
