Re: [yocto] Errors with update-rc.d: /etc/init.d/XXX exists during rc.d purge (use -f to force)
Hi everybody again,
is there any update on this?
I'm facing the same issue with the 1.5.2 release.
I don't want to add that -f in meta/classes/update-rc.d.bbclass if there is a
better solution. (And I'm quite sure there must be a better one ;-) )
Maybe overriding the postrm function in my own meta-layer with some kind of
bbclassappend?
regards,
Richard
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On
Behalf Of Richard Leitner - SKIDATA
Sent: Thursday, November 28, 2013 3:02 PM
To: Stath, Paul
Cc: Yocto Project Discussion ML (yocto@yoctoproject.org)
Subject: Re: [yocto] Errors with update-rc.d: /etc/init.d/XXX exists during
rc.d purge
(use -f to force)
Hi Paul,
thank you for that hint and description of your workaround!
Looks like you've invested a little bit more time into working around this
issue than me
:-)
I've added -f to the update-rc.d.bbclass and now it's working like a charm:
diff --git a/meta/classes/update-rc.d.bbclass
b/meta/classes/update-rc.d.bbclass
index d8cc342..dbb5781 100644
--- a/meta/classes/update-rc.d.bbclass
+++ b/meta/classes/update-rc.d.bbclass
@@ -33,7 +33,7 @@ updatercd_postrm() {
if test $D != ; then
OPT=-f -r $D
else
- OPT=
+ OPT=-f
fi
if type update-rc.d /dev/null 2/dev/null; then
update-rc.d $OPT ${INITSCRIPT_NAME} remove
Nonetheless, I think there have to be a cleaner way to solve this issue
than forcing
the update-rc.d.
Maybe someone else has an idea how to solve this problem?
regards,
Richard
-Original Message-
From: Stath, Paul [mailto:pst...@axxcelera.com]
Sent: Wednesday, November 27, 2013 5:40 PM
To: Richard Leitner - SKIDATA
Cc: Yocto Project Discussion ML (yocto@yoctoproject.org)
Subject: RE: Errors with update-rc.d: /etc/init.d/XXX exists during
rc.d purge (use -f to
force)
Richard --
My workaround was a little less drastic than yours. (grin)
Before upgrading to the new package via 'dpkg -i', I would edit the
postrm script in /var/lib/dpkg/info/pkg-name,postrm, adding the -f
argument to force the symlink removal, as suggested by the error message.
Then the upgrade install works correctly. (With only a warning from
the postrm script of the previous package.)
I believe that the issue is that when installing a package over an
earlier release, dpkg performs the following steps:
1) Extract control files of new package
2) Execute prerm script of previous package if applicable.
3) Execute preinst script of new package.
4) Unpack new files and backup old files.
5) Execute postrm script of previous package if applicable.
6) Configure the package
When installing a newer version of the package, the postrm in step 5
fails, because the initscript from the new package is extracted in step 4,
and update-
rc.d w/o the -f
argument exits with a non-zero return code.
I would argue that the updatercd_postrm() stanza in the
update-rc.d.bbclass should include the -f flag.
(Anyone on the list want to chime in on this?)
In the meantime, I have added my own updatercd_postrm() stanza in
the .bbappend file for the package I'm having issues with, which
overrides the one provided by update-rc.d.bbclass.
updatercd_postrm() {
update-rc.d $D -f ${INITSCRIPT_NAME} remove }
--
Paul Stath
Axxcelera Broadband Wireless
From: Richard Leitner - SKIDATA [richard.leit...@skidata.com]
Sent: Wednesday, November 27, 2013 11:02 AM
To: Stath, Paul
Cc: Yocto Project Discussion ML (yocto@yoctoproject.org)
Subject: RE: Errors with update-rc.d: /etc/init.d/XXX exists during
rc.d purge (use -f to force)
Hi Paul,
good to hear I'm not the only one suffering from this issue...
No, I've received no response on the mailing list yet, but maybe
someone has a hint
for us now?
The only workaround I found is to purge the package and afterwards
install the
new version.
I know this is a really dirty workaround, but it's the only solution I
found.
Have you discovered any other workarounds, Paul?
regards
Richard
-Original Message-
From: Stath, Paul [mailto:pst...@axxcelera.com]
Sent: Wednesday, November 27, 2013 4:49 PM
To: Richard Leitner - SKIDATA
Subject: RE: Errors with update-rc.d: /etc/init.d/XXX exists during
rc.d purge (use -f to force)
Richard --
I am also getting the update-rc.d: /etc/init.d/XXX exists during
rc.d purge error
when I attempt to install a newer version of one of my packages.
It doesn't look like you received any response to your post to the yocto
mailing
list.
Did you get any response, or did you discover a workaround?
--
Paul Stath
Axxcelera Broadband Wireless
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
[yocto] Rasperry Pi bcm2835-bootfiles-20140221-r3 do_fetch
Hello, The following do_fetch of bcm28353-bootfiles-20140221-r3 is taking considerable amount of time. I have kept system monitor applcation on on my ubuntu workstation which shows download at about 114KBps. I want to know if this do_fetch task is interrupted and bitbake is stopped as I have to close down my office, will bitbaking the next time i start the process continue download from where I stopped or will start fetching for the package from 0 again. Also can it be downloaded separately, if yes where can I find the link to it and where do i have to store it once its downloaded. Kashyap -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] building armhf deb with Yocto Daisy
Dear All, I am currently trying to build armhf debs using Yocto. I use the machine tune = cortexa9hf-neon for an iMX6 Dual Lite Dev board. All the debs built in the build/tmp/deploy/deb/ folder are XYZ_armel.deb How do i build XYZ_armhf.deb using Yocto ? Any suggestions or pointer will be helpful. Thanks Regards -- *Anup Kini*Systems Engineer *--* *Synapticon* | Cyber-Physical System Solutions -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] building armhf deb with Yocto Daisy
On Fri, Jun 13, 2014 at 10:13:54AM +0200, Anup Kini wrote: Dear All, I am currently trying to build armhf debs using Yocto. I use the machine tune = cortexa9hf-neon for an iMX6 Dual Lite Dev board. All the debs built in the build/tmp/deploy/deb/ folder are XYZ_armel.deb How do i build XYZ_armhf.deb using Yocto ? For my the Beagleboard xM I enabled hard float ABI by setting DEFAULTTUNE in my local.conf: DEFAULTTUNE = cortexa8hf-neon You could give that a try with the appropriate value. I assume it will work in a machine conf file as well as in local.conf. Thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk pgpTIERHcVThJ.pgp Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Daisy 1.6.1 Build Complete (artifacts available)
Hi Saul, Usually they are displayed on any build from that triggered one, e.g. if you scroll down here you can see the commits used: https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/1 39 Regards, -- Alexandru Georgescu Yocto QA Engineer SSG/SSD Open Source Technology Center Romania On 13/06/14 02:37, Saul Wold s...@linux.intel.com wrote: Guys, http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.1/ poky: a43dba8c2904f9c1ce0425c53c5a7f4718121e6b oecore: d28b21e01fbc4b780d14495894c4253d422cd9d9 I don't have Beth's scripts to generate the complete list. -- Sau! Saul Wold Yocto Component Wrangler @ Intel Yocto Project / Poky Build System -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to determine which tasks bitbake just ran?
On Thursday 12 June 2014 15:52:10 Patrick Doyle wrote: Thanks. bitbake foo | cat is most likely to be what I was looking for. I found the cooker log shortly after I asked my question. I'll go look through bitbake and see what it would take to create a symbolic link to the most recent logfile, as is done with the logfiles for the individual tasks. I'd really like to see this symlink added too FWIW, so +1 :) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] building armhf deb with Yocto Daisy
Hi Paul, I did try that, but still the packages built are all armel.deb I am trying to build armhf.deb packages. I also checked in the package_deb.bbclass, where for arm, its defaulted to armel. I am not sure if this will effect the build and packaging process also. I have a linaro armhf image and trying to add custom binaries to it by building it from Yocto. Looking forward for some suggestions. On 13 June 2014 10:22, Paul Barker p...@paulbarker.me.uk wrote: On Fri, Jun 13, 2014 at 10:13:54AM +0200, Anup Kini wrote: Dear All, I am currently trying to build armhf debs using Yocto. I use the machine tune = cortexa9hf-neon for an iMX6 Dual Lite Dev board. All the debs built in the build/tmp/deploy/deb/ folder are XYZ_armel.deb How do i build XYZ_armhf.deb using Yocto ? For my the Beagleboard xM I enabled hard float ABI by setting DEFAULTTUNE in my local.conf: DEFAULTTUNE = cortexa8hf-neon You could give that a try with the appropriate value. I assume it will work in a machine conf file as well as in local.conf. Thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk -- *Anup Kini*Systems Engineer *--* *Synapticon* | Cyber-Physical System Solutions Mobile: Direct: +49 151 / 638 646 73 +49 7335 / 186 999 21 Fax: +49 7335 / 186 999 1 synapticon.com http://www.synapticon.com/ | @synapticon_co https://twitter.com/#!/synapticon_co Synapticon GmbH | Hohlbachweg 2 | 73344 Gruibingen, DE Secretary +49 7335 / 186 999 0 | General Manager: Nikolai Ensslen Registry Court Ulm HRB 725114 | USt-ID DE271647127 This message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Please notify the sender immediately if you have received this e-mail by mistake and delete it from your system. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to specify a default value for a variable in a recipe
OK, I've got to ask this, because it totally confuses me. I wrote a
recipe to build a custom application (gstreamer plugin, actually) that
I wanted to fetch from our SCM. Bitbake told me I needed to specify a
source revision and even gave me a clue of what to put in. Looking at
the development manual, I decided I wanted to use the latest revision
from our repository by default, so I added the following line to my
recipe:
SRCREV_default_pn-gstxbac = ${AUTOREV}
But now I'm curious. Why couldn't I use (I haven't tried this yet)
SRCREV_pn-gstxbac ?= ${AUTOREV}
and even more confusingly, why isn't the syntax something more like:
SRCREV_pn-gstxbac_default = ${AUTOREV}
What's going on here?
Does one syntax (BLAH_default vs BLAH ?=) get evaluated early in the
bitbake process and the other get evaluated late?
Does the location of the letters default in a variable name matter?
At some point, I really need to wrap my head around Bitbake, it's
syntax, and how it operates and internalize all of that.
--wpd
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] using ADT with hard float?
L.S., Can I use the ADT tools to compile for ARM using hardware floating point? /usr/arm-linux-gnueabihf/lib/sf is linked to /usr/arm-linux-gnueabi/lib regards, Ruud Ruud den Bekker Cordis Automation B.V. High Tech Campus 9 5656 AE Eindhoven -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to specify a default value for a variable in a recipe
On 2014-06-13 07:08, Patrick Doyle wrote:
OK, I've got to ask this, because it totally confuses me. I wrote a
recipe to build a custom application (gstreamer plugin, actually) that
I wanted to fetch from our SCM. Bitbake told me I needed to specify a
source revision and even gave me a clue of what to put in. Looking at
the development manual, I decided I wanted to use the latest revision
from our repository by default, so I added the following line to my
recipe:
SRCREV_default_pn-gstxbac = ${AUTOREV}
But now I'm curious. Why couldn't I use (I haven't tried this yet)
SRCREV_pn-gstxbac ?= ${AUTOREV}
If this is in the gstxbac recipe itself, use the much simpler
SRCREV ?= ${AUTOREV}
and even more confusingly, why isn't the syntax something more like:
SRCREV_pn-gstxbac_default = ${AUTOREV}
What's going on here?
Does one syntax (BLAH_default vs BLAH ?=) get evaluated early in the
bitbake process and the other get evaluated late?
Does the location of the letters default in a variable name matter?
At some point, I really need to wrap my head around Bitbake, it's
syntax, and how it operates and internalize all of that.
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to specify a default value for a variable in a recipe
On Fri, Jun 13, 2014 at 9:47 AM, Gary Thomas g...@mlbassoc.com wrote:
If this is in the gstxbac recipe itself, use the much simpler
SRCREV ?= ${AUTOREV}
Even better! While I like that solution best of all, that opens up a
whole new world of hurt for me.
How does
SRCREV_default_pn-gstxbac = ${AUTOREV}
work? When would I use that over the much simpler solution you proposed?
I am thinking that if I used your solution, I might place
SRCREV_pn-gstxbac = 123 (or a git hash, or whatever)
in my local.conf? in my BSP layer.conf?
I guess I could put
SRCREV_default_pn-gstxbac = 123 in my BSP layer.conf, and then,
later on, on some other project that used the same board, I might put
SRCREV_pn-gstxbac = ${AUTOREV} in my local.conf, or maybe in a
.bbappend file for my BSP?
How/where does the _pn suffix (middlex?) come into play?
At this point, I like your solution tremendously, as it makes sense to
me. But I sure would like to understand more about all the myriad
capabilities offered by bitbake.
--wpd
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding files to the hddimg
Hello, I'm relatively new to yocto and this is maybe something that is pretty basic but how can I add my own files in the bootimg (.hddimg) using a custom recipes? And I really means the boot image file, not the rootfs image. Thanks, François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to specify a default value for a variable in a recipe
On 2014-06-13 08:07, Patrick Doyle wrote:
On Fri, Jun 13, 2014 at 9:47 AM, Gary Thomas g...@mlbassoc.com wrote:
If this is in the gstxbac recipe itself, use the much simpler
SRCREV ?= ${AUTOREV}
Even better! While I like that solution best of all, that opens up a
whole new world of hurt for me.
How does
SRCREV_default_pn-gstxbac = ${AUTOREV}
work? When would I use that over the much simpler solution you proposed?
I am thinking that if I used your solution, I might place
SRCREV_pn-gstxbac = 123 (or a git hash, or whatever)
in my local.conf? in my BSP layer.conf?
I guess I could put
SRCREV_default_pn-gstxbac = 123 in my BSP layer.conf, and then,
later on, on some other project that used the same board, I might put
SRCREV_pn-gstxbac = ${AUTOREV} in my local.conf, or maybe in a
.bbappend file for my BSP?
How/where does the _pn suffix (middlex?) come into play?
Any time you need to set the variable outside of the recipe itself (.bb* or
.inc),
then you need the _pn-${recipe} syntax.
At this point, I like your solution tremendously, as it makes sense to
me. But I sure would like to understand more about all the myriad
capabilities offered by bitbake.
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to specify a default value for a variable in a recipe
On Fri, Jun 13, 2014 at 10:13 AM, Gary Thomas g...@mlbassoc.com wrote:
Any time you need to set the variable outside of the recipe itself (.bb* or
.inc),
then you need the _pn-${recipe} syntax.
Ahhh…. that's good to know.
I keep wanting to understand the scope rules of bitbake. This helps.
Thanks Gary.
--wpd
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] PROVIDES now always working (populate_sdk)?
Hi, I use external toolchain and 'm trying to do populate_sdk. I get a strage output. First bitbake tells me, that: DEBUG: providers for eglibc are: ['eglibc'] DEBUG: sorted runtime providers for eglibc are: ['/home/marek/yocto/poky/meta/recipes-core/eglibc/eglibc_2.19.bb'] (it is not the only one) Then it says: ERROR: Multiple .bb files are due to be built which each provide eglibc (/home/marek/yocto/poky/meta-marek-toolchain/recipes-devtools/external-marek-toolchain/external-marek-toolchain.bb /home/marek/yocto/poky/meta/recipes-core/eglibc/eglibc_2.19.bb). Of course external-marek-toolchain.bb provides eglibc (and is set as preffered provider). What can be the cause? BR, Marek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] put symlink into /usr in sysroot
I've found the solution. I created a function (fun) and added it to the
functions called during populate_sysroot:
SYSROOT_PREPROCESS_FUNCS += fun
The function fun does the work: ln -s lib ${SYSROOT_DESTDIR}usr/lib64
BR,
Marek
On 11.06.2014 13:33, ext Marek Andrus wrote:
Hi,
I have to make symbolic link /usr/lib64 to /usr/lib in target sysroot.
I create it in install phase and it appears in output rpm package.
Unfortunately it doesn't appear in sysroot. I've found that if I
create links/files inside eg. /usr/lib the same way, they appear in
sysroot. So probably the question should be like this: how to put
anything into /usr or / in sysroot?
BR,
Marek Andrus
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Custom image for EMB-3500
Hi, This is Rohit, I am trying to get yocto wokring on a ARM Board (EMB-3500 iMX6). The board doesn't support booting from Memory card. So we use the mfgtools to flash the image to on board Nand. We have Ubuntu Image which works with no issue. The Ubuntu Image has 3 files, 1. rootfs.tar.bz2 2. u-boot.bin 3. uImage I have build a Yocto iMX6qSabreauto core-image-full-cmdline image, copied the core-image-full-cmdline-imx6qsabreauto.tar.bz2 and uImage-imx6qsabreauto.bin in place of rootfs.tar.bz2 and uImage Tried to flash the image to Nand, it fails to boot. I get following error, MMC read: dev # 3, block # 2048, count 8192 ... 8192 blocks read: OK ## Booting kernel from Legacy Image at 1080 ... Image Name: Linux-3.10.17-1.0.0_ga+g232293e Image Type: ARM Linux Kernel Image (uncompressed) Data Size:5264120 Bytes = 5 MB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! I have tried to use the working kernel (Ubuntu - uImage). The kernel loads, but the board turns off automatically. I get following message before it turn off, EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p1): using internal journal EXT3-fs (mmcblk0p1): recovery complete EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:1. Freeing init memory: 212K Any help in fixing this issue is really appreciated. Thanks, Rohit -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [oe] [meta-oracle-java][PATCH] Version update and Java for ARM
Updated oracle jre and jdk recipes to the latest update 60.
Also added recipe for ejre to support ARM.
Signed-off-by: Pavel Shumeika
pavel_shume...@epam.commailto:pavel_shume...@epam.com
---
.../oracle-java/oracle-jse-ejre-arm_1.7.0.bb | 8 +
recipes-devtools/oracle-java/oracle-jse-ejre.inc | 40 ++
.../oracle-java/oracle-jse-jdk-i586_1.7.0.bb | 10 +++---
.../oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +++---
recipes-devtools/oracle-java/oracle-jse-jdk.inc| 8 +
.../oracle-java/oracle-jse-jre-i586_1.7.0.bb | 10 +++---
.../oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +++---
recipes-devtools/oracle-java/oracle-jse.inc| 4 +--
8 files changed, 78 insertions(+), 22 deletions(-)
create mode 100644 recipes-devtools/oracle-java/oracle-jse-ejre-arm_1.7.0.bb
create mode 100644 recipes-devtools/oracle-java/oracle-jse-ejre.inc
diff --git a/recipes-devtools/oracle-java/oracle-jse-ejre-arm_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-ejre-arm_1.7.0.bb
new file mode 100644
index 000..9b55173
--- /dev/null
+++ b/recipes-devtools/oracle-java/oracle-jse-ejre-arm_1.7.0.bb
@@ -0,0 +1,8 @@
+PV_UPDATE = 60
+
+require oracle-jse-ejre.inc
+
+SRC_URI =
http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz;http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz
+
+SRC_URI[md5sum] = b9b8f598b0a7f49e4d221f16ba25c6c0
+SRC_URI[sha256sum] =
ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf
diff --git a/recipes-devtools/oracle-java/oracle-jse-ejre.inc
b/recipes-devtools/oracle-java/oracle-jse-ejre.inc
new file mode 100644
index 000..1731055
--- /dev/null
+++ b/recipes-devtools/oracle-java/oracle-jse-ejre.inc
@@ -0,0 +1,40 @@
+SUMMARY = Oracle Java SE runtime environment binaries
+DESCRIPTION = This is the proprietary JRE from Sun/Oracle, with the Hotspot
JVM. It is\
+ provided by Sun/Oracle only in binary format.\
+ Java Platform, Standard Edition (Java SE) lets you develop and deploy Java\
+ applications on desktops and servers, as well as in today's demanding\
+ embedded environments. Java offers the rich user interface, performance,\
+ versatility, portability, and security that today's applications require.\
+ The JRE (Java Runtime Environment) is needed on a system to run Java\
+ applications and applets
+
+JDK_JRE = ejre
+
+LICENSE_FLAGS = oracle_java
+LICENSE = Oracle_Binary_Code_License_Agreement
+LIC_FILES_CHKSUM = \
+
file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/COPYRIGHT;md5=be9fe5d47a7dcfb78f142f487afb34bb
\
+
file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=f3a388961d24b8b72d412a079a878cdb
\
+
+
+# get the java update version in the resulting package
+PR =. u${PV_UPDATE}
+S = ${WORKDIR}
+
+do_install () {
+ install -d -m 0755
${D}/usr/${JDK_JRE}${PV}_${PV_UPDATE}
+ cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE}${D}/usr/
+ ln -sf ${JDK_JRE}${PV}_${PV_UPDATE} ${D}/usr/java
+}
+
+# All the files are provided in a binaray package, and keeping all the
+# files in a single package causes packaging QA errors and warnings.
+# Avoid these packaging failure by skiping all the QA checks
+INSANE_SKIP_${PN} = ${ERROR_QA} ${WARN_QA}
+
+# Inhibit warnings about files being stripped, we can't do anything about it.
+INHIBIT_PACKAGE_DEBUG_SPLIT = 1
+
+FILES_${PN} = /usr/
+
+RPROVIDES_${PN} += java2-runtime
\ No newline at end of file
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
index 978fbd5..dae68dc 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PR = r1
+PV_UPDATE = 60
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u60-b19/jdk-7u60-linux-i586.tar.gz;http://download.oracle.com/otn-pub/java/jdk/7u60-b19/jdk-7u60-linux-i586.tar.gz
-SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
-SRC_URI[sha256sum] =
dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
+SRC_URI[md5sum] = b33c914b03e46c3e7c33e4bdddbec4bd
+SRC_URI[sha256sum] =
d736fb4fd7c8ef50b76411daa640c6feeb48a5c275d29a90ffeb916a78d47a48
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
index 7979401..3e9ed4f 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
[yocto] Installing a new software
Hi, I am a newbee to yocto and I have a query. what is the process to add a new software to the image which is up and running. Should I add that package to recipe and build the image again and deploy it or is there any other simple way to do that?? -- Thanks Regards, Bharath Chandra Elluru. Contact Number:785-979-4875. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] virtual/mesa, virtual/libgl provided by multiple packages
On 28/05/2014 21:31, Khem Raj wrote: On Tue, May 27, 2014 at 3:44 PM, Chris Morgan chmor...@gmail.com wrote: Building a custom image with wayland and weston based on core-image, seeing issues with virtual/mesa and virtual/libgl being provided by multiple packages. Not sure if I'm doing something wrong here, like not specifying packages that provide those virtual targets? you got to set PREFERRED_PROVIDERS for jpeg and virtual/libgl to be either mesa or mesa-gl Did you find a solution to this Chris? I'm seeing the same thing with a meta-raspberrypi build of core-image-weston. The preferred provider seems set correctly by the RPi layer though (rpi-default-providers.inc) PREFERRED_PROVIDER_virtual/libgl ?= mesa-gl Thanks, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] virtual/mesa, virtual/libgl provided by multiple packages
On Fri, Jun 13, 2014 at 3:45 PM, Alex J Lennon ajlen...@dynamicdevices.co.uk wrote: On 28/05/2014 21:31, Khem Raj wrote: On Tue, May 27, 2014 at 3:44 PM, Chris Morgan chmor...@gmail.com wrote: Building a custom image with wayland and weston based on core-image, seeing issues with virtual/mesa and virtual/libgl being provided by multiple packages. Not sure if I'm doing something wrong here, like not specifying packages that provide those virtual targets? you got to set PREFERRED_PROVIDERS for jpeg and virtual/libgl to be either mesa or mesa-gl Did you find a solution to this Chris? I'm seeing the same thing with a meta-raspberrypi build of core-image-weston. The preferred provider seems set correctly by the RPi layer though (rpi-default-providers.inc) PREFERRED_PROVIDER_virtual/libgl ?= mesa-gl Thanks, Alex Hi Alex. I haven't actually gotten back to this but I (or someone else I work with) is going to be getting back to it in the next few weeks as we try to get accelerated graphics on the bbb. Chris -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How do I create a recipe for laying down post-build config files?
Well, now that I've resolved my spelling error, the build succeeds, but my
pkg_postinst_${PN} () function doesn't seem to run.
I suppose I'm resigned to making .bbappend recipes to lay down my revised
version of the config files.
at least they can all be localized in a layer. Sometimes you just have to bite
the bullet and do things
the right way.
However, I don't know how to go about removing files and links after the build
is done, and running transformative scripts on other files. For example, see
the following code examples that I want to
replicate.
#Remove unneeded services from startup
echo Remove unneeded services from startup
rm ${D}/etc/rc5.d/S20nfsserver
rm ${D}/etc/rc5.d/S20syslog
rm ${D}/etc/rc5.d/S70lighttpd
#Remove /var/log link to /var/volatile/log, persist log.
rm ${D}/var/log
mkdir ${D}/var/log
mv ${D}/etc/default/volatiles/00_core
${D}/etc/default/volatiles/00_core.orig
grep -v volatile/log ${D}/etc/default/volatiles/00_core.orig | tee
${D}/etc/default/volatiles/00_core /dev/null
rm ${D}/etc/default/volatiles/00_core.orig
Any ideas how to do this?
-Jim-
From: Jim Rafert
Sent: Monday, June 09, 2014 3:44 PM
To: yocto@yoctoproject.org
Subject: How do I create a recipe for laying down post-build config files?
I'm trying to gather all my post-build tweaks into a recipe that will be built
as part of an upper-level layer, so that they are installed after the meta
layer is processed. Many of these could be accomplished as part of .bbappend
files for the recipes that originally supply the config files, but I wanted to
gather all my customizations in one spot, so that they're easy to find.
The recipe doesn't actually build anything, so there's no do_build task.
This is surely something that is commonly wanted.
Here's my current recipe, in spectra-postbuild_0.1.bb.
When I try to build an image, the build fails with
ERROR: QA Issue: spectra-postbuild: Files/directories were installed but not
shipped
/RELEASE-NOTES.txt
When I disable the installed-vs-shipped QA test, it fails later when it can't
find a package file.
I must be missing something critical here?
SUMMARY = Post processing of configuration files for SpectraOS
SECTION = base
LICENSE = GPLv2
LIC_FILES_CHKSUM =
file://${WORKDIR}/COPYRIGHT;md5=349c872e0066155e1818b786938876a4
RDEPENDS_${PN} = initscripts
PR = r0
SRC_URI = file://inittab \
file://fstab \
file://rsyslog.conf \
file://grub.cfg \
file://mount.sh \
file://RELEASE-NOTES.txt \
file://Spectra-OS-Version \
file://initializeCustomKernelModules \
file://firewall \
file://sysctl.conf \
file://COPYRIGHT \
CONFFILES_${PN} += ${sysconfdir}/init.d/firewall
CONFFILES_${PN} += ${sysconfdir}/init.d/initializeCustomKernelModules
FILES_${PN} = /RELEASE_NOTES.txt /Spectra-OS-Version
#INSANE_SKIP_${PN} = installed-vs-shipped
do_install () {
install -m 755 ${WORKDIR}/RELEASE-NOTES.txt ${D}
install -m 755 ${WORKDIR}/Spectra-OS-Version ${D}
}
pkg_postinst_${PN} () {
install -d ${D}${sysconfdir}/init.d
install -d ${D}${sbindir}
#Install our inittab and fstab
echo Install our inittab and fstab
install -m 544 ${WORKDIR}/inittab ${D}/etc/inittab
install -m 755 ${WORKDIR}/fstab ${D}/etc/fstab
install -m 755 ${WORKDIR}/rsyslog.conf ${D}/etc/rsyslog.conf
mkdir -p ${D}/boot/grub
install -m 755 ${WORKDIR}/grub.cfg ${D}/boot/grub/grub.cfg
install -d ${D}/etc/udev/scripts
install -m 755 ${WORKDIR}/mount.sh ${D}/etc/udev/scripts/mount.sh
chmod 755 ${D}/etc/udev/scripts/mount.sh
install -m 755 ${WORKDIR}/RELEASE-NOTES.txt ${D}
install -m 755 ${WORKDIR}/Spectra-OS-Version ${D}
#Remove unneeded services from startup
echo Remove unneeded services from startup
rm ${D}/etc/rc5.d/S20nfsserver
rm ${D}/etc/rc5.d/S20syslog
rm ${D}/etc/rc5.d/S70lighttpd
#Add /dev/sdd to the auto mount blacklist
chmod 777 ${D}/etc/udev/mount.blacklist
echo /dev/sda* ${D}/etc/udev/mount.blacklist
echo /dev/sdd* ${D}/etc/udev/mount.blacklist
echo /dev/sde* ${D}/etc/udev/mount.blacklist
chmod 644 ${D}/etc/udev/mount.blacklist
#Remove /var/log link to /var/volatile/log, persist log.
rm ${D}/var/log
mkdir ${D}/var/log
mv ${D}/etc/default/volatiles/00_core
${D}/etc/default/volatiles/00_core.orig
grep -v volatile/log ${D}/etc/default/volatiles/00_core.orig | tee
${D}/etc/default/volatiles/00_core /dev/null
rm ${D}/etc/default/volatiles/00_core.orig
#Create directory for SCST
mkdir -p ${D}/var/lib/scst/pr
mkdir -p ${D}/usr/local/bin
mkdir -p ${D}/etc/logrotate.d
#Install drivers load script
echo Install drivers load script
install -m 755 ${WORKDIR}initializeCustomKernelModules ${D}/etc/init.d
ln -s ${D}/etc/init.d/initializeCustomKernelModules
Re: [yocto] [OE-core] OEDAM: OpenEmbedded Developers (Americas) Meeting
On Mon, May 19, 2014 at 5:57 PM, Stephen Arnold stephen.arnol...@gmail.com wrote: And a special thanks to everyone for letting the Gentoo dev crash the meeting. The meeting *was* fun and educational (especially for me). So far both the community and technology have been a lot of fun getting custom builds for various machines, as well as educational (is there an echo in here? ;) We were glad to have you there, Steve. Thanks for coming! Thanks again, Steve (aka mr_science) On Mon, May 12, 2014 at 4:19 PM, Jeff Osier-Mixon je...@jefro.net wrote: Meeting notes have been published on the OEDAM page: http://openembedded.org/wiki/OEDAM#Minutes Jefro takes the blame for typos and other reporting errors. On Wed, May 7, 2014 at 4:18 PM, Denys Dmytriyenko de...@denix.org wrote: The OpenEmbedded Board of Directors would like to thank everyone who was able to participate (either in person in Santa Clara or online) in our first OEDAM OpenEmbedded Developers (Americas) Meeting on May 2nd and 3rd! The meeting was a huge success and a lot of fun! We would also like to thank Ettus Research/NI for providing the premises, as well as Jefro and the Yocto Project for sponsoring the event and providing food! The meeting minutes should be published shortly. -- Denys On Thu, Feb 20, 2014 at 07:03:24PM -0500, Philip Balister wrote: The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is immediately after the Embedded Linux Conference North America. All active OpenEmbedded and Yocto Project developers are invited to attend. NOTE: this is a development meeting for the project itself, not a training session. May 2-3, 2014 time TBD Ettus Research/National Instruments 4600 Patrick Henry Drive Santa Clara, CA 95054 USA Lunch will be provided on both days. For more information and to add yourself to the list of attendees, see the wiki page at http://openembedded.org/wiki/OEDAM Here are a couple of photos from 2009: http://www.flickr.com/photos/32615155@N00/sets/72157622653686647/ I'd like to thank Jefro for help with this announcement. Any errors are mine though. Philip, OpenEmbedded eV Chair. ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Jeff Osier-Mixon @Intel Yocto Project Community Manager http://yoctoproject.org -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Jeff Osier-Mixon @Intel Yocto Project Community Manager http://yoctoproject.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
