Hello.
Well, the below line actually inheriting image-live.bbclass. The variable
values I can see by '-e' option may be the final values, not in the middle of
parsing.
>IMAGE_TYPE_live = "${@build_live(d)}"
>
>inherit ${IMAGE_TYPE_live}
The solution I came up is, to copy genericx86.conf to
Hello.
Though the build successfully completes, but the image does not boot and I
believe parameters are not set properly for my image.
What I am trying to do is to build xxx.hdddirect image instead of xxx.hddimg
for genericx86(, on fido).
As I inspect with '-e' option, I believe, at least the
On Thu, Jul 14, 2016 at 4:16 PM, Simon Bolek wrote:
> Hi Raj,
>
> About depmod again.
> Should it be run from meta/classes/kernel.bbclass ?
> ...
> pkg_postinst_kernel-base () {
> if [ ! -e "$D/lib/modules/${KERNEL_VERSION}" ]; then
> mkdir -p $D/lib/modules/${KERNEL_VERSION}
> fi
Hi Raj,
About depmod again.
Should it be run from meta/classes/kernel.bbclass ?
...
pkg_postinst_kernel-base () {
if [ ! -e "$D/lib/modules/${KERNEL_VERSION}" ]; then
mkdir -p $D/lib/modules/${KERNEL_VERSION}
fi
if [ -n "$D" ]; then
depmodwrapper -a -b $D ${KERNEL_VERS
Thank you in advance. Could really use the help.
I have to get php5 working in apache2.
yocto@yocto-H8SGL:~/poky/build$ bitbake core-image-lsb
Loading cache: 100%
|#|
ETA: 00:00:00
Loaded 237
Hi
Here is the final report for QA Test Cycle on Yocto Project 2.1.1 rc1 release :
* Bugs Summary
** High / M+
- test_rpm_query_nonroot - Failed to create new user - need to be
backported to 2.1.2 : 8988 [1]
- test_parselogs failed on udevd[342] inotify_add_watch /dev/loop: 9
Default eventlog creating to False when starting an AB build session
from the command line.
[YOCTO #9884]
Signed-off-by: Bill Randle
---
bin/remote_kick.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/bin/remote_kick.py b/bin/remote_kick.py
index 20a7b7e..7320162 100644
--- a/bin/remote_
Add a new 'create_eventlog' custom property to the configurations that
could potentially create a toaster event log. In the case of "nightly.conf",
ensure the property is passed to the Triggered builds.
[YOCTO #9884]
Signed-off-by: Bill Randle
---
buildset-config.controller/nightly-arm-lsb.conf
Now that multiple eventlog files can be generated, upload thyem all. Also,
only upload files in user requested an eventlog be generated.
[YOCTO #9884]
Signed-off-by: Bill Randle
---
.../autobuilder/buildsteps/UploadToasterEventlog.py | 16 +++-
1 file changed, 11 insertions(+),
Qualify creation of the toaster eventlog based on the setting of the new
'custom_create_eventlog' property. Place the eventlog in build/tmp/log,
instead of build and add a timestamp to the eventlog filename since
multiple event logs can be generated during a multi-image buildset and
otherwise only
Currently, a toaster eventlog is generated for most all machine specific
images (e.g., nightly-arm, nightly-x86, etc.) and placed in the top-level
build directory. Having it in the top level dir causes inotify overflow in
bitbake, due to the large number of changes to the file.
This set of patches
ELCE is in Berlin this year on Oct 11-13 (Tuesday-Thursday). After
conversations with the Yocto Project, we've worked out that there will
be a Yocto Project developer day on Monday, Oct 10 and OEDEM
(OpenEmbedded developer meeting) on Friday, Oct 14.
The Yocto Project developer day is basically a
On Wed, 2016-07-06 at 13:16 -0700, Bill Randle wrote:
> QA started testing wic images in Yocto 2.1, but was building them
> themselves. Have the autobuilder publish the wic images so they are
> available for testing.
>
Merged to master, thanks.
Joshua
> [YOCTO #9397]
>
> Bill Randle (2):
> P
On Thu, 2016-07-14 at 10:38 +0100, Joshua G Lock wrote:
On Wed, 2016-07-06 at 13:16 -0700, Bill Randle wrote:
Publish the wic images created by the nightly-wic build so they are
available for QA testing.
[YOCTO #9397]
Signed-off-by: Bill Randle
mailto:william.c.ran...@intel.com>>
---
buildse
Hello
>IMAGE_FSTYPES += "vmdk"
Thank you it worked.
(I should remember '_append' applied after all '=' assignments are done.)
After .hdddirect image is successfully created, I am still working on the
following.
i) image does not boot, maybe its boot device path thing...
ii) hddimage, iso ima
On 01/07/16 03:29, Takashi Matsuzawa wrote:
>
> Hello Yocto.
>
> Well, this may not be a very new topic, but I wonder if you have recent
> suggetions.
> So far I have tried the followings and see some improvement, making the build
> time to days to hours.
>
> 1) All of the directories, DL_DIR,
It works fine! Problem solved
Stefan Jaritz
ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de
Geschäftsführ
On 14 July 2016 at 11:22, wrote:
> I want to create a recipe for an application. This application is
> generated through cmake. In the cmake file "CMakeLists.txt" is the passage:
> ##
> include(FindPythonInterp)
> include(FindPythonLibs)
>
> add_custom_command(OUTPUT "${CMAKE_BIN
Hej
I want to create a recipe for an application. This application is
generated through cmake. In the cmake file "CMakeLists.txt" is the
passage:
##
include(FindPythonInterp)
include(FindPythonLibs)
add_custom_command(OUTPUT "${CMAKE_BINARY_DIR}/error.cpp"
"${CMAKE_BINARY_DIR}/
On Wed, 2016-07-06 at 13:16 -0700, Bill Randle wrote:
> Publish the wic images created by the nightly-wic build so they are
> available for QA testing.
>
> [YOCTO #9397]
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-wic.conf| 8 ++---
> .../autobuilder/build
You can do the following check.
1. Find out the package which produces libvolk.so.0.0.0, I think it
should be volk.
2. Check if the binary package is generated, which includes those dynamic
libraries. It is possible that those libraries are generated and not shipped in
any package.
21 matches
Mail list logo
