,
Marc
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https
+= echo ${@print_layers_version(d)} /
${IMAGE_ROOTFS}/etc/build;
Ah, nice solution!
That might be something to add to my own /etc/build. You can never get
too much info if some issues turn up...
/Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
Will the GA start at 17:00, or shouldn't we start it after the closing session
finishes?
Cheers,
Anders
Philip Balister phi...@balister.org wrote:
Non-members are welcome to come to the meeting. If you are interested in
becoming a member of the eV
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
recommend you to create your
own image. A first step might be to just copy one of the image recipes
to a layer of your own, and then modify it according to your taste.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto
Hans
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB Tel: +46 702 44 84 36
Laxholmstorget 3 Email: and...@chargestorm.se
602 21 Norrköping Web
Hans Beckérus hans.becke...@gmail.com wrote:
On Mon, Apr 22, 2013 at 9:47 AM, Anders Darander
and...@chargestorm.se wrote:
Hi,
Hans Beckérus hans.becke...@gmail.com wrote:
Hello. I wish to bring in gnupg to our system but from what I can
tell
gnupg is not part of Yocto nor OpenEmbedded
the
current versions.
Cheers,
Anders
i hope i am not annoying you. Thank You for your time and patience.
--
Anders Darander
ChargeStorm AB Tel: +46 702 44 84 36
Laxholmstorget 3 Email: and...@chargestorm.se
602 21 Norrköping Web: www.chargestorm.se
Sent from my Android phone
in question.
But neither worked.
That should make it work.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
to do using the useradd class. See
http://cgit.openembedded.org/openembedded-core/tree/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
for more info
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto
alternatives exist
for it
update-alternatives: removing //usr/bin/yes as no more alternatives
exist for it
update-alternatives: removing //bin/zcat as no more alternatives exist
for it
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing
* Paul Eggleton paul.eggle...@linux.intel.com [08 17:23]:
On Monday 07 November 2011 10:18:51 Anders Darander wrote:
We have found a problem with upgrading packages on our own image.
(Hopefully it'll show up to an error from our side).
After upgrading system packages, like busybox, we
https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Time flies fast, and the travel schedules for fall will likely need to
be set soon...
Are there any plans for a YP Dev.Day in Edinburgh, and if so, any dates
set?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
Paul Eggleton paul.eggle...@linux.intel.com wrote:
On Wednesday 18 September 2013 10:47:56 Anders Darander wrote:
* Brad Litterell b...@evidence.com [130917 21:20]:
I have a number of QT components that have qmake style .pro files.
In my recipe I inherit both externalsrc qmake2. I'm
already being installed to a package named openssh-sftp. Thus, it
should be enough to add openssh-sftp to your image.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org
-sftp there, or which packages do you have there?
Which version of Yocto / Poky are you using? What layers do you have enabled?
Cheers,
Anders
Thanks
Amit
On Tue, Oct 1, 2013 at 6:56 PM, Anders Darander and...@chargestorm.se
wrote:
* Amit Tomer amittome...@gmail.com [131001 14:57
any tests on my own until early next week. If necessary,
I hope that someone else might be able to help you until then.
Cheers,
Anders
This is taken from build confriguation.
Thanks
Amit.
On Tue, Oct 1, 2013 at 7:37 PM, Anders Darander and...@chargestorm.se
wrote:
Amit Tomer amittome
0xff7e0060
faulting instruction address: 0xf107e05c
Oops: Kernel access of bad area, sig: 11 [#1]
..
.
How can I solve this problem?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Anders
Jack jackrubby2...@gmail.com wrote:
Anders Darander anders@... writes:
Thanks Anders,
But I have this problem not only for GPIOs, but also for other
registers.
Well, my comment about dereferencing physical addresses using *-only, wasn't
restricted to GPIO's only. It was regarding physical
other questions on mdev, it's been a little while since I
used mdev. Let us know if the ideas above is enough, or if you want to
dig more into mdev.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
* Hans Beckérus hans.becke...@gmail.com [140121 13:12]:
On Tue, Jan 21, 2014 at 12:10 PM, Hans Beckérus hans.becke...@gmail.com
wrote:
On Tue, Jan 21, 2014 at 11:23 AM, Anders Darander and...@chargestorm.se
wrote:
* Hans Beckérus hans.becke...@gmail.com [140121 11:05]:
Things looked
.
The image.bb file is far to late to change the distro configuration.
The better, long term solution would be to define your own distro. Which
really isn't that hard.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing
have been handled by
inherit python3native
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
a standard bitbake recipe and just install those files into
the rootfs.
If it's something else, I think you need to explain it a little bit
more.
Cheers,
Anders
Any suggestions?
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing
http and ssh URIs.
No, the protocol is specified by adding protocol=xxx.
SRC_URI =
git://github.com/GraphicsEmpire/gridvisualization.git;branch=master”
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto
use bitbake -e recipe-name to check that EXTRA_OECONF
looks OK.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
after
each other.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
you...
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
in oe-core.
Otherwise, check out https://github.com/MentorEmbedded/meta-ro-rootfs,
which is were volatile-binds originates from.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https
install -m 0555 ${WORKDIR}/zd1211_*${D}/${libdir}/firmware/zd1211/
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
with diff
section on http://jungels.net/articles/diff-patch-ten-minutes.html.
If you think you might need to add multiple patches, rework them etc.
I'd recommend using git.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing
On 25 November 2014 17:13:17 CET, peterengcomau...@adam.com.au
peterengcomau...@adam.com.au wrote:
My original problem is that the image built in 1.6.1 does not build in
1.7. Paul indicated this is probably because of the -foreign issue as
referred to in the reference manual Section 5.6.3 when
* Matt Schuckmann matt.schuckm...@planar.com [141126 18:22]:
Yes you are correct I want a small number of files into to reside in a
writeable partition with links in the root file system to point to
them. I guess I latched on to the volatiles mechanism because it seems
close to meeting my
will be much appreciated.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
directory.
Thus, you really should be using the tarball when you want to run an
nfsroot.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* matthias.he...@atlas-elektronik.com matthias.he...@atlas-elektronik.com
[141210 11:48]:
-Ursprüngliche Nachricht-
Von: Anders Darander [mailto:and...@chargestorm.se]
Gesendet: Mittwoch, 10. Dezember 2014 11:24
An: Heise, Matthias
Cc: j...@spectralogic.com; yocto
as distro features today.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
that rewrites URLs? The https:// URL should
look like https://git.yoctoproject.org/git/poky/...
When `repo sync` works for me, I'm still getting the git:// URLs.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
avoid calling do_compile() as there is no makefile its plain
file repo which need to be packaged.
Just create an empty do_compile(). Or you could remove do_package() from
the task list for this recipe, though, it's slightly easier to just
provide an empty do_compile().
Cheers,
Anders
--
Anders
in different directories and need
to be placed in some predefined paths.
So how we can achieve the same.
Thanks,
Abhinav
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https
checking *recipe* names, not layer names...
Thus, you'll have to look for another example. ;)
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi,
* Barros Pena, Belen belen.barros.p...@intel.com [150331 18:00]:
On 31/03/2015 10:39, Anders Darander and...@chargestorm.se wrote:
I don't know if this is the right thread but a couple of other things
that we really would need in order to fully be able to utilize this.
1) Some way
them?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
with something stalling).
Can anyone point me in the right direction?
Just a couple of questions.
Does the log.do_fetch reveal anything?
If you enable the debug flags for bitbake, do you get anything that
makes sense when re-running the fetch task?
Cheers,
Anders
--
Anders Darander
ChargeStorm
wouldn't
create a patch to patch it in the source tree. I'd rather just add the
complete config file to FILES +=... and then replace the one from the
source package with my copy in a do_install_appen() function.
This is by far the simplest way of those two.
Cheers,
Anders
--
Anders Darander
On 17 Apr 2015 16:30, Paul Eggleton paul.eggle...@linux.intel.com wrote:
I have sent an additional patch to the bitbake list to try to protect
against
future instances of this issue, at least for bb.utils.prunedir() and
bb.utils.remove():
in either one of the current packages, or in a new
package.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
these files should be installed.
Add a line:
FILES_${PN} += /opt/we_remote
to your recipe. This should tell the packaging step that all files under
/opt/web_root should be included in the ${PN}-package.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
support nightmare again...
If the checksums can be guaranteed to be stable, then, yes, such a
change can be looked upon.
Shallow clones is in this case a lot more likely to be usefull, though,
implementing that might have a few issues on it's own...
Cheers,
Anders
--
Anders Darander
No, avoid doing this. The reasons are the same as why you shouldn't
unpack the tarball using a new image type; you're not allowed to set the
correct owner, group, and permissions on files, nor are you allowed to
create device nodes.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
* Andre McCurdy <armccu...@gmail.com> [151103 11:34]:
> On Mon, Nov 2, 2015 at 11:05 PM, Anders Darander <and...@chargestorm.se>
> wrote:
> > * Andre McCurdy <armccu...@gmail.com> [151102 20:35]:
> >> See the "IMAGE_TYPES" variable for a list
RES =+ "ssh-server-dropbear" *in image recipe*.*
> Can i able to change dropbear.service file before creating final image.
Sure, add a bbappend-file in your layer, and add your own versions of
those two service-files in your layer.
Cheers,
Anders
--
Anders Dara
* Andy Hung(洪翊桓_Pegatron) <andy_h...@pegatroncorp.com> [151202 10:49]:
> Hi Anders,
> Thanks for your help, pls see updates below,
> > Message: 2
> > Date: Tue, 24 Nov 2015 14:25:14 +0100
> > From: Anders Darander <and...@chargestorm.se>
> > To: yoct
* Andy Hung(洪翊桓_Pegatron) <andy_h...@pegatroncorp.com> [151125 11:53]:
> Message: 2
> Date: Tue, 24 Nov 2015 14:25:14 +0100
> From: Anders Darander <and...@chargestorm.se>
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Header files in /usr/include of rootfs
> M
ed for normal operation.
How flexible to you intend to make this system? Allow everything that
swupdate supports? Or a specific subset?
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
If we have a machine specific defconfig 'defconfig' in our meta-data, the
install
command fails. OTOH, in that case it's not necessary to copy it into twe WORKDIR
either.
Signed-off-by: Anders Darander <and...@chargestorm.se>
---
recipes-kernel/linux/linux-raspberrypi.inc | 4 +++-
ge/mkknlimg --dtok
> ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
> +${STAGING_DIR_NATIVE}${libexecdir}/mkknlimg --dtok
> ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
> fi
> fi
> }
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Borzecki on Feb 2nd. I think this is worth taken into
> account.
>
Yes, that's right.
If the rest of the patches in that series is non-controversial, could we
have them applied? Otherwise, could we have Khem's patch applied, and
the other series rebased upon that?
We've had the mast
On Fri, 26 Feb 2016, 03:54 Khem Raj wrote:
> Go ahead
>
Yes, go ahead.
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
SCRIPT_PARAMS = "start 02 2 3 4 5 . stop 01 0 1 6 ."
> INITSCRIPT_NAME = "can_if"
> CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
If this is the complete recipe, you never install can_if...
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB /
or QA the LTS branches.
I'm pretty sure that this is the point Philip was after, that it really
doesn't make sense for Poky.
LTS branches in oe-core and bitbake, OTOH, makes sense, and would be
appreciated by quite some.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB
cipe.
> I changed my [task] dependencies to match what you've quoted and everything
> works as before. !Thanks!
I'd still recommend doing as little as possible in each recipe, and
leverage the standard modules.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStor
> AAA.bbappend:
> pkg_postinst_AAA() {} - OK
> pkg_postinst_AAA_append() {} - OK
> pkg_postinst_BBB() {} - NG
> pkg_postinst_BBB_append() {} - NG
A recipe can't influence another recipe, thus this isn't going to work.
However, a single recipe can build multiple packages, eg AAA and
AAA-fo
platform developers will 'git clone'
my_git_repo/yocto_git/... <-- yocto framework
my_git_repo/meta-openembedded
Well, I'm using bitbake and openembedded-core repos directly instead of
yocto, but that doesn't really matter.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeSto
, it'll be better in the long run.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
> 3. Untar the tar ball under
> {YOCTO_BUILD_DIR}//tmp//deploy/image/{TARGET}/*rootfs.tar.bz2 to the export
> dir
> - takes additional time.. Not good.
This is the right way to do it.
If it takes to much time, create a script that runs bitbake and then
untars the rootfs.
Cheers,
Anders
--
ipt in build/tmp/deploy/sdk/ to install the
> sdk, I can see that the library is not installed in the sdk sysroot. The
> header is there, but the static library is not.
> I also tried adding this to local.conf:
> EXTRA_IMAGE_FEATURES += "staticdev-pkgs"
> but that also
can i assume those should read "machine.conf"? because i have no
> idea what "bsp_name.conf" refers to as it is.
Yes, that's the machine.conf...
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
* Riko [170815 07:42]:
> Do you mean this one ?
Yes.
> Build Configuration:
> BB_VERSION= "1.34.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE = "beaglebone"
> DISTRO
> > yocto mailing list
> > > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> > > https://lists.yoctoproject.org/listinfo/yocto
> > <https://lists.yoctoproject.org/listinfo/yocto>
> > --
> > ___
t still prefer /
require a few smaller python applications.
You'd be welcome to suggest that people try to install the complete
pyhton(3)-modules package, as that makes it easier for everyone with
large eMMC's and SD-cards, though.
Cheers,
Anders
--
Anders Darander, Senio
fix this will be to include required static libraries in the image
> before building SDK - eg: for glibc static development libraries:
> IMAGE_INSTALL_append = " glibc-staticdev"
Why install it to the image?
TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
woul
> files making up the demo). I ran "bitbake -c populate_sdk test-image"
> and I expected the file usr/lib/test-lib to be present in the SDK, but
> it is not.
Ah, a small test example? Perfect!
Could you add it the bug above? It would likely make it easier to debug.
Cheers
Anders
gt; acceptable method is to have a simple way of ensuring that a certain
> file is converted to that symlink.
This is normally done by a manual inspection / addition of bbappend
file.
Cheers,
Anders
--
Anders Darander, Senior System Architect
Ch
Should I make any other setting to add the “navit” recipe to my image?
> Is this the correct method of copying "recipes-navigation" folder to
> "/poky/meta " ?
Well, it works. If you don't mind the rest of meta-oe, I'd rather add
that layer to conf/bblayers.conf. That wo
? That seems like a bug to me...
You could add
TOOLCHAIN_TARGET_TASK += "boost"
to the image. That should drag in boost for you. (Maybe you should use
boost-dev instead?)
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
_
ld be able to tell you that you're
not using the jethro branch of meta-oe, but rather the master branch, a
lot easier.
You need to use the correct branches for all your layers. Mixing release
branches for certain layers, and master branches for other is a no-go,
unless you know what you're doing. (
80 matches
Mail list logo