Try doing:
${CC} test.c
This will invoke the cross compiler with all the compilation flags required to
produce
an executable for the target, using libraries on the target root file system.
From: Raghavendra Kakarla [raghavendra.kaka...@inedasystems.com
Wow. That must have taken some digging! Thanks, Paul!
From: Paul Eggleton [paul.eggle...@linux.intel.com]
Sent: Tuesday, February 24, 2015 8:19 AM
To: Jim Rafert
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Simple recipe quit working in dizzy
Jim
AM, Jim Rafert wrote:
> Hi Paul,
>
> Thank you for taking an interest in this.
>
> I looked at the log.do_rootfs, and didn't see anything that was immediately
> suspicious.
> I have inlined the log at the end of my reply, here.
>
> I don't see how such a simple
Hi Paul,
Thank you for taking an interest in this.
I looked at the log.do_rootfs, and didn't see anything that was immediately
suspicious.
I have inlined the log at the end of my reply, here.
I don't see how such a simple recipe could be broken by a Yocto bug, and not
have the
whole thing be
Hi all,
The following recipe, spectra-postbuild_0.1.bb, quit working when I ported from
1.6 daisy to 1.7.1 dizzy. I include the recipe in my image by adding it at the
end of of the IMAGE_INSTALL_append variable in my local.conf file. The purpose
of the recipe is simply to lay down some files
Hello Abhishek,
Here's some more information to supplement what Andrei wrote.
The Yocto build system is based upon OpenEmbedded (OE), which depends upon
bitbake recipes to build everything from the kernel to applications. Recipes
are gathered
into layers, which provide some aggregate functiona
t: Tuesday, December 23, 2014 1:21 AM
To: Paul Eggleton
Cc: Jim Rafert; yocto@yoctoproject.org
Subject: Re: [yocto] Building clang with Yocto
I tried ldd-ing my binary on my build machine since it doesn't work on my image
and it was built on glibc indeed. Since yocto is based on ulibc so it won&
user on the client are mapped to
the anonymous nfs user, which would cause the kind of errors you are seeing.
From: Jim Rafert [j...@spectralogic.com]
Sent: Monday, December 22, 2014 10:10 AM
To: matthias.he...@atlas-elektronik.com; yocto@yoctoproject.org
Subjec
at by mounting the root file system share from another nfs client
and testing if you can write/create files.
-Jim-
From: matthias.he...@atlas-elektronik.com [matthias.he...@atlas-elektronik.com]
Sent: Wednesday, December 10, 2014 1:31 AM
To: Jim Rafert;
using.
From: Yu, Chan KitX [chan.kitx...@intel.com]
Sent: Tuesday, December 09, 2014 8:24 PM
To: Liviu Gheorghisan; Jim Rafert; yocto@yoctoproject.org
Subject: Re: [yocto] Building clang with Yocto
Liviu and Jim,
The thing is I’m trying to integrate LLVM+Clang together in the LLVM recipe.
?
-Jim-
From: Liviu Gheorghisan [liviu.gheorghi...@enea.com]
Sent: Tuesday, December 09, 2014 9:27 AM
To: Yu, Chan KitX; Jim Rafert; yocto@yoctoproject.org
Subject: Re: [yocto] Building clang with Yocto
Hello Yu, Jim
I think you can get the clang executable into
Hi Matthias,
Sorry, I missed the kernel command line in all the other gobbledy-gook put out
by the boot.
Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp
nfsroot=:,v3,tcp
That doesn't look right to me.
-Jim-
From: matthias.he...@atlas-elektro
Hi Matthias,
>From the following,
IP-Config: Complete:
device=eth0, hwaddr=00:1f:7b:b4:12:00, ipaddr=10.42.0.84,
mask=255.255.255.0, gw=10.42.0.1
host=10.42.0.84, domain=, nis-domain=(none)
bootserver=10.42.0.1, rootserver=10.42.0.1, rootpath=
nameserver0=10.42.0.1
I can tell
the Yocto framework, you will share the information.
-Jim-
From: Yu, Chan KitX [chan.kitx...@intel.com]
Sent: Monday, December 08, 2014 6:19 PM
To: Jim Rafert; yocto@yoctoproject.org
Subject: RE: Building clang with Yocto
Hi Jim,
How did you jam the clang
Hello Chan,
I have been working to a similar goal, to include clang in the toolchain to be
used for compiling applications to run on the target. Using clang to compile
the OS and kernel are not required or desired by me.
You may get some insight from the thread I started in November on the
Hi Mike,
It sounds like using volatiles is the opposite of what you want. Unless I miss
the point,
what you want is to have your root file system mounted read-only with only
select files being
writable, and persistent. Volatiles are by definition not persistent.
Volatiles may be a part of you
nativesdk-automake \
nativesdk-shadow \
nativesdk-makedevs \
nativesdk-smartpm \
nativesdk-llvm \
nativesdk-postinst-intercept \
"
RDEPENDS_${PN}_darwin = "\
nativesdk-pkgconfig \
nativesdk-opkg \
nativesdk-libtool \
"
Thank you very much in
again, thank you for your help. You have greatly advanced my
understanding of building a recipe for the SDK.
-Jim-
From: Joseph Andrew de la Peña [jdelap...@lexmark.com]
Sent: Friday, November 14, 2014 12:39 AM
To: Jim Rafert
Cc: nick; yocto@yoctoproject.org
Subject: Re:
Thanks Nick, that will be much appreciated.
-Jim-
From: nick [xerofo...@gmail.com]
Sent: Thursday, November 13, 2014 1:42 PM
To: Jim Rafert; yocto@yoctoproject.org
Subject: Re: [yocto] New recipe for toolchain fails install, "ERROR: ld.so:
o
tc/default/volatiles/00_core
${D}/etc/default/volatiles/00_core.orig
grep -v volatile/log ${D}/etc/default/volatiles/00_core.orig | tee
${D}/etc/default/volatiles/00_core >/dev/null
rm ${D}/etc/default/volatiles/00_core.orig
Any ideas how to do this?
-Jim-
______
Thanks, Alex.
You have sharp eyes, my friend. I had been struggling with this one so long, I
guess I was not looking for typos.
-Jim-
From: Alex J Lennon [ajlen...@dynamicdevices.co.uk]
Sent: Tuesday, June 10, 2014 2:58 AM
To: Jim Rafert
Cc: yocto
I'm trying to gather all my post-build tweaks into a recipe that will be built
as part of an upper-level layer, so that they are installed after the meta
layer is processed. Many of these could be accomplished as part of .bbappend
files for the recipes that originally supply the config files, b
22 matches
Mail list logo
