Re: [yocto] [PATCH] Added missing LDFLAGS in sample recipe for morty branch
Hi,
Yes but it was fixed that way in the Pyro branch.
do_compile() {
${CC} ${LDFLAGS} helloworld.c -o helloworld
}
regards
--
Pierre FICHEUX -/- CTO Smile-ECS, France -\- pierre.fich...@smile.fr
http://www.smile.fr
http://ingenierie.openwide.fr
I would love to change the world, but they won't give me the source
code
Le 2017-07-01 16:53, Khem Raj a écrit :
On 7/1/17 12:52 AM, Pierre FICHEUX wrote:
This problem causes the following error :
ERROR: example-0.1-r0 do_package_qa: QA Issue: No GNU_HASH in the elf
binary
Signed-off-by: Pierre FICHEUX
---
.../target/arch/layer/recipes-example/example/example-recipe-0.1.bb
| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
b/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
index 5fbf594..e534d36 100644
---
a/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
+++
b/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
@@ -14,7 +14,7 @@ SRC_URI = "file://helloworld.c"
S = "${WORKDIR}"
do_compile() {
-${CC} helloworld.c -o helloworld
+${CC} ${LDFLAGS} helloworld.c -o helloworld
perhaps doing compile and link in two steps where CFLAGS and LDFLAGS
are
used would be clearer
something like
${CC} ${CFLAGS} -c helloworld.c -o helloworld.o
${LD} ${LDFLAGS} helloworld.o -o helloworld
}
do_install() {
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RPi app built with SDK won't load
Did you try compiling in text mode?
$ $CC -o test test.c
--
Pierre FICHEUX -/- CTO Smile-ECS, France -\- pierre.fich...@smile.fr
http://www.smile.fr
http://ingenierie.openwide.fr
I would love to change the world, but they won't give me the source
code
Le 2017-07-02 03:07, Paul D. DeRocco a écrit :
From: Andrea Galbusera [mailto:giz...@gmail.com]
Could you please post the exact source code of your test
program and the steps you take to (a) build the SDK and (b)
build your test executable? Is your running image a pretty
standard one (core-image-minimal, rpi-test-image or so) or do
your own with custom features?
It did have some custom features, so I did a plain build of
core-image-minimal using raspberrypi3 as the MACHINE. I also did a
populate_sdk for it, and installed the SDK in /opt/poky/2.2.1-a32 by
running the install script.
The test program test.c is just "int main(void) { return 0; }". I
normally use Eclipse CDT to compile native programs, so I set up a
cross project using the SDK, which involves a few manual settings,
including telling it the tools are in
/opt/poky/2.2.1-a32/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux,
and adding a --sysroot to the command lines. The compiler command
line came out as:
arm-poky-linux-gcc
--sysroot=/opt/poky/2.2.1-a32/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
-O3 -Wall -c -mfloat-abi=hard -MMD -MP -MF"test.d" -MT"test.o" -o
"test.o" "../test.c"
(without the line breaks). I had to add "-mfloat-abi-hard" to get it
to link. The link command line was:
arm-poky-linux-gcc
--sysroot=/opt/poky/2.2.1-a32/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
-s -o "test" ./test.o
(again, without the line breaks). After dd-ing the image to my SD
card, I mounted it and manually copied the "test" program into its
rootfs. When I stuck it in the RPi3 and ran it, I got
-sh: ./test: not found
The shell in this case is busybox, so the error message is slightly
different from bash.
I rechecked everything I had described before, analyzing the
executable and comparing it to some working executable from the
rootfs. There must be SOMETHING in my executable that the loader is
barfing on, after it's successfully opened the file but before it
starts looking for libraries. But it's an awfully small executable, so
it's hard to imaging where that something is hiding.
--
Ciao, Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Added missing LDFLAGS in sample recipe for morty branch
On Sun, Jul 2, 2017 at 1:01 AM, Pierre FICHEUX wrote:
> Hi,
>
> Yes but it was fixed that way in the Pyro branch.
>
I thought this patch was being proposed for master. If yes then different
solution in pyro should not be a big problem. you can always backport
the new patch to pyro
> do_compile() {
> ${CC} ${LDFLAGS} helloworld.c -o helloworld
> }
>
> regards
>
> --
> Pierre FICHEUX -/- CTO Smile-ECS, France -\- pierre.fich...@smile.fr
> http://www.smile.fr
> http://ingenierie.openwide.fr
> I would love to change the world, but they won't give me the source code
>
>
> Le 2017-07-01 16:53, Khem Raj a écrit :
>>
>> On 7/1/17 12:52 AM, Pierre FICHEUX wrote:
>>>
>>> This problem causes the following error :
>>>
>>> ERROR: example-0.1-r0 do_package_qa: QA Issue: No GNU_HASH in the elf
>>> binary
>>>
>>> Signed-off-by: Pierre FICHEUX
>>> ---
>>> .../target/arch/layer/recipes-example/example/example-recipe-0.1.bb|
>>> 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git
>>> a/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
>>> b/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
>>> index 5fbf594..e534d36 100644
>>> ---
>>> a/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
>>> +++
>>> b/scripts/lib/bsp/substrate/target/arch/layer/recipes-example/example/example-recipe-0.1.bb
>>> @@ -14,7 +14,7 @@ SRC_URI = "file://helloworld.c"
>>> S = "${WORKDIR}"
>>>
>>> do_compile() {
>>> -${CC} helloworld.c -o helloworld
>>> +${CC} ${LDFLAGS} helloworld.c -o helloworld
>>
>>
>> perhaps doing compile and link in two steps where CFLAGS and LDFLAGS are
>> used would be clearer
>>
>> something like
>>
>> ${CC} ${CFLAGS} -c helloworld.c -o helloworld.o
>> ${LD} ${LDFLAGS} helloworld.o -o helloworld
>>
>>
>>> }
>>>
>>> do_install() {
>>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RPi app built with SDK won't load
On Sat, Jul 1, 2017 at 6:07 PM, Paul D. DeRocco wrote:
>> From: Andrea Galbusera [mailto:giz...@gmail.com]
>>
>> Could you please post the exact source code of your test
>> program and the steps you take to (a) build the SDK and (b)
>> build your test executable? Is your running image a pretty
>> standard one (core-image-minimal, rpi-test-image or so) or do
>> your own with custom features?
>
> It did have some custom features, so I did a plain build of
> core-image-minimal using raspberrypi3 as the MACHINE. I also did a
> populate_sdk for it, and installed the SDK in /opt/poky/2.2.1-a32 by running
> the install script.
>
> The test program test.c is just "int main(void) { return 0; }". I normally
> use Eclipse CDT to compile native programs, so I set up a cross project using
> the SDK, which involves a few manual settings, including telling it the tools
> are in
> /opt/poky/2.2.1-a32/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux, and
> adding a --sysroot to the command lines. The compiler command line came out
> as:
>
> arm-poky-linux-gcc
> --sysroot=/opt/poky/2.2.1-a32/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
> -O3 -Wall -c -mfloat-abi=hard -MMD -MP -MF"test.d" -MT"test.o" -o "test.o"
> "../test.c"
>
> (without the line breaks). I had to add "-mfloat-abi-hard" to get it to link.
> The link command line was:
>
> arm-poky-linux-gcc
> --sysroot=/opt/poky/2.2.1-a32/sysroots/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
> -s -o "test" ./test.o
>
> (again, without the line breaks). After dd-ing the image to my SD card, I
> mounted it and manually copied the "test" program into its rootfs. When I
> stuck it in the RPi3 and ran it, I got
>
> -sh: ./test: not found
>
pick a program that runs fine on target say /sbin/init and your test program
then find the unstripped binaries of both on your build system. run
arm-poky-linux-gcc -A init and
arm-poky-linux-gcc -A test
send the output of both cmds.
> The shell in this case is busybox, so the error message is slightly different
> from bash.
>
> I rechecked everything I had described before, analyzing the executable and
> comparing it to some working executable from the rootfs. There must be
> SOMETHING in my executable that the loader is barfing on, after it's
> successfully opened the file but before it starts looking for libraries. But
> it's an awfully small executable, so it's hard to imaging where that
> something is hiding.
>
> --
>
> Ciao, Paul D. DeRocco
> Paulmailto:pdero...@ix.netcom.com
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] buildset-config/nightly-refkit: add layers to bbconf
Since we are parsing and building all the images in refkit-ci.inc,
there are some layers that are now required. This includes flatpak,
industrial, and ROS layers. Since we are building a dynamic set of
images based on this inc file, we should be adding these layers
dynamically as well at some point.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 6 ++
1 file changed, 6 insertions(+)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index ab3ef6fa6..1d2487da6 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -31,6 +31,9 @@ steps: [{'SetDest':{}},
'refkit/meta-security-isafw',
'refkit/meta-intel-realsense',
'refkit/meta-clang',
+ 'refkit/meta-flatpak',
+ 'refkit/meta-refkit-industrial',
+ 'refkit/meta-ros',
'refkit/meta-openembedded/meta-filesystems',
'refkit/meta-openembedded/meta-gnome',
'refkit/meta-openembedded/meta-networking',
@@ -65,6 +68,9 @@ steps: [{'SetDest':{}},
'refkit/meta-security-isafw',
'refkit/meta-intel-realsense',
'refkit/meta-clang',
+ 'refkit/meta-flatpak',
+ 'refkit/meta-refkit-industrial',
+ 'refkit/meta-ros',
'refkit/meta-openembedded/meta-filesystems',
'refkit/meta-openembedded/meta-gnome',
'refkit/meta-openembedded/meta-networking',
--
2.13.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to make changes and build u-boot source code in yocto
Hi, I am trying to make some changes in u-boot code and using bitbake u-boot to build. But it doesn't build. I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This also didn't work. Can I Get some help on how to change and build u-boot. Thanks, Prasoon -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Antwort: How to make changes and build u-boot source code in yocto
Hej ho my Workflow for adjusting uboot (u-boot-at91): 1.) build the original uboot 2.) apply changes 3.) create patch 3.1.) if you reconfigure it -> save/copy the config 3.2.) if you adding code -> use meld or something similar to create a patch 4.) create u-boot-at91_%.bbappend 4.1) copy patch/config into that recipe dir 4.2) check u-boot-at91_%.bbappend paths etc. 5.) rebuild I you mess to much around in /tmp/work*** you should use "-c clean"/"-c cleanall" to reset it regards Stefan ESA Elektroschaltanlagen Grimma GmbH Broner Ring 30 04668 Grimma Telefon: +49 3437 9211 181 Telefax: +49 3437 9211 26 E-Mail: s.jar...@esa-grimma.de Internet: www.esa-grimma.de Geschäftsführer: Dipl.-Ing. Jörg Gaitzsch Jörg Reinker Sitz der Gesellschaft: Grimma Ust.-ID: DE 141784437 Amtsgericht: Leipzig, HRB 5159 Steuernummer: 238/108/00755 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Von:Prasoon Kumar An: yocto@yoctoproject.org Datum: 03.07.2017 08:34 Betreff:[yocto] How to make changes and build u-boot source code in yocto Gesendet von: yocto-boun...@yoctoproject.org Hi, I am trying to make some changes in u-boot code and using bitbake u-boot to build. But it doesn't build. I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This also didn't work. Can I Get some help on how to change and build u-boot. Thanks, Prasoon-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
