Re: [yocto] Another in a seemingly infinite chain of errors
From: Zhenhua-B19537
FILES_${PN}_append = xxx should useful, xxx is the file
which is listed in the were installed but not shipped message.
More info of FILES can be found in
https://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.ht
ml#var-FILES
Thanks for the quick response.
The problem is that every directory that I create in this one recipe is in
that list, not just the files. This includes things like
/lib/systemd/system.
I have another recipe, which is basically the same as the hello.c example,
except that it is a real program. It works fine without a FILES_${PN}
variable. So what is it about my failing recipe that makes it need a
FILES_${PN} variable? It has no do_compile, just a do_install script with a
bunch of install and ln commands.
By the way, I also notice it says to use things like ${bindir} for standard
directories. Is there a comprehensive list of these anywhere? I don't find
them in the Yocto Dev Manual or Ref Manual.
--
Ciao, Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build status
Hi Michael, The adt-installer is missing from the http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ build. But since it is using the same commit for as http://autobuilder.yoctoproject.org/pub/nightly/20130703-2 build, we will use the one there instead for testing. Regards, -- Alexandru Georgescu From: Michael Halstead [mailto:mhalst...@linuxfoundation.org] On Behalf Of Michael Halstead Sent: Thursday, July 04, 2013 03:36 To: yocto@yoctoproject.org Subject: Re: Yocto Project 1.5_M2.rc1 build status Adidtional autobuilder configuration errors were corrected and a third spin of 1.5_M2.rc1 started. Please find the build at the new location: http://autobuilder.yoctoproject.org/pub/nightly/20130703-3 poky eaa5df34af42b6a37f6506847d0f3ef6ba0d298ahttps://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-arm daf582c93a7283fb0af3b25fe2ada48f4c9985c4https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppc a2bcb25c53f935ae9a423c57ca5e2f7a2f7b1a69 (Changed since last build) meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-poky e35dfd79e3970f88a8273125890a54f75f108b97https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Another in a seemingly infinite chain of errors
-Original Message-
From: Paul D. DeRocco [mailto:pdero...@ix.netcom.com]
Sent: Friday, July 05, 2013 2:20 PM
From: Zhenhua-B19537
FILES_${PN}_append = xxx should useful, xxx is the file which is
listed in the were installed but not shipped message.
More info of FILES can be found in
https://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-
manual.ht
ml#var-FILES
Thanks for the quick response.
The problem is that every directory that I create in this one recipe is
in that list, not just the files. This includes things like
/lib/systemd/system.
[Luo Zhenhua-B19537] Seems like the similar issue as
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4309
I have another recipe, which is basically the same as the hello.c example,
except that it is a real program. It works fine without a FILES_${PN}
variable. So what is it about my failing recipe that makes it need a
FILES_${PN} variable? It has no do_compile, just a do_install script with
a bunch of install and ln commands.
[Luo Zhenhua-B19537] Generally were installed but not shipped means those
files are installed into ${D}, but not placed in any resulting package. FILES
can solve it. If the folder is empty, you can remove it directly.
By the way, I also notice it says to use things like ${bindir} for
standard directories. Is there a comprehensive list of these anywhere? I
don't find them in the Yocto Dev Manual or Ref Manual.
[Luo Zhenhua-B19537] I am not sure whether such variables are documented in a
unified doc, I always check it in meta/conf/bitbake.conf or bitbake -e | grep
xxx.
Best Regards,
Zhenhua
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ivi] [PATCHv3] connman: do not delete init scripts in bbappend
Currently connman init scripts are installed only when 'sysvinit' feature is
enabled in DISTRO_FEATURES: commit 7c8160ccbe17d6e10bd7a09b91843182a89b9055
in poky. No need to remove them in bbappend:
- they are not installed for 'systemd'-enabled systems
- they are needed for 'sysvinit'-enabled systems
Signed-off-by: Sergey Matyukevich sergey_matyukev...@mentor.com
---
recipes-connectivity/connman/connman_1.15.bbappend |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/recipes-connectivity/connman/connman_1.15.bbappend
b/recipes-connectivity/connman/connman_1.15.bbappend
index cda612b..f1deaf2 100644
--- a/recipes-connectivity/connman/connman_1.15.bbappend
+++ b/recipes-connectivity/connman/connman_1.15.bbappend
@@ -1,9 +1 @@
PRINC := ${@int(PRINC) + 2}
-
-INITSCRIPT_NAME =
-INITSCRIPT_PARAMS =
-
-do_install_append() {
- # Remove init scripts
- rm -r ${D}${sysconfdir}/init.d
-}
--
1.7.2.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Fix retrieval of System tap parameters
- the parameters for runnin crosstap are populated before the window is
actually open so they remain null
- retrieve them after the window has closed run the script
Signed-off-by: Ioana Grigoropol ioanax.grigoro...@intel.com
---
.../sdk/remotetools/actions/SystemtapHandler.java | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
index 9d27e5a..184582a 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
@@ -33,13 +33,14 @@ public class SystemtapHandler extends AbstractHandler {
shell, Systemtap
);
- String metadata_location =
((SystemtapSettingDialog)setting).getMetadataLocation();
- String remote_host =
((SystemtapSettingDialog)setting).getRemoteHost();
- String user_id = ((SystemtapSettingDialog)setting).getUserID();
- String systemtap_script =
((SystemtapSettingDialog)setting).getSystemtapScript();
- String systemtap_args =
((SystemtapSettingDialog)setting).getSystemtapArgs();
if(setting.open() == BaseSettingDialog.OK) {
+
+ String metadata_location =
((SystemtapSettingDialog)setting).getMetadataLocation();
+ String remote_host =
((SystemtapSettingDialog)setting).getRemoteHost();
+ String user_id =
((SystemtapSettingDialog)setting).getUserID();
+ String systemtap_script =
((SystemtapSettingDialog)setting).getSystemtapScript();
+ String systemtap_args =
((SystemtapSettingDialog)setting).getSystemtapArgs();
IProgressService progressService =
PlatformUI.getWorkbench().getProgressService();
SystemtapModel op = new
SystemtapModel(metadata_location,remote_host, user_id, systemtap_script,
systemtap_args,window.getShell().getDisplay());
--
1.7.9.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build status
Thank you. The final steps of http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ were blocked and never completed so there may be other things missing as well. We probably need to do another build before releasing but it will hopefully be from the same commit as well. Michael Halstead Yocto Project / Sys Admin On 07/05/2013 01:05 AM, Georgescu, Alexandru C wrote: Hi Michael, The adt-installer is missing from the http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ build. But since it is using the same commit for as http://autobuilder.yoctoproject.org/pub/nightly/20130703-2 build, we will use the one there instead for testing. Regards, *--* *Alexandru Georgescu* *From:*Michael Halstead [mailto:mhalst...@linuxfoundation.org] *On Behalf Of *Michael Halstead *Sent:* Thursday, July 04, 2013 03:36 *To:* yocto@yoctoproject.org *Subject:* Re: Yocto Project 1.5_M2.rc1 build status Adidtional autobuilder configuration errors were corrected and a third spin of 1.5_M2.rc1 started. Please find the build at the new location: http://autobuilder.yoctoproject.org/pub/nightly/20130703-3 poky eaa5df34af42b6a37f6506847d0f3ef6ba0d298a https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eaa5df34af42b6a37f6506847d0f3ef6ba0d298a meta-fsl-arm daf582c93a7283fb0af3b25fe2ada48f4c9985c4 https://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=daf582c93a7283fb0af3b25fe2ada48f4c9985c4 meta-fsl-ppc a2bcb25c53f935ae9a423c57ca5e2f7a2f7b1a69 (Changed since last build) meta-intel e0d6134ed2e2687ff9f2ee77701666447842bf33 https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=e0d6134ed2e2687ff9f2ee77701666447842bf33 meta-minnow286a72ba3f5e29432be1dd77127de5bdc2d988c3 https://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/commit/?id=286a72ba3f5e29432be1dd77127de5bdc2d988c3 meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222 https://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/commit/?id=b73552fb998fd30a01dbee5a172e432a16078222 eclipse-poky e35dfd79e3970f88a8273125890a54f75f108b97 https://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e35dfd79e3970f88a8273125890a54f75f108b97 Please begin QA as soon as possible. Thank you. smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project 1.5_M2.rc1 build status
On Friday 05 July 2013 10:02:01 Michael Halstead wrote: Thank you. The final steps of http://autobuilder.yoctoproject.org/pub/nightly/20130703-3/ were blocked and never completed so there may be other things missing as well. We probably need to do another build before releasing but it will hopefully be from the same commit as well. Feel free to stop the dylan-next build I started about an hour ago on the AB, I had a dodgy commit in there so it's mostly failed. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Another in a seemingly infinite chain of errors
From: Luo Zhenhua-B19537
[Luo Zhenhua-B19537] Seems like the similar issue as
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4309
Just adding everything to FILES_${PN} solves the problem, although it's
still a mystery to me why the helloworld.c example doesn't need to do that.
By the way, I also notice it says to use things like ${bindir} for
standard directories. Is there a comprehensive list of
these anywhere? I
don't find them in the Yocto Dev Manual or Ref Manual.
[Luo Zhenhua-B19537] I am not sure whether such variables are
documented in a unified doc, I always check it in
meta/conf/bitbake.conf or bitbake -e | grep xxx.
Thanks. I think I'll create my own little text file listing them all, along
with the default values they expand into.
If anyone involved in upgrading the docs is reading this, that really should
go into the Ref Manual, in a single table.
--
Ciao, Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Changing syslinux configuration
For my system (something similar to core-image-base running on a Cedartrail Atom mobo), the syslinux.cfg file needs to be tweaked. It is built by a script in syslinux.bbclass, which is controlled by various variables. First of all, it's important that it not try to use a serial port as a console, so that means I'm supposed to set SYSLINUX_SERIAL to . Second, it's providing two choices called boot and install, and I'd like to eliminate the latter, which involves setting the LABELS variable to boot. I see that syslinux.bbclass has default value of 0 115200, but it has no default value for LABELS, which would cause a failure if something else wasn't setting it to boot install. I see that it is inherited by boot-directdisk.bbclass, but it doesn't provide a default value for LABELS, either. Does anyone know what recipe actually sets LABELS? And then, do I override these variables by creating a .bbappend file for that recipe? Or are these two symbols global symbols that I can somehow supply values for in my layer file? I really have no understanding of the scope of all the multiplicity of variables in the Bitbake system. Does each recipe have its own namespace for variables, or is everything global? -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
