The idea comes from upstream arm compiler which `Build from
source for the Raspberry Pi'
$ ls /third_party/toolchains/cpus/arm/
arm_compiler_configure.bzl BUILD CROSSTOOL.tpl
https://www.tensorflow.org/install/source_rpi
Signed-off-by: Hongxu Jia
---
recipes-framework/tensorflow/files/BUILD
On Wed, Feb 13, 2019 at 2:43 AM Johann Obermayr
wrote:
>
> Hello,
>
>
>
> At this time we work with 1.3.2 (yes, it’s very old, but we are working to
> change to v2.5.x)
>
>
>
> We have some trouble with your toolchain.
>
> Kernel/scripts/basic/fixdep is missing.
>
this looks more like a
Hello,
At this time we work with 1.3.2 (yes, it's very old, but we are working to
change to v2.5.x)
We have some trouble with your toolchain.
1. Kernel/scripts/basic/fixdep is missing.
If I will compile in the toolchain kernel source directory "make scripts" I get
some other errors (see
Hello,
At this time we work with 1.3.2 (yes, it's very old, but we are working to
change to v2.5.x)
We have some trouble with your toolchain.
1. Kernel/scripts/basic/fixdep is missing.
If I will compile in the toolchain kernel source directory "make scripts" I get
some other errors (see
Dears,
I have built under Ubuntu/Linux 14.04 an Yocto image *imx-morty* for
i.MX6QP with *bitbake fsl-image-qt5*. Now I want to generate the
cross-toolchain for this image as follows
root@02849625e4d5:/home/root/fsl-morty-bsp/build-x11/tmp/deploy/sdk# sh
I'm using Yocto krogoth and meta-mingw to build the meta-toolchain for windows
system. The build is quite smooth.
I extract the built toolchain
poky-glibc-x86_64-meta-toolchain-core2-64-toolchain-2.1.tar.xz on windows to
c:/yocto2.1
However when I try to run a simple build from windows cmd
hua@nxp.com>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> The problem is that ccache is not finding the compiler after environment-
> setup*.sh is sourced.Your error message can
-
>> From: Daniel. [mailto:danielhi...@gmail.com]
>> Sent: Friday, July 01, 2016 4:48 AM
>> To: Zhenhua Luo <zhenhua@nxp.com>
>> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
>> Subject: Re: [yocto] Failed to cross compile kernel with Y
>> -Original Message-
>> From: Daniel. [mailto:danielhi...@gmail.com]
>> Sent: Wednesday, June 29, 2016 8:14 PM
>> To: Zhenhua Luo <zhenhua@nxp.com>
>> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
>> Subject: Re: [yocto] Failed to c
om>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> Is /usr/lib64/gcc a file or a link? Is it a valid link?
>
> 2016-06-29 5:52 GMT-03:00 Zhenhua Luo <zhenhua@nxp.com>:
bjsimics/bin
>
> $
>
> $ which gcc
>
> /usr/lib64/ccache/gcc
>
> $ gcc -v
>
> ccache: error: Could not find compiler "gcc" in PATH
>
> $
>
>
>
>
>
> Best Regards,
>
>
>
> Zhenhua
>
>
>
> From: Khem Raj [mai
st Regards,
Zhenhua
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Tuesday, June 28, 2016 10:48 PM
To: Zhenhua Luo <zhenhua@nxp.com>
Cc: yocto@yoctoproject.org
Subject: RE: [yocto] Failed to cross compile kernel with Yocto toolchain
/usr/lib64/ccache is unusual why do you have it in
k...@gmail.com]
> Sent: Tuesday, June 28, 2016 12:36 AM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> On Mon, Jun 27, 2016 at 1:16 AM, Zhenhua Luo <zhenhua@nxp.com>
;> From: Burton, Ross [mailto:ross.bur...@intel.com]
>> Sent: Tuesday, June 28, 2016 6:27 PM
>> To: Zhenhua Luo <zhenhua@nxp.com>
>> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
>> Subject: Re: [yocto] Failed to cross compile kernel with Yocto
Hi,
> From: Burton, Ross [mailto:ross.bur...@intel.com]
> Sent: Tuesday, June 28, 2016 6:27 PM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchai
On 28 June 2016 at 06:56, Zhenhua Luo wrote:
> [Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script.
> but the /usr/bin is in the PATH env variable.
>
You *do* have a gcc in /usr/bin, right?
Ross
--
___
Hello Khem,
> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Tuesday, June 28, 2016 12:36 AM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
&
On 03/17/2016 12:40 PM, gm...@reliableembeddedsystems.com wrote:
Hi,
It may sound slightly crazy:) but can I use a toolchain, which was created by
Poky as an external toolchain for Poky?
What I am after is something like this:
I create a multiplatfrom v7 compatible Yocto project, which spits
Hi,
It may sound slightly crazy:) but can I use a toolchain, which was
created by Poky as an external toolchain for Poky?
What I am after is something like this:
I create a multiplatfrom v7 compatible Yocto project, which spits out
toolchain/rootfs/kernel/various device trees.[1]
Now I
> On Oct 12, 2015, at 12:57 AM, atulkumar singh wrote:
>
> Hi All,
>
> Can anyone please tell me how to build a meta toolchain with debug support by
> setting CFLAGS to "-g -O0”.
>
Read
http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DEBUG_BUILD
Hi All,
Can anyone please tell me how to build a meta toolchain with debug support
by setting CFLAGS to "-g -O0".
I tried adding this into gcc recipe but that didn't worked out for me as
another option I even tried adding CFLAGS_gcc = "-g -O0".
But no success, actually I wish to debug inside a
Hi,
Try the following:
TARGET_CFLAGS_append = " -g -O0"
TARGET_CXXFLAGS_append = " -g -O0"
Thanks,
Best Regards, Wily Taekhyun Shin
=
Wily Taekhyun Shin
Research Engineer
R Center
Telechips Inc.
Tel : +
Hi,
I'm sure (or at least hope so) that there is documentation for this, but I just
couldn't find it.
We are using Yocto to build Linux images on couple different HW (x86 and imx6).
Now we would like to make SDK (with toolchain) for them.
I've learned that there is command: bitbake
On 05/11/15 03:52, Keskinarkaus, Teemu wrote:
I’ve learned that there is command: bitbake image-recipe –c
populate_sdk that’ll create the sdk. The thing is that it contains the
sysroots, but toolchain is not there.
Just to clarify, you're not literally typing bitbake image-recipe -c
maximatecc
making machines smart, safe and productive
-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com]
Sent: 12. toukokuuta 2015 1:03
To: Keskinarkaus, Teemu; yocto@yoctoproject.org
Subject: Re: [yocto] Toolchain and SDK
On 05/11/15 03:52, Keskinarkaus, Teemu
How can I install the yocto toolchain in directory that I choose (not the
default directory)?
I run poky...toolchain-1.6.2.sh (that created when I run 'bitbake
meta-toolchain'), and I choose target directory for SDK.
The toolchain Installed in the directory that I choose, but yet has a link
Hi all,
i tried to build a toolchain for Qt SDK with following command, but i
received an error.
Can anyone know how to fix it?
Thanks in advance.
*[tvtritin@g-105-1 build-core-image]$ bitbake -k meta-toolchain-qtLoading
cache: 100%
Hi All,
I wish to build my toolchain independent of host machine, either my sdk
machine is 32bit or 64 bit.
Like for 32bit host machine i am mentioning with i686 for SDKMACHINE in
local.conf and x86-64 for 64 bit machine.
Please let me know what i need to do to make my toolchain independent of
On Wed, Jul 16, 2014 at 3:28 PM, atulkumar singh
atul.singh...@gmail.com wrote:
I wish to build my toolchain independent of host machine, either my sdk
machine is 32bit or 64 bit.
Like for 32bit host machine i am mentioning with i686 for SDKMACHINE in
local.conf and x86-64 for 64 bit machine.
Hi Nicolas,
Thanks for your reply.
And i am using Fedora20.
Also please let me know how to check whether the machine has been install
with 32bit lib or not?
Thanks and regards,
Atul
On 16 Jul 2014 19:15, Nicolas Dechesne nicolas.deche...@linaro.org
wrote:
On Wed, Jul 16, 2014 at 3:28 PM,
On Wed, Jul 16, 2014 at 6:37 PM, atulkumar singh
atul.singh...@gmail.com wrote:
Thanks for your reply.
And i am using Fedora20.
Also please let me know how to check whether the machine has been install
with 32bit lib or not?
I don't use Fedora, so i can't give the exact instructions, but the
On 5 March 2014 21:14, Khem Raj raj.k...@gmail.com wrote:
On Wed, Mar 5, 2014 at 9:00 AM, Michael Gloff mgl...@emacinc.com wrote:
| *** Error: Package name contains illegal characters, (other than
[a-z0-9.+-])
hmm meta-environment-PMX-090T is a package name and
thats limitation of opkg
Paul,
The error is below. Machine name: PMX-090T. This is on dora 1.5.1
ERROR: Function failed: opkg-build execution failed
ERROR: Logfile of failure stored in:
/opt/oe/build/tmp/work/i686-nativesdk-emacsdk-linux/meta-environment-PMX-090T/1.0-r8/temp/log.do_package_write_ipk.15358
Log data
On Wednesday 05 March 2014 11:00:31 Michael Gloff wrote:
On Mon, Mar 3, 2014 at 12:52 PM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Sunday 02 March 2014 19:58:41 Michael Gloff wrote:
Is there a reason why the toolchain cannot be built with a machine name
that contains
Thanks,
Not a big deal at all to build the toolchain with a different machine name.
Just curious.
Michael Gloff
On Wed, Mar 5, 2014 at 11:45 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Wednesday 05 March 2014 11:00:31 Michael Gloff wrote:
On Mon, Mar 3, 2014 at 12:52 PM, Paul
On Wed, Mar 5, 2014 at 9:00 AM, Michael Gloff mgl...@emacinc.com wrote:
| *** Error: Package name contains illegal characters, (other than
[a-z0-9.+-])
hmm meta-environment-PMX-090T is a package name and
thats limitation of opkg backend, if you are too tied to
Hi Michael,
On Sunday 02 March 2014 19:58:41 Michael Gloff wrote:
Is there a reason why the toolchain cannot be built with a machine name
that contains capital letters? Seems weird, everything else builds fine,
but meta-toolchain fails complaining about caps.
Although machine names are
Is there a reason why the toolchain cannot be built with a machine name
that contains capital letters? Seems weird, everything else builds fine,
but meta-toolchain fails complaining about caps.
Thanks,
Michael Gloff
___
yocto mailing list
Hello all,
I am currently working with the zedboard using a rootfs generated with a
dylan branch of yocto (gsl, gnuplot, gnuradio, java, vlc, v4l-utils, and
openCV with C920 camera). My zImage and devicetree.dtb were built with
yocto sdk. My BOOT.BIN (FSBL system.bit and u-boot) were built with
Please post meta-xilinx questions to the meta-xilinx list.
On 01/03/2014 11:46 AM, Edward Vidal wrote:
Hello all,
I am currently working with the zedboard using a rootfs generated with a
dylan branch of yocto (gsl, gnuplot, gnuradio, java, vlc, v4l-utils, and
openCV with C920 camera). My
On 2014-01-03 15:48, Philip Balister wrote:
Please post meta-xilinx questions to the meta-xilinx list.
On 01/03/2014 11:46 AM, Edward Vidal wrote:
Hello all,
I am currently working with the zedboard using a rootfs generated with a
dylan branch of yocto (gsl, gnuplot, gnuradio, java, vlc,
I must be missing something obvious. It's easy for me to build and install a
toolchain package using
bitbake meta-toolchain
The resulting toolchain package shows up at...
./tmp/deploy/sdk/poky-eglibc-i686-meta-toolchain-core2-toolchain-1.5.sh
...which is easy to install.
It seems the proper way
Hi,
We have a requirement to build our own custom toolchain for BSP mips64
architecture.
We have to use glibc(2.13) instead of eglibc and newlib(1.20) instead of uclibc
as libraries. Toolchain to be build with version 4.6.3 . I am able to override
existing toolchain version SRC 4.7.2 to 4.6.3
Thanks for the information. That is what I was looking for. I was asking of
the canadian build possibilities for a toolchian and I found the answer to
that question.
If I may ask. There was a thread:
* I have a cross-toolchain supplied by an ARM SoC vendor which I need
to** use to build my
On Thu, Oct 31, 2013 at 1:38 AM, jan alexandru vaduva
vaduva.jan.alexan...@gmail.com wrote:
Thanks for the information. That is what I was looking for. I was asking of
the canadian build possibilities for a toolchian and I found the answer to
that question.
If I may ask. There was a thread:
I am trying something like this, but I have some annoying QA issues:
QA Issue: Files/directories were installed but not shipped
Hope to make them dissapear. I tried adding:
FILES_${PN} += ..
or
install -D -m 0755 ${S}/... ${D}/...
but with no succes.
Do you have any ideeas regarding this.
On Thu, Oct 31, 2013 at 7:54 AM, jan alexandru vaduva
vaduva.jan.alexan...@gmail.com wrote:
I am trying something like this, but I have some annoying QA issues:
QA Issue: Files/directories were installed but not shipped
Hope to make them dissapear. I tried adding:
FILES_${PN} += ..
or
On Thu, Oct 31, 2013 at 9:19 AM, jan alexandru vaduva
vaduva.jan.alexan...@gmail.com wrote:
I have attached the log file.
You need to package them up correctly in packages
Look at the external sourcery toolchain recipes for help
On Thu, Oct 31, 2013 at 6:11 PM, Khem Raj raj.k...@gmail.com
On Wed, Oct 23, 2013 at 6:19 AM, jan alexandru vaduva
vaduva.jan.alexan...@gmail.com wrote:
Hello,
I have a curiosity:
Take a toolchain that builds for a 32-bits architecture, but breaks for a
64-bits one.
Is there a way to ensure that when builded with Yocto that toolchain will be
On Wed, Oct 23, 2013 at 2:01 AM, Rohit2 Jindal
rohit2.jin...@aricent.com wrote:
Hi ,
Actually I am trying to compile our own toolchain by applying our board
specific patches to it in yocto . But getting error (attached error log)
while running gcc-cross-initial for 4.6.3 toolchain .
I
Hi ,
Actually I am trying to compile our own toolchain by applying our board
specific patches to it in yocto . But getting error (attached error log) while
running gcc-cross-initial for 4.6.3 toolchain .
I have removed some patches to make it compatible for my own required toolchain
patch
Hello,
I have a curiosity:
Take a toolchain that builds for a 32-bits architecture, but breaks for a
64-bits one.
Is there a way to ensure that when builded with Yocto that toolchain will
be generated and used to build target specific recipes.
Thanks,
Alex
Any reasons why toolchains compile wihtout any issues on sysvinit and not
with systemd?
On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop
swaroop.dama...@gmail.com wrote:
Yes... I thought the same and so, I made two build directories , one for
sysvinit and the other for systemd and the
On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop
satyaswaroop.dama...@gmail.com wrote:
Any reasons why toolchains compile wihtout any issues on sysvinit and not
with systemd?
On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop
swaroop.dama...@gmail.com wrote:
Yes... I thought
Hi Khem,
May I ask you where I have to set that because I dont see anything like
sysvinit has been set ... would be greatfull if you can tell me that
Greets,
Satya
On Thu, Jun 20, 2013 at 9:29 AM, Khem Raj raj.k...@gmail.com wrote:
On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop
Yeah.. I checked it and its true. In the errror its totally different issue
*| The following packages have unmet dependencies:*
*| udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed*
*| Recommends: libusb-dev but it is not installable*
*| Recommends:
On 20 June 2013 10:07, DAMARLA Satya Swaroop swaroop.dama...@gmail.com wrote:
The udev version to ve installed is 182-r7 bu I dont understand why 1:204-r0
is trying to get installed..
This is because your deploy directory contains the systemd udev
package, which is version 204 and so newer than
I think you guys are right and now I am able to build the toolchain
perfectly
On Thu, Jun 20, 2013 at 12:06 PM, Burton, Ross ross.bur...@intel.comwrote:
On 20 June 2013 10:07, DAMARLA Satya Swaroop swaroop.dama...@gmail.com
wrote:
The udev version to ve installed is 182-r7 bu I dont
I think I had to open the issue as its not closed... Here is more
clarity
The issue is I decided the problem may be with init_manager. I did two
builds one with sysvinit using traditional Poky distro and other one is
uisng systemd using new distribution which is different as we need a new
On 19 June 2013 13:08, DAMARLA Satya Swaroop swaroop.dama...@gmail.com wrote:
I think I had to open the issue as its not closed... Here is more
clarity
The issue is I decided the problem may be with init_manager. I did two
builds one with sysvinit using traditional Poky distro and other
On Thu, Aug 16, 2012 at 09:47:37PM -0700, Khem Raj wrote:
Hi All
Recently glibc build has been simplified upstream. It has dropped the
dependency on libgcc_s and libgcc_eh for building glibc itself.
This means that we can simplify our toolchain bootstrap a bit by
dropping 1 of the 3 cross
On Tue, Aug 21, 2012 at 5:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
Maybe it's because
http://git.openembedded.org/openembedded-core/commit/?id=30617bde61a3b0a0944b49a0c9fb7159dacbb19f
is missing PR bump and gcc wasn't rebuilt before eglibc upgrade (OEBasic not
OEBasicHash here).
Hi All
Recently glibc build has been simplified upstream. It has dropped the
dependency on libgcc_s and libgcc_eh for building glibc itself.
This means that we can simplify our toolchain bootstrap a bit by
dropping 1 of the 3 cross gcc build stages. We do not need
gcc-cross-intermediate
anymore.
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors of PPC that are not
currently supported:
* e500v2 (gcc needs
On Jul 15, 2011, at 8:37 AM, Richard Purdie wrote:
On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala ga...@kernel.crashing.org wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors of PPC that are not
currently supported:
*
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala ga...@kernel.crashing.org wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors of
On Fri, Jul 15, 2011 at 2:13 PM, Kumar Gala ga...@kernel.crashing.org wrote:
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain
68 matches
Mail list logo