On Thu, 2019-04-11 at 08:42 +0530, akuster808 wrote:
>
> On 4/10/19 3:11 PM, richard.pur...@linuxfoundation.org wrote:
> > On Wed, 2019-04-10 at 05:56 +0530, akuster808 wrote:
> > > On 4/9/19 8:52 PM, Richard Purdie wrote:
> > > > I'm sorry to have to say this but the project is terminating
> > >
Hi Joe,
Thank you for working on the refpolicy upgrade.
I have a quick test with your patch. Here are the results:
Machine: qemux86-64
Image: core-image-selinux
Init manager: systemd
Boot command: runqemu qemux86-64 kvm nographic bootparams="selinux=1
enforcing=X" qemuparams="-m 1024"
1. All
Hi all.
I worked on my project woth Krogoth, gcc 5.3.0, on imx6dlsabresd board.
My application is build with cmake 3.4.3, shipped with BSP.
I'd like to strip debug symbols from the final binary, but if I prepend
the strip parameter in CMAKE_{C,CXX}_FLAGS_RELEASE in my CMakeLists.txt,
bitbake gi
Thanks
It was a typing error.
In my recipe I set the value as you told me.
But the ERROR keep on show
Il 10/04/19 11:59, mikko.rap...@bmw.de ha scritto:
> On Wed, Apr 10, 2019 at 11:47:42AM +0200, Mauro Ziliani wrote:
>> Hi all.
>>
>> I need to change the default IMAGE_NAME of my image recipe.
You need to use vardepsexclude (read in the bitbake manual how to).
Generally I am not a fan of putting timestamps into anything
yocto-built, it's prone to issues like this, breaks reproducibility,
and also subverts sstate if not managed carefully. I'd almost suggest
you build the image with a def
Thanks
I'll try your suggestion
Il 11/04/19 13:12, Alexander Kanavin ha scritto:
> You need to use vardepsexclude (read in the bitbake manual how to).
>
> Generally I am not a fan of putting timestamps into anything
> yocto-built, it's prone to issues like this, breaks reproducibility,
> and also
Just attempting to revive this dead horse again...
Anyone made any proress here?
Since cross-compiling turned out to be really really painful, I tried if
compiling on the board would be an option. No such luck, apparently the
Fortran compiler isn't being crosscompiled either.
On 26-01-19 20:0
Hi,
when searching for the files a package creates I find it very
practical to use `oe-pkgdata-util`. i.e.
oe-pkgdata-util list-pkg-files busybox
However the same method doesn't work when applied to
packagegroups.
--
___
yocto mailing list
yocto@yoctop
(ctrl+enter, sorry :/)
Anyways, the same (oe-pkgdata-util) approach doesn't work for
identifying what files a packagegroup installs.
```
oe-pkgdata-util list-pkg-files packagegroup-core-ssh-openssh
packagegroup-core-ssh-openssh:
```
A workaround seems to be finding the packagegroup source
a
Mike Looijmans Wrote:
> Just attempting to revive this dead horse again...
>
> Anyone made any proress here?
>
> Since cross-compiling turned out to be really really painful, I tried if
> compiling on the board would be an option. No such luck, apparently
> the Fortran compiler isn't being crosscom
Richard and Armin,
I am going to start pulling Eclipse from the docs today. The changes won't
make the frozen rc build but the website docs will reflect reality.
Scott
On Thu, Apr 11, 2019 at 12:20 AM wrote:
> On Thu, 2019-04-11 at 08:42 +0530, akuster808 wrote:
> >
> > On 4/10/19 3:11 PM, ri
On Thu, Apr 11, 2019 at 05:27:25PM +, Alistair Francis wrote:
> Signed-off-by: Alistair Francis
Acked-by: Denys Dmytriyenko
[YOCTO #13145]
This was announced at 2019.01:
https://www.mail-archive.com/u-boot@lists.denx.de/msg305424.html
Basically, am335x_boneblack is just a special subset o
On Thu, Apr 11, 2019 at 9:29 AM Scott Rifenbark
wrote:
> Richard and Armin,
>
> I am going to start pulling Eclipse from the docs today. The changes
> won't make the frozen rc build but the website docs will reflect reality.
>
Thank you, Scott.
>
> Scott
>
> On Thu, Apr 11, 2019 at 12:20 AM
>
On Tuesday, March 26, 2019 9:54 PM, Timothy Froehlich wrote:
> Is there a recommended way of doing this? Right now I have a
> ROOTFS_POSTPROCESS_CMD
> that moves the directories and symlinks them back, but I'm not sure if I'm
> doing it exactly right or if there's something built-in.
> The func
There is nothing wrong with my network network!
For now the issue is resolved.
Thanks any way.
On 2019-04-08 1:10 p.m., Burton, Ross wrote:
The better fix is to fix your network. If you need a proxy, set it in
local.conf.
Ross
On Mon, 8 Apr 2019 at 18:09, Nataliya Korovkina
wrote:
Hello
It's done but I keep the same problem, I've add zlib in the PACKAGECONFIG too
without any result...
De : Khem Raj
Envoyé : lundi 8 avril 2019 20:04
À : Clement CHERBEIX
Cc : Yocto Project
Objet : Re: [yocto] problem with ruby
On Mon, Apr 8, 2019 at 9:44 AM Clém
I've try that and doesn't change anything...
I think the problem is from the gem zlib who is not build / take by Yocto so it
can't be use.
When i try to use it with a simple ruby program i can't find zlib in the
environment of the devshell.
De : Khem Raj
Envoyé
Signed-off-by: Alistair Francis
---
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
index 70d3cfe..bc18ee8 100644
--- a/meta
[YOCTO #13145]
This was announced at 2019.01:
https://www.mail-archive.com/u-boot@lists.denx.de/msg305424.html
Basically, am335x_boneblack is just a special subset of am335x_evm config,
created and owned by BeagleBoard.org community. Since it was not migrated to
use CONFIG_BLK in time for 2019.04
Build should strip it automatically what does your build recipe look like
On Thu, Apr 11, 2019 at 1:37 AM Mauro Ziliani wrote:
> Hi all.
>
> I worked on my project woth Krogoth, gcc 5.3.0, on imx6dlsabresd board.
>
> My application is build with cmake 3.4.3, shipped with BSP.
>
>
> I'd like to s
On Wed, Apr 10, 2019 at 2:49 AM Mauro Ziliani wrote:
> Hi all.
>
> I need to change the default IMAGE_NAME of my image recipe.
>
> I make my image recipe as mysystem-image_1.0.bb and I'd like to produce
> and image (tar) with the name
>
> mysystem-image-1.0-.tar
>
>
Isn’t time stamp part of the s
21 matches
Mail list logo
