Hello all,
We have a device whose image is built using an older yocto image. It is
based on yocto Danny, if I recall correctly.
How do users of yocto handle the need occasionally to update one or more
component packages to deal with security vulnerabilities?
I am not a yocto expert and I
Hello,
I have an older yocto-based image built with Danny.
We have a need to update two components, php and dropbear, to the most
modern versions for security purposes.
What is the preferred way to do this without moving the whole image to
the latest version of poky/yocto? That would be a
Hello,
I would like to have yocto generate two copies of busybox, one
statically-linked and one dynamically linked. So I try to make a copy of
the busybox recipe and give it a new name like busybox-s_x.bb
But my knowlege of yocto comes up short and I get lots of errors.
Is there a way
, how can I build them both as separate targets?
Thanks,
Brian
On 6/17/2014 9:31 AM, Andrea Adami wrote:
On Tue, Jun 17, 2014 at 5:41 PM, Brian Smucker b...@bsmucker.eu.org wrote:
Hello,
I would like to have yocto generate two copies of busybox, one
statically-linked and one dynamically linked
).
And it errors out when it attempts to patch to
busybox-static-1.20.2-r2/busybox-static-1.20.2 (the S variable path).
What am I missing?
Thanks,
Brian
On 6/17/2014 9:31 AM, Andrea Adami wrote:
On Tue, Jun 17, 2014 at 5:41 PM, Brian Smucker b...@bsmucker.eu.org wrote:
Hello,
I would like
Hi,
Was wondering why this has not been answered. Maybe it is too dumb of a
question? If so, let me know or point me to some documentation.
Thanks.
Brian
On 5/23/2014 11:37 AM, Brian Smucker wrote:
Hello,
I have an initial ramfs image that I want to convert to Yocto. That is
in addition
, how would I begin to do it?
Thanks,
Brian
On 5/29/2014 8:38 AM, Søren Holm wrote:
Torsdag den 29. maj 2014 08:07:11 skrev Brian Smucker:
Hi,
Was wondering why this has not been answered. Maybe it is too dumb of a
question? If so, let me know or point me to some documentation.
I'm declaring
On 5/29/2014 12:38 PM, Søren Holm wrote:
Torsdag den 29. maj 2014 09:49:55 skrev Brian Smucker:
Thanks Soren,
My followup question is: Can I mix toolchains in this situation?
Can I compile the initramfs binaries with the uclibc toolchain based on
the poky-tiny distro and the regular file
Hello,
I have an initial ramfs image that I want to convert to Yocto. That is
in addition to the main yocto-based custom distro.
The initial ram fs is a tiny image based on uclibc (poky-tiny) and
having busybox and two other compiled apps. The main file system is
eglibc-based.
How is
wrote:
On Tue, Jan 15, 2013 at 6:57 PM, Brian Smucker b...@bsmucker.eu.org wrote:
Hi Rudolf,
On 1/15/2013 3:28 PM, Rudolf Streif wrote:
Brian,
What are you exactly referring to as new version? The package version
that bitbake builds is defined by the recipe, through the version
designation
Hello all,
I'm not sure if my prior question was unclear or if the question was
something nobody knows the answer to.
I think there's probably a simple answer, but maybe not.
So the background is this: A poky/danny setup where I have
previously-compiled core-image-minimal.
I force busybox
Gary,
Thank you. It seems the bitbake -C option was indeed what I wanted.
And researching it helped fill in some of the gaps in my understanding.
Thanks,
Brian
On 1/16/2013 11:09 AM, Gary Thomas wrote:
On 2013-01-16 12:02, Brian Smucker wrote:
Hello all,
I'm not sure if my prior
Hello All,
I'm a relative newbie to yocto/oe, but have got a ways down the road to
understanding, but the gaps in my understanding cause me great grief at
times.
I think this probably is a simple question, but somehow I'm doing
something wrong.
I recompile busybox with a new config:
Hi Rudolf,
On 1/15/2013 3:28 PM, Rudolf Streif wrote:
Brian,
What are you exactly referring to as new version? The package
version that bitbake builds is defined by the recipe, through the
version designation in the recipe's file name or through explicitly
setting PV.
I think what you
On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
On 12-12-24 02:59 PM, Brian Smucker wrote:
Hi,
Catching up on email from the holidays. Did you ever get an answer
to this ?
Not yet, resumed my quest today.
I'm a yocto mostly-newbie, trying to find my way. I have a custom layer
that I am
On 1/2/2013 1:12 PM, Bruce Ashfield wrote:
On 13-01-02 04:11 PM, Brian Smucker wrote:
On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
On 12-12-24 02:59 PM, Brian Smucker wrote:
Hi,
Catching up on email from the holidays. Did you ever get an answer
to this ?
Not yet, resumed my quest
, the light finally dawned that
there was something else going on.
The silver lining to all this thrashing around for me was the fact that
I do understand the kernel bitbake process much better.
Brian
On 1/2/2013 2:15 PM, Bruce Ashfield wrote:
On Wed, Jan 2, 2013 at 4:47 PM, Brian Smucker b
Hi,
I'm a yocto mostly-newbie, trying to find my way. I have a custom layer
that I am using to build a kernel. The layer right now consists of a few
kernel patches and a defconfig and is based on the standard kernel
otherwise.
When I do a diff on my defconfig and the bitbake generated
From a yocto also-newbie:
This is a helpful command: bitbake -e |grep xxx
where xxx is something like ^IMAGE_FSTYPE=
That retrieves the current settings of that variable.
It doesn't answer your main question of what are the options. I had
that exact question a week or so ago.
Thanks
Brian
19 matches
Mail list logo
