On 2016-09-09 2:33 PM, Clark, Mark A wrote:
All, I am still running into issues on building the RT image. I was
able to configure poky/jethro to create the core-image-rt. That being
said the kernel boot would hang at switching clock source “Switching to
clocksource tsc”. I was attempting to
Script was using /bin/sh and double brackets were causing an error in
nightly-oe-selftest build:
/home/pokybuild/yocto-autobuilder/bin/checkvnc: 6:
/home/pokybuild/yocto-autobuilder/bin/checkvnc: [[: not found
Changed double to single brackets to make sh happy.
Signed-off-by: Graydon, Tracy
--
On second thought… Forget this one. I will submit a new patch that
un-bashifies it. That would be the “right” thing to do.
-t
On 09/09/16, 1:15 PM, "yocto-boun...@yoctoproject.org on behalf of
Graydon, Tracy" wrote:
>Script was using /bin/sh and causing an error in nightly-oe-selftest
>build:
>
Following up as I've done more investigation and debugging this afternoon:
I've been able to resolve my problem with the missing symbolic link to
.so by explicitly including a runtime dependency
(RDEPENDS_${PN}) to the -dev module, so my link is now present on the
filesystem image at boot. I've a
Script was using /bin/sh and causing an error in nightly-oe-selftest build:
/home/pokybuild/yocto-autobuilder/bin/checkvnc: 6:
/home/pokybuild/yocto-autobuilder/bin/checkvnc: [[: not found
Changing script to use /bin/bash instead fixes the issue.
Signed-off-by: Graydon, Tracy
---
bin/checkvnc
On Fri, Sep 9, 2016 at 8:12 AM, Siegel, Jeffrey (Nokia - US) <
jeffrey.sie...@nokia.com> wrote:
> Thanks, this fixed the issue. After checking the output of ‘git log’, I
> picked this commit:
>
> git checkout d458b3
>
Sorry about that, I’ll see about creating stable release branches.
--
Christop
All, I am still running into issues on building the RT image. I was able to
configure poky/jethro to create the core-image-rt. That being said the kernel
boot would hang at switching clock source "Switching to clocksource tsc". I
was attempting to run down the issue there when the 2.1 krogo
I have some, I presume naive, questions about some messages I'm
getting as a result of running (or attempting to run) my
vendor-provided kernel module under qemu. (I've not tried on the real
hardware yet, I'd like it at least to boot somewhat cleaner on the
emulator before I commit to burning a CD
...nd HERE's the link
https://www.yoctoproject.org/yocto-project-developer-day-europe-2016
On Fri, Sep 9, 2016 at 8:51 AM, Jeff Osier-Mixon wrote:
> Hi all - we are in the planning stages for DevDay at ELCE right now,
> particularly the advanced track. This track changes every session,
> usua
Hi all - we are in the planning stages for DevDay at ELCE right now,
particularly the advanced track. This track changes every session,
usually to cover the things we are working on hardest - for example,
in San Diego we covered CROPS, devtool, the latest Toaster features,
and much more.
Whether y
Current Dev Position: YP 2.2 M4 (M3 Building rc1)
Next Deadline: YP 2.2 M4 which will be Oct. 3rd (5:00pm GMT)
SWAT team rotation: Alejandro -> Jussi
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
*M3 has continued to be problematic:
o The qem
Thanks, this fixed the issue. After checking the output of ‘git log’, I picked
this commit:
git checkout d458b3
Jeff
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
All,
We are planning to spin up a team to look at redefining/cleaning up the
categories in Yocto's bugzilla. We will then work on the migration to these
new categories and ensure each category has the correct default owner. If you
are interested in being an active participant, please let
On 9/9/16 6:33 AM, Takashi Matsuzawa wrote:
> Hello, Yocto.
>
>
> I am now puzzled by this variable ste in $CONFIG_SITE setup file in
> Yocto-generated SDK.
>
>
> I generated x86_64 host, arm (32bit) target SDK.
>
> And if I invoke $CC (arm-poky-linux-gnueabi-gcc), using this SDK, sizeof
> (
On 9/9/16 2:58 AM, Zhenhua Luo wrote:
> Hi all,
>
>
>
> Can Yocto support image build for Cortex-M4 targets? If no, does somebody know
> if there is some distro/packaging tool which can support Cortex-M4?
>
The Cortex-M4 does not have an MMU. The Yocto Project system, currently, only
support
This is because your distro has enabled the security options, but
native-frameworks has bad link lines that work without security flags more
via luck than anything else.
You'll need to fix the linking order used to build libbinder.
Ross
On 9 September 2016 at 08:15, BHARATH RAJ wrote:
> I am n
On 8 September 2016 at 23:06, Siegel, Jeffrey (Nokia - US) <
jeffrey.sie...@nokia.com> wrote:
> ‘bb’ Python source contains shebang path ‘/usr/bin/env python3’ , which
> means it expects to be run by a Python 3.x interpreter. But then it imports
> python code from bitbake/lib, and bitbake/Yocto us
I am now trying to build one recipe on Yocto 2.0 based environent.
Howerver, I am seeng following error.I wonder if this is a known
problem and you already have workaround?
It says undefined reference to `__init_array_start'.
This error did not happen with Yocto 1.8 based build, So, it can be
Hi,
I'm fairly new to Yocto, several web article recommend the use of Chris
Larson's 'bb' utility. I understand 'bb' is not part of Yocto, but perhaps
someone here knows the answer to my problem. Running 'bb log' in my build
directory results in:
[siegel@xxx junk]$ bb log
Traceback (most recent
Hello, Yocto.
I am now puzzled by this variable ste in $CONFIG_SITE setup file in
Yocto-generated SDK.
I generated x86_64 host, arm (32bit) target SDK.
And if I invoke $CC (arm-poky-linux-gnueabi-gcc), using this SDK, sizeof (long)
is 4 (long = int)
However, if I look into $CONFIG_SITE's d
Hi all,
Can Yocto support image build for Cortex-M4 targets? If no, does somebody know
if there is some distro/packaging tool which can support Cortex-M4?
Best Regards,
Zhenhua
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproj
* Takashi Matsuzawa [160908 14:23]:
> Provided the following scripts are provided, in two bbappend recipes
> as below, which of them are actually executed and which are not? I
> have briefly tried and 'OK's below are called and 'NG's are not.
> AAA.bbappend:
> pkg_postinst_AAA() {} - OK
> pkg_
22 matches
Mail list logo
