On Tuesday, 10 July 2018 3:32:56 AM CEST ChenQi wrote:
> I usually use the following steps when I need to modify source for some
> purpose.
>
> 1. bitbake A (or at least bitbake A -c configure)
> *2. cd tmp/work/x/A/**
> **3. make the modification*
> 4. bitbake A -c compile -f
> 5. bitbake A
Hello All,
This is the full report for 2.3.4.rc1:
https://wiki.yoctoproject.org/wiki/WW25_-_2018-06-22-_Full_Test_Cycle_-_2.3.4_rc1
=== Summary
All planned tests were executed. There were zero high milestone defect. Team
had found 3 new defects where yocto-bsp failed to cr
Hi Aron,
On 2018-07-10 05:18, Aaron Chan wrote:
This patch is to enable auto-assignments buildbot URL based on Hosts FQDN.
The socket module allows the retrieval on FQDN and constructs the entire
URL by default, this default settings can be overwritten in c['buildbotURL']
based on local administ
Thanks Ross. I found init-install.sh that I could relate to run-time
installation offered at BOOT time. And I'd used it to install image on SSD
from USB drive.
Would you or anyone know where the script that formats/generates .hddimg? I'd
like to see if we could customize the layout of this
On Tue., 10 Jul. 2018, 00:15 Andre McCurdy, wrote:
> On Mon, Jul 9, 2018 at 3:07 PM, Michael Allwright
> wrote:
> > Yes, it ended up in the development package in the do_install_append
> > attempt
>
> How did you confirm that (ie that the header ended up in the
> module-a-dev package) ?
In the
This patch is to fix the inconsistency in loading custom module
yoctoabb & yocto_console_view during Buildbot Master startup.
Signed-off-by: Aaron Chan
---
__init__.py| 0
yocto_console_view/__init__.py | 0
2 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644
This patch is to enable auto-assignments buildbot URL based on Hosts FQDN.
The socket module allows the retrieval on FQDN and constructs the entire
URL by default, this default settings can be overwritten in c['buildbotURL']
based on local administrator preferences.
Signed-off-by: Aaron Chan
---
On Fri, Jul 6, 2018 at 8:20 AM Simon Chamlian wrote:
>
> Hi,
>
> Is there a way to keep the source code of a package to be able to modify it
> and then compile?
>
> For example, with LTIB ( Linux Target Image Builder ), it was possible with a
> command to extract the source code from a package,
Hi Simon,
I usually use the following steps when I need to modify source for some
purpose.
1. bitbake A (or at least bitbake A -c configure)
*2. cd tmp/work/x/A/**
**3. make the modification*
4. bitbake A -c compile -f
5. bitbake A
If you find the modification useful, make a patch from it
On Mon, Jul 9, 2018 at 3:07 PM, Michael Allwright
wrote:
> Yes, it ended up in the development package in the do_install_append
> attempt
How did you confirm that (ie that the header ended up in the
module-a-dev package) ?
> , but I couldn't #include it in the second module (file didn't exist
>
Yes, it ended up in the development package in the do_install_append
attempt, but I couldn't #include it in the second module (file didn't exist
in the include search paths).
I would point out though, that I am interested in what is the correct way
to do this, and not just in finding some workarou
You may have missed one of my emails (still included here below) w.r.t. where
the issue came from. It's coming from application code outside of Yocto that
is built as 32-bit apps, while Poky/BSP are built in 64-bit.
From: Alexander Kanavin
Sent: Monday, July 9
Ah, so are you attempting to build 32 bit apps against a 64 bit
openssl from poky? I'd say you need to either enable multilib and
build the apps against lib32-openssl:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#combining-multiple-versions-library-files-into-one-image
or
The error message you've provided is caused by an openssl header
referring to another header file that doesn't exist. It does not come
from application code, but is due to openssl being incorrectly
configured.
Alex
2018-07-09 20:08 GMT+02:00 Raymond Yeung :
> You may have missed one of my emails
On Mon, Jul 9, 2018 at 8:27 AM, Michael Allwright
wrote:
> Hello,
>
> I think it would be useful to extend the hello-mod recipe in meta-skeleton
> to demonstrate some slightly more complicated scenarios. For example, I am
> trying to find out how to have two external kernel modules A and B, where
Hello,
I think it would be useful to extend the hello-mod recipe in meta-skeleton
to demonstrate some slightly more complicated scenarios. For example, I am
trying to find out how to have two external kernel modules A and B, where
module B #includes a header file provided by module A.
I have made
Current Dev Position: YP 2.6 M2.
Next Deadline: YP 2.6 M2 Build Target is July 16, 2018
SWAT Team Rotation:
· SWAT lead is currently: Ross
· SWAT team rotation: Ross -> Paul on July 13, 2018
· SWAT team rotation: Paul -> Tracy on July 20, 2018
· https://wiki.y
All,
The triage team meets weekly and does its best to handle the bugs reported into
the bugzilla. The numbers of people attending that meeting have fallen, as have
the number of people available to help fix bugs. One of the things we hear
users report is they don't know how to help. We (the
Just fix the build issue. Look into how opensslconf.h gets created and
where the -32 suffix comes from and why the included file is absent.
Seriously - that is less effort than trying to make Yocto do what it really
was not designed for, and certainly takes less than one week to resolve.
Also, yo
+ yocto mailing list.
From: Raymond Yeung
Sent: Sunday, July 8, 2018 5:31 PM
To: Burton, Ross
Subject: Re: [yocto] How to remove openssl from sysroots
We're not going to integrate everything into one homogeneous package. Poky and
BSP would be together. Then,
On Fri, Jul 06, 2018 at 09:11:35PM +0200, Ulf Samuelsson wrote:
In my current project we have a simplified version in a
”component.bbclass”. It relies on a variable COMPONENT_DIR
defined in our local.conf.
A recipe located in ”recipe-//_$PV.bb” doing
inherit component
will find its sour
Hello Team,
Under DISTRO_VERSION = "2.0.2" ("jethro"), I was using the attached
“setcap.patch” on pseudo_1.7.4 to get POSIX capability set in the files as
below :
pkg_postinst_${PN}() {
setcap cap_net_raw+ep $D$bindir/helloworld
}
This was working fine.
However, recently switched to
On Monday, 9 July 2018 10:45:58 AM CEST Robert Yang wrote:
> On 07/09/2018 04:36 PM, Paul Eggleton wrote:
> > On Monday, 9 July 2018 10:34:07 AM CEST Paul Eggleton wrote:
> >> On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
> >>> Fixed:
> >>> Assume there is no master branch in hello laye
If it's just a single simple binary that you need to run at build time
then you can build it manually in the target recipe before invoking
make.
The Pango recipe has an example of doing this.
Ross
On 7 July 2018 at 11:17, Alexander Kanavin wrote:
> How to do this is specific to each project. Ge
Some comments inline, including where I think your problem is:
On 9 July 2018 at 10:04, AKASH BHARDWAJ wrote:
> LICENSE = "CLOSED"
>>
>
Why are you setting LICENSE in local.conf?
> PACKAGE_FEED_URIS = " http://git.yoctoproject.org/cgit/cgit.cgi/meta-
>> raspberrypi/tree/recipes-devtools/wiring
./poky-glibc-x86_64-rpi-basic-image-cortexa7hf-neon-vfpv4-toolchain-2.4.3.sh
Poky (Yocto Project Reference Distro) SDK installer version 2.4.3
=
Enter target directory for SDK (default: /opt/poky/2.4.3):
/home/akash/rpil/rpi-build/tmp
The relevant recipes are in meta/recipes-core/initrdscripts/.
Ross
On 9 July 2018 at 04:10, Raymond Yeung wrote:
> This brings up the next logical question - where is the installer? I'd
> already done a grep and looked into the volume of output. You could ask
> why don't I read the code. Yes
On 07/09/2018 04:36 PM, Paul Eggleton wrote:
On Monday, 9 July 2018 10:34:07 AM CEST Paul Eggleton wrote:
Hi Robert,
On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
Fixed:
Assume there is no master branch in hello layer:
$ update.py -l hello -b master
INFO: Skipping update of laye
Hi Paul,
On 07/09/2018 04:34 PM, Paul Eggleton wrote:
Hi Robert,
On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
Fixed:
Assume there is no master branch in hello layer:
$ update.py -l hello -b master
INFO: Skipping update of layer hello - branch master doesn't exist
This is correct
On Monday, 9 July 2018 10:34:07 AM CEST Paul Eggleton wrote:
> Hi Robert,
>
> On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
> > Fixed:
> > Assume there is no master branch in hello layer:
> > $ update.py -l hello -b master
> > INFO: Skipping update of layer hello - branch master doesn'
Hi Robert,
On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
> Fixed:
> Assume there is no master branch in hello layer:
> $ update.py -l hello -b master
> INFO: Skipping update of layer hello - branch master doesn't exist
>
> This is correct since hello layer doesn't have master branch,
This patch is to add/update configuration needed to support several
hardware platforms on ARM64, x32, x86/x86-64, MIPS64, PPC on
autobuilder as new features added in 2.6 M2 and to support automated
manual BSP test case(s) for future QA releases.
Signed-off-by: Aaron Chan
---
config.py | 17 +
32 matches
Mail list logo
