poky-linux/linux-libc-headers/4.12-r0/temp/log.do_install.4172
contents to gather more useful information to discover/fix your issue.
2018-04-17 11:50 GMT+02:00 Stéphane Ancelot :
>
>
> Le 17/04/2018 à 09:08, Iván Castell a écrit :
>
> Review "dmesg" output to see if ther
Hello forum.
We are trying to use yocto in a continuous integration environment with
different (production vs debug) scenarios.
To setup a given scenario (production vs debug) we are using something like
this:
$ SCENARIO=debug
$ MACHINE= DISTRO=-${SCENARIO} source
../../build--${SCENARIO
Thanks a lot for all your replies. I am working on a solution trying to get
the best option of all your answers. I will come back after deciding my
solution to share it with the community.
Related with that shared state cache, I found some information on a e-book
(search the text on google to fin
That sounds really convincing, I will give it a chance and come back to
describe the hole process after all. Thank you for that valuable
information Mr. Ross
2018-04-23 17:38 GMT+02:00 Burton, Ross :
> Very curious as to what book said that, because *any* example of that
> happening is a bug in t
scenarios?
Thank you in advance! :-)
2018-04-24 8:45 GMT+02:00 Iván Castell :
> That sounds really convincing, I will give it a chance and come back to
> describe the hole process after all. Thank you for that valuable
> information
Hello forum.
I have two questions related with the generation of images when the distro
is configured to use a repository of rpm packages signed with gpg.
First question: after running the "bitbake my-image.bb" command, the build
process stops with this message of error:
ERROR: myimage-1.0-r0 do
The purpose is deploying a yocto PR server using a docker container. More
info about PR server can be found in the following link:
https://wiki.yoctoproject.org/wiki/PR_Service
To try doing that I wrote this "Dockerfile" to generate a docker image:
FROM ubuntu:16.04
MAINTAINER Yocto
# Update, u
Iván Castell :
> The purpose is deploying a yocto PR server using a docker container. More
> info about PR server can be found in the following link: https://wiki.
> yoctoproject.org/wiki/PR_Service
>
> To try doing that I wrote this "Dockerfile" to generate a docker ima
Hello forum.
Using the "rocko" branch. The SSL CA certificates "ca-certificates.crt"
don't appear inside this directory:
build/tmp/work/x86_64-linux/curl-native/7.54.1-r0/recipe-sysroot-native/etc/ssl/certs/
That generates issues when trying to build images that use a https
repository of rpm pac
is that when the ca-certificates.crt is properly installed,
the build process ends fine. If that file is not properly installed, the
build process fails with the error reported in my previous message.
2018-05-08 21:15 GMT+02:00 Alexander Kanavin <
alexander.kana...@linux.intel.com>:
>
pos.d
install -m 0600 ${WORKDIR}/yocto-adv-rpm.repo
${D}/etc/yum.repos.d/yocto-adv-rpm.repo
}
FILES_${PN} += "/etc/yum.repos.d"
The contets of yocto-adv-rpm.repo are in the previous message.
2018-05-09 8:29 GMT+02:00 Iván Castell :
> But I am not fetching nor installing package
00 Alexander Kanavin <
alexander.kana...@linux.intel.com>:
> On 05/09/2018 09:29 AM, Iván Castell wrote:
>
>> But I am not fetching nor installing packages over the network during
>> image creation. I just build an image using local recipes (standard
>> procedure). One of those
o/yocto/build/tmp/deploy/rpm
After that, "repodata" directory appears in the package feed and
"repomd.xml" file is inside available, but "repomd.xml.asc" is still not
found.
Do I am missing something?
Thank you in advance!
2018-05-09 13:44 GMT+02:00 Iván Caste
Ok that's already fixed. I could manage it executing this in host machine
after building the image:
$ bitbake package-index
2018-05-10 16:01 GMT+02:00 Iván Castell :
> Once the image was build and cloned into the target device, this error
> appears when trying to update dnf da
Hello forum.
After updating all my layers to the lastest state of the "rocko" branch, I
am getting this error in "meta-oe" layer:
| In file included from ../../git/fontforge/splinefont.h:36:0,
| from ../../git/fontforge/sd.h:34,
| from ../../git/fontforge/svg.h:4
e
> workaround right now is to disable uninative. This in your local.conf
> will work:
>
> INHERIT_remove = "uninative"
>
> Ross
>
> On 11 May 2018 at 13:02, Iván Castell wrote:
> > Hello forum.
> >
> > After updating all my layers to the las
I fixed this issue defining different distro.conf files in my custom layer,
adding a custom variable DISTRO_STAGE with the name of my distro
(production, rnd, retail, and so on), Then you setup DISTRO in your
local.conf to the proper value you want to use. Finally you can use that
DISTRO_STAGE vari
f these types of images for a while now.
>
> So far have avoided diving into multiple distros because would like to
> have the option
> of building all the images at the same time (so they are basically the
> same distro).
>
> On Fri, Jun 1, 2018 at 8:13 AM, Iván Castell
>
s that you create a single image
> file per build
> (which can be any of the given types)?
> You're setup doesn't allow for building the "developent" and
> "production" image at the same time?
>
> Be Well,
> Alan
>
>
>
> On Fri, Jun 1, 20
2018-06-01 11:24 GMT+02:00 Alexander Kanavin :
> I have to say defining multiple distros and then tweaking recipes
> according to those definitions is not a good practice, as recipes should
> generally only access DISTRO_FEATURES and otherwise be distro-agnostic. The
> above iptables scenario shou
I managed this issue redefining this script in my custom layer (rocko
branch):
scripts/lib/wic/canned-wks/mkefidisk.wks
and setting a bigger size for the root partition (80GB in my case):
part / --source rootfs --ondisk sda --fstype=ext4 --label platform
--align 1024 --use-uuid --*size 8
Hello forum.
I am trying to integrate several BSP-layers for different platforms on a
single Yocto repository to build a Linux Yocto-based distro for all those
platforms easily.
The idea is maintaining a single bblayers.conf with all the layers
available, set PLATFORM and DISTRO on local.conf, ca
Hello.
Many thanks for your explanation Mr. Trevor. That makes sense to me. At
least now we know we are in the good way.
2018-06-07 18:47 GMT+02:00 Trevor Woerner :
> Hi Iván,
>
> On Thu 2018-06-07 @ 04:39:11 PM, Iván Castell wrote:
> > When setting the "build" direc
Hello.
First you need to reconfigure your kernel configuration (ncurses must be
properly installed in your host PC):
$ bitbake -c menuconfig virtual/kernel
After you need to generate a fragment.cfg (containing a diff betweeen your
default and your recently customized kernel config):
$ b
755 ${WORKDIR}/rcS.rnd ${D}${sysconfdir}/init.d/rcS
> }
>
> do_install_append_class-release () {
> install -m 755 ${WORKDIR}/rcS.release ${D}${sysconfdir}/init.d/rcS
> }
>
> BBCLASSEXTEND = "production rnd release"
>
> ==
>
> I
Hello yocto mailing list.
I'm having troubles trying to setup a Yocto image with full support to
English and Spanish languages (Spanish as default).
The testing image I am building is based on the rocko branch, and my distro
is "systemd" based.
My current distro.conf yocto setup is this:
GL
Hi forum.
I'm having ABI issues trying to compile a Go lang related project.
In order to resolve my project dependencies, I use dep tool. To be able to
dep, I had to modify meta/recipes-devtools/go/go-dep_0.3.0.bb, adding this
at the end:
BBCLASSEXTEND = "native nativesdk"
After that, this
Hello forum!
I'm trying to build a yocto image without busybox and without any busybox
applet deployed.
I have tried that configuring my distro.conf file in this way:
DISTRO_FEATURES_remove = " busybox"
VIRTUAL-RUNTIME_base-utils = ""
PREFERRED_PROVIDER_virtual/base-utils = ""
Nonet
tinylogin'
Is there some valid alternative available? Where are these alternatives
defined?
In general, is it posible to build yocto images without using busybox at
all?
2018-02-16 16:56 GMT+01:00 Iván Castell :
> Hello forum!
>
> I'm trying to build a yocto image w
2018-02-19 16:18 GMT+01:00 Maxin B. John :
> Hi,
>
> On Mon, Feb 19, 2018 at 02:17:38AM -0800, Khem Raj wrote:
> > On Mon, Feb 19, 2018 at 12:35 AM, Iván Castell
> > wrote:
> > > I have tried breaking apart packagegroup-core-boot, making a copy in my
> &g
2018-02-20 7:45 GMT+01:00 Martin Hundebøll :
> Hi Ivan,
>
>>
>> Thank you for the information, I will take into account that tool for
>> future embedded projects. However, the focus of this issue was to remove
>> completely busybox from the image, not replacing it by another application
>> box.
>>
2018-02-21 4:01 GMT+01:00 Paul Eggleton :
> On Tuesday, 20 February 2018 9:26:49 PM NZDT Iván Castell wrote:
> > 2018-02-20 7:45 GMT+01:00 Martin Hundebøll :
> > >> Thank you for the information, I will take into account that tool for
> > >> future embedded pro
Hello forum.
I have a question regarding the expansion of variables in a recipe. Suppose
I have a recipe with this "do_install" task defined:
do_install() {
BBB = ${WORKDIR}
}
Variable BBB expands to the proper working directory.
$ bitbake -e | grep BBB
BBB = /path/to/w
2018-02-21 17:17 GMT+01:00 Joshua Watt :
> On Wed, 2018-02-21 at 16:50 +0100, Iván Castell wrote:
>
> Hello forum.
>
> I have a question regarding the expansion of variables in a recipe.
> Suppose I have a recipe with this "do_install" task defined:
>
>
Hello forum.
Working with 'rocko' yocto branch. Yocto generates .ext4, .hddimg and .wic
images. I want to install the proper image to the HDD of my PC, in order to
use it as my default Linux distro.
I have been using the .wic image to boot from the USB pendrive until now,
writing it to the USB us
help to would be very helpful. Thanks in advance!!
2018-03-01 12:20 GMT+01:00 Iván Castell :
> Hello forum.
>
> Working with 'rocko' yocto branch. Yocto generates .ext4, .hddimg and .wic
> images. I want to install the proper image to the HDD of my PC, in order to
> use it as
2018-03-02 0:41 GMT+01:00 Anuj Mittal :
> Hi,
>
> On 03/01/2018 07:20 PM, Iván Castell wrote:
> >
> > Is this the proper way to install the generated image in the hard disk?
> > Maybe I am doing something wrong?
>
> Does the image boot up if you select 'boo
ipes-core/initrdscripts/initramfs-framework/init. In that init
script there are two calls to "fatal" function. Maybe this information can
be useful to discover what is happening.
I have tested adding suggested "init_fatal_sh" bootarg but I don't get any
ound
/init: line98: grep: command not found
/init: line112: sed: command not found
And after all, this error message appears:
ERROR: Initramfs failed to initialize the system
Hope all this information can be helpful to fix this issue.
Thank you in advance! :-)
2018-03-02 9:52 GMT+01:0
Hello forum.
I want to customize my rootfs partition to be mounted with the
"data=journal" option enabled.
To do that I have modified my layer adding a custom mkefidisk.wks script
with this contents for the rootfs partition:
part / --source rootfs --ondisk sda --fstype=ext4
--fsoptions="data
After some googling I fixed my issue customizing mkefidisk.wks script, adding
"rootflags=data=journal" to the line related with the bootloader:
bootloader --ptable gpt --timeout=5 --append="rootfstype=ext4
console=ttyS0,115200 console=tty0 rootflags=data=journal noapic"
Now my rootfs is mount
Hello forum.
My layer provides two custom recipes A and B with exactly the same
functionality. To get a working image, one of these two recipes must be
included on the generated image (A_installed XOR B_installed).
So I need the build process being able to check the list of installed
packages, st
> manual.html#var-RCONFLICTS
>
> Best regards,
> Vincent
>
> 2018-03-26 9:54 GMT+02:00 Iván Castell :
>
>> Hello forum.
>>
>> My layer provides two custom recipes A and B with exactly the same
>> functionality. To get a working image, one of these two recip
Hello forum.
In order to generate a distro image with support for signed rpm packages, I
generated a pair of GPG keys, and setup my custom distro.conf file so Yocto
can sign packages it generates. My distro.conf file includes this:
INHERIT += "sign_rpm"
RPM_GPG_NAME = "gpgyocto"
RPM_G
44 matches
Mail list logo
