On Mon, Sep 12, 2016 at 12:16 PM, Burton, Ross wrote:
>
> On 12 September 2016 at 19:22, Matthew Stanger
> wrote:
>>
>> I'm using Yocto 1.7.1 I'd like built programs to have the build path
>> striped down. The goal is if I'm looking at some programs log after cross
>> compiling I want this:
>>
>>
Ronald,
Was the kernel compiled with -fstack-protector?
Try running this on target:
cat /proc/kallsyms | grep __stack_chk_fail
Does it output the symbol address?
Take a look here: http://lxr.free-electrons.com/source/kernel/panic.c#L558
Best regards
2016-09-13 19:14 GMT-03:00 Ronald Oakes :
>
That resolved my problem. (And while I was at it, I found that I had
failed to create a new .bbappend file to pull my custom kernel config
file in when I had to change to an older kernel version due to kernel
versions supported by the vendor - so I had none of my other kernel
configurations either
I'm fighting to build PyQt5 (with Qt5) and have heard via irc someone
has done this. Does anyone have any info on this?
Thanks,
Philip
PS: Sorry for spamming three lists. I have very little to go one who
said they had done this, so no info on what community he might think he
is parts of. Why we
> On Sep 12, 2016, at 11:40 PM, Andreas Müller
> wrote:
>
> On Tue, Sep 13, 2016 at 4:06 AM, Jonathan Liu wrote:
>> The IMAGE_NAME variable already contains the date and time so it is
>> redundant to also include the date again with IMAGEDATESTAMP
>> when writing to image-version-info in the b
> On Sep 13, 2016, at 1:05 AM, Andreas Müller
> wrote:
>
> On Tue, Sep 13, 2016 at 2:19 AM, Andreas Müller
> wrote:
>> oe-core's commit d54339d4b1a7e884de636f6325ca60409ebd95ff creates image in
>> IMGDEPLOYDIR and copies through sstate to DEPLOY_DIR_IMAGE. That causes
>> DEPLOY_DIR_IMAGE not v
> On Sep 13, 2016, at 10:31 AM, robert.berger@gmane
> wrote:
>
> Hi,
>
> Shouldn't it be possible to build a bare-metal Cortex-M4 compiler with the YP
> and build a small RTOS like FreeRTOS with this compiler?
>
yes it should be possible. you can also look into meta-ti where I think they
t
> On Sep 12, 2016, at 11:32 PM, milad hasanvand
> wrote:
>
> Dear all,
>
> based on the material presented in GDP master, i successfully compiled it and
> it is working. but when i try to extract sdk using this command " bitbake
> genivi-dev-platform-sdk -c populate_sdk " i got the following
On Mon, Sep 12, 2016 at 7:02 AM, Gujulan Elango, Hari Prasath (H.)
wrote:
> Hello All
>
> We are including the meta-ivi layer in our custom distribution. There is a
> package 'dlt-daemon' whose fetch URL got modified upstream in the recipe file
> due to some corruption in the repositories. I wan
Hi,
On 2016-09-13 21:55, Ronald Oakes wrote:
Any ideas how to proceed?
1) Can you try to use it from an in-tree kernel module? (modify the
attachment)
2) Can you grep in your kernel config for
CONFIG_CC_STACKPROTECTOR and friends?
Regards,
Robert
>From 69cabc395bd097dde34664b4e1fe1c57
Furthering my investagation into why my vendor supplied kernel modules
were failing to load due to the error "Unknown symbol __stack_chk_fail
(err 0)," I conducted the following experiment:
1: I took the sample code from
poky/meta-skeleton/recipes-kernel/helo-mod and moved it into a new
layer as m
Hi,
I use multi-v7 kernel for the zedboard and create a custom packagegroup
which contains openCV[1] which I add to the image.
[1]
https://github.com/RobertBerger/meta-mainline/blob/jethro-training-v4.4.x/multi-v7-ml/recipes-core/packagegroups/packagegroup-opencv.bb
Regards,
Robert
--
__
Hi,
Shouldn't it be possible to build a bare-metal Cortex-M4 compiler with
the YP and build a small RTOS like FreeRTOS with this compiler?
Regards,
Robert
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yoct
Thanks for the help! The solution is simple. As mentioned by Ross No
do_fetch extension is needed. The extract + copy goes into do_install.
part of the recipe
do_install () {
install -d ${D}/opt
tar -xzf example.tar.gz -C ${D}/opt/
}
FILES_${PN} += "/opt/*"
Re
On 13 September 2016 at 08:08, wrote:
>
> ??? do_fetch_append () {
> ???extract ${S}/example.tar.gz
> ??? }
> ??? do_install () {
> ???copy ${S}/ ${D}/opt/
> ??? }
It's a tarball so use "tar" to extract, and you'll need to mkdir ${D}/opt
before copying. but that's barely just p
On Tue, Sep 13, 2016 at 2:19 AM, Andreas Müller
wrote:
> oe-core's commit d54339d4b1a7e884de636f6325ca60409ebd95ff creates image in
> IMGDEPLOYDIR and copies through sstate to DEPLOY_DIR_IMAGE. That causes
> DEPLOY_DIR_IMAGE not valid when calling IMAGE_CMD. Therefore use
> IMGDEPLOYDIR for sdcard
Hej
I like to build an package out of a git repro. This git repro contains
compressed files. One of these files I like to copy into my package. I
looked into the documentation, but it is only described how to use the
fetcher of bitbake. Think I need to add some extra lines of instruction
after
On 12 September 2016 at 07:39, BHARATH RAJ wrote:
> Hi All,
>
> I am trying to build one recipes on Yocto2.0 based environment.
>
> However I am seeing following error.I wonder if this is a known problem.
>
> It says error: '__uint128_t' does not name a type
>
Details might help: e.g. what arch
18 matches
Mail list logo
