Hi
I want to add USB modeswitch and minicom packages on the target image. I am
using raspberry pi 3 for the same. How to add those two packages so that
they are enabled on target machine.
Regards
vishal
--
___
yocto mailing list
yocto@yoctoproject.org
On Mon, Oct 23, 2017 at 4:57 PM, vishal ashapur wrote:
> Ya, I want gcc compiler to be on target image. I'm using raspberry pi3
> board.
In local.conf add.
EXTRA_IMAGE_FEATURES_append = " tools-sdk tools-debug dbg-pkgs"
if you are using an image which does not inherit
Use tinfoil to collect all variable names globally and in each recipe.
No longer show the count of variables if they are undocumented.
Fixes [YOCTO #2086]
Signed-off-by: Amanda Brindle
---
scripts/contrib/bbvars.py | 90
The following changes since commit 65d23bd7986615fdfb0f1717b615534a2a14ab80:
README.qemu: qemuppc64 is not supported (2017-10-16 23:54:31 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib abrindle/bbvars_tinfoil
Ya, I want gcc compiler to be on target image. I'm using raspberry pi3
board.
On 24-Oct-2017 1:14 AM, "Randy MacLeod" wrote:
On 2017-10-23 01:17 PM, Khem Raj wrote:
> On Mon, Oct 23, 2017 at 4:52 AM, vishal ashapur
> wrote:
>
>> Hi
>> I'm
Hi Andrea,
You're right, I missed the SDK in the IMAGE_FEATURES. I just changed that in my
image recipe and rebuit the image and then the SDK and the sdk was not rebuilt
from the one earlier this morning.
Here is the line from my image recipe:
SDKIMAGE_FEATURES += "dev-pkgs dbg-pkgs
On Mon, Oct 23, 2017 at 10:31 PM, Greg Wilson-Lindberg
wrote:
> Hi Andrea,
> I added the dbg-pkgs to the IMAGE_FEATURES but it didn't seem to make a
> difference in what was included, still no .a file in the SYSROOT.
> Regards,
> Greg
Hi Greg,
maybe I wasn't clear, from
On 2017-10-23 01:17 PM, Khem Raj wrote:
On Mon, Oct 23, 2017 at 4:52 AM, vishal ashapur wrote:
Hi
I'm building a Linux kernel from yocto, on which I have to enable gcc. Can u
please tell me how to enable gcc. And also usb_modeswitch package
it uses gcc, I think you
On Mon, Oct 23, 2017 at 11:07 AM, Marlon Smith wrote:
> Khem, with a couple of modifications I was able to get this script working
> perfectly and installing the modules into the system automatically. Thanks
> a lot!
>
> If you or anyone else would like a copy of the
On Mon, Oct 23, 2017 at 4:52 AM, vishal ashapur wrote:
> Hi
> I'm building a Linux kernel from yocto, on which I have to enable gcc. Can u
> please tell me how to enable gcc. And also usb_modeswitch package
it uses gcc, I think you need to clarify your question a bit so
From: André Draszik
fscryptctl is a low-level tool written in C that handles
raw keys and manages policies for Linux filesystem
encryption [1].
For a tool that presents a higher level interface and
manages metadata, key generation, key wrapping, PAM
integration, and
From: André Draszik
fscryptctl is a low-level tool written in C that handles
raw keys and manages policies for Linux filesystem
encryption [1].
For a tool that presents a higher level interface and
manages metadata, key generation, key wrapping, PAM
integration, and
Hi
I'm building a Linux kernel from yocto, on which I have to enable gcc. Can
u please tell me how to enable gcc. And also usb_modeswitch package
Regards
Vishal
--
___
yocto mailing list
yocto@yoctoproject.org
On 23 October 2017 at 12:39, Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > poky is generated using combo-layer, which effectively cherry-picks
> commits from the parent repositories (in this case bitbake,
> > oe-core, meta-poky, meta-yocto-bsp). This explains why the SHAs don't
> poky is generated using combo-layer, which effectively cherry-picks
commits from the parent repositories (in this case bitbake,
> oe-core, meta-poky, meta-yocto-bsp). This explains why the SHAs don't
match, as the history doesn't match.
This is exactly my original point. We should have here
> WARNING: firmware-imx-1,5.4-r0 do-fetch:failed to fetch URL...
I recall, I had the same error. Seems that this particular URL (server) is
down for some reason. Happens for this package frequently.
You should try later, but continue to do the target with bitbake -k switch.
> Or better yet use
> http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-ma
nual.html#ref-classes-image-buildinfo
Since I am also (relatively) new to YOCTO, reading these emails makes me
think about dependencies between YOCTO distros and layers within distros.
Looking what is written here,
17 matches
Mail list logo