* imx-bootlets build failure
@ 2013-09-17 14:03 Otavio Salvador
2013-09-17 14:24 ` Alexandre Belloni
0 siblings, 1 reply; 8+ messages in thread
From: Otavio Salvador @ 2013-09-17 14:03 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
Hello Alexandre,
I've put current master in autobuilder and got following build failure:
| make[1]: Entering directory
`/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o core/entry.o
core/entry.S
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o
core/resume.o core/resume.S
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036
-DCMDLINES_FILE=\"./output-target/command_lines_stripped.txt\"
-D__ASSEMBLY__ -o core/cmdlines.o core/cmdlines.S
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/setup.o core/setup.c
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/keys.o core/keys.c
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -o board/cfa10036.o
board/cfa10036.c
| arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
-fno-builtin -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o
hw/lradc-buttons.c
| arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
output-target/linux_prep.ld linux_prep.ld.in
| arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
./board/cfa10036.o ./hw/lradc-buttons.o -static -nostdlib -T
./output-target/linux_prep.ld -L./ -lgcc
| arm-poky-linux-gnueabi-ld: cannot find -lgcc
| make[1]: *** [output-target/linux_prep] Error 1
| make[1]: Leaving directory
`/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
| make: *** [linux_prep] Error 2
| ERROR: oe_runmake failed
| WARNING: /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/run.do_compile.13439:1
exit 1 from
| exit 1
| ERROR: Function failed: do_compile (log file is located at
/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/log.do_compile.13439)
Can you take a look at this?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-17 14:03 imx-bootlets build failure Otavio Salvador
@ 2013-09-17 14:24 ` Alexandre Belloni
2013-09-17 14:38 ` Otavio Salvador
0 siblings, 1 reply; 8+ messages in thread
From: Alexandre Belloni @ 2013-09-17 14:24 UTC (permalink / raw)
To: Otavio Salvador; +Cc: meta-freescale@yoctoproject.org
On 17/09/2013 16:03, Otavio Salvador wrote:
> Hello Alexandre,
>
> I've put current master in autobuilder and got following build failure:
>
> | make[1]: Entering directory
> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o core/entry.o
> core/entry.S
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o
> core/resume.o core/resume.S
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036
> -DCMDLINES_FILE=\"./output-target/command_lines_stripped.txt\"
> -D__ASSEMBLY__ -o core/cmdlines.o core/cmdlines.S
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/setup.o core/setup.c
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/keys.o core/keys.c
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o board/cfa10036.o
> board/cfa10036.c
> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o
> hw/lradc-buttons.c
> | arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
> output-target/linux_prep.ld linux_prep.ld.in
> | arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
> ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
> ./board/cfa10036.o ./hw/lradc-buttons.o -static -nostdlib -T
> ./output-target/linux_prep.ld -L./ -lgcc
> | arm-poky-linux-gnueabi-ld: cannot find -lgcc
> | make[1]: *** [output-target/linux_prep] Error 1
> | make[1]: Leaving directory
> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
> | make: *** [linux_prep] Error 2
> | ERROR: oe_runmake failed
> | WARNING: /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/run.do_compile.13439:1
> exit 1 from
> | exit 1
> | ERROR: Function failed: do_compile (log file is located at
> /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/log.do_compile.13439)
>
>
> Can you take a look at this?
>
Hum, weird, I built master this morning and it worked fine. Is that the
only board using the bootlets failing ?
I seem to get the same log but it is not failing:
arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc -fno-builtin
-O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o hw/lradc-buttons.c
arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
output-target/linux_prep.ld linux_prep.ld.in
arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
./board/cfa10036.o
./hw/lradc-buttons.o -static -nostdlib -T ./output-target/linux_prep.ld
-L/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/sysroots/cfa10058/usr/lib/a
rm-poky-linux-gnueabi/4.8.1/ -lgcc
arm-poky-linux-gnueabi-objcopy -R -S -O binary output-target/linux_prep
output-target/linux_prep.rom
make[1]: Leaving directory
`/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/work/cfa10058-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-sr
c-10.12.01/linux_prep'
I'll try to update my tree again and see if I can reproduce.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-17 14:24 ` Alexandre Belloni
@ 2013-09-17 14:38 ` Otavio Salvador
2013-09-17 15:12 ` Eric Bénard
2013-09-21 7:48 ` Alexandre Belloni
0 siblings, 2 replies; 8+ messages in thread
From: Otavio Salvador @ 2013-09-17 14:38 UTC (permalink / raw)
To: Alexandre Belloni; +Cc: meta-freescale@yoctoproject.org
On Tue, Sep 17, 2013 at 11:24 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 17/09/2013 16:03, Otavio Salvador wrote:
>> Hello Alexandre,
>>
>> I've put current master in autobuilder and got following build failure:
>>
>> | make[1]: Entering directory
>> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o core/entry.o
>> core/entry.S
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o
>> core/resume.o core/resume.S
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036
>> -DCMDLINES_FILE=\"./output-target/command_lines_stripped.txt\"
>> -D__ASSEMBLY__ -o core/cmdlines.o core/cmdlines.S
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/setup.o core/setup.c
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/keys.o core/keys.c
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o board/cfa10036.o
>> board/cfa10036.c
>> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
>> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o
>> hw/lradc-buttons.c
>> | arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
>> output-target/linux_prep.ld linux_prep.ld.in
>> | arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
>> ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
>> ./board/cfa10036.o ./hw/lradc-buttons.o -static -nostdlib -T
>> ./output-target/linux_prep.ld -L./ -lgcc
>> | arm-poky-linux-gnueabi-ld: cannot find -lgcc
>> | make[1]: *** [output-target/linux_prep] Error 1
>> | make[1]: Leaving directory
>> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
>> | make: *** [linux_prep] Error 2
>> | ERROR: oe_runmake failed
>> | WARNING: /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/run.do_compile.13439:1
>> exit 1 from
>> | exit 1
>> | ERROR: Function failed: do_compile (log file is located at
>> /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/log.do_compile.13439)
>>
>>
>> Can you take a look at this?
>>
>
> Hum, weird, I built master this morning and it worked fine. Is that the
> only board using the bootlets failing ?
>
> I seem to get the same log but it is not failing:
>
> arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc -fno-builtin
> -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o hw/lradc-buttons.c
> arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
> output-target/linux_prep.ld linux_prep.ld.in
> arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
> ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
> ./board/cfa10036.o
> ./hw/lradc-buttons.o -static -nostdlib -T ./output-target/linux_prep.ld
> -L/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/sysroots/cfa10058/usr/lib/a
> rm-poky-linux-gnueabi/4.8.1/ -lgcc
> arm-poky-linux-gnueabi-objcopy -R -S -O binary output-target/linux_prep
> output-target/linux_prep.rom
> make[1]: Leaving directory
> `/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/work/cfa10058-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-sr
> c-10.12.01/linux_prep'
>
> I'll try to update my tree again and see if I can reproduce.
Yes, this is weird indeed.
This has been done using my autobuilder and it helps to spot some
miss-use or weird things like that.
So it uses same tmp directory for all builds and it helps to spot some
inter-machine dependencies and wrong settings. I still not clear what
might be causing this yet.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-17 14:38 ` Otavio Salvador
@ 2013-09-17 15:12 ` Eric Bénard
2013-09-21 7:48 ` Alexandre Belloni
1 sibling, 0 replies; 8+ messages in thread
From: Eric Bénard @ 2013-09-17 15:12 UTC (permalink / raw)
To: Otavio Salvador; +Cc: meta-freescale@yoctoproject.org
Le Tue, 17 Sep 2013 11:38:29 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> On Tue, Sep 17, 2013 at 11:24 AM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
> > On 17/09/2013 16:03, Otavio Salvador wrote:
> >> Hello Alexandre,
> >>
> >> I've put current master in autobuilder and got following build failure:
> >>
> >> | make[1]: Entering directory
> >> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o core/entry.o
> >> core/entry.S
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -D__ASSEMBLY__ -o
> >> core/resume.o core/resume.S
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036
> >> -DCMDLINES_FILE=\"./output-target/command_lines_stripped.txt\"
> >> -D__ASSEMBLY__ -o core/cmdlines.o core/cmdlines.S
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/setup.o core/setup.c
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o core/keys.o core/keys.c
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o board/cfa10036.o
> >> board/cfa10036.c
> >> | arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc
> >> -fno-builtin -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o
> >> hw/lradc-buttons.c
> >> | arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
> >> output-target/linux_prep.ld linux_prep.ld.in
> >> | arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
> >> ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
> >> ./board/cfa10036.o ./hw/lradc-buttons.o -static -nostdlib -T
> >> ./output-target/linux_prep.ld -L./ -lgcc
> >> | arm-poky-linux-gnueabi-ld: cannot find -lgcc
> >> | make[1]: *** [output-target/linux_prep] Error 1
> >> | make[1]: Leaving directory
> >> `/home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-src-10.12.01/linux_prep'
> >> | make: *** [linux_prep] Error 2
> >> | ERROR: oe_runmake failed
> >> | WARNING: /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/run.do_compile.13439:1
> >> exit 1 from
> >> | exit 1
> >> | ERROR: Function failed: do_compile (log file is located at
> >> /home/otavio/hacking/fsl-community-bsp/build-2013-09-17/tmp/work/cfa10036-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/temp/log.do_compile.13439)
> >>
> >>
> >> Can you take a look at this?
> >>
> >
> > Hum, weird, I built master this morning and it worked fine. Is that the
> > only board using the bootlets failing ?
> >
> > I seem to get the same log but it is not failing:
> >
> > arm-poky-linux-gnueabi-gcc -c -Wall -I./include -nostdinc -fno-builtin
> > -O -DMX28 -DBOARD_CFA10036 -o hw/lradc-buttons.o hw/lradc-buttons.c
> > arm-poky-linux-gnueabi-cpp -P -DBASE_ADDR=0x00002000 -o
> > output-target/linux_prep.ld linux_prep.ld.in
> > arm-poky-linux-gnueabi-ld -o output-target/linux_prep ./core/entry.o
> > ./core/resume.o ./core/cmdlines.o ./core/setup.o ./core/keys.o
> > ./board/cfa10036.o
> > ./hw/lradc-buttons.o -static -nostdlib -T ./output-target/linux_prep.ld
> > -L/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/sysroots/cfa10058/usr/lib/a
> > rm-poky-linux-gnueabi/4.8.1/ -lgcc
> > arm-poky-linux-gnueabi-objcopy -R -S -O binary output-target/linux_prep
> > output-target/linux_prep.rom
> > make[1]: Leaving directory
> > `/home/alex/Projects/crystalfontz/fsl/cfa10058/tmp/work/cfa10058-poky-linux-gnueabi/imx-bootlets/10.12.01-r4/imx-bootlets-sr
> > c-10.12.01/linux_prep'
> >
> > I'll try to update my tree again and see if I can reproduce.
>
> Yes, this is weird indeed.
>
> This has been done using my autobuilder and it helps to spot some
> miss-use or weird things like that.
>
> So it uses same tmp directory for all builds and it helps to spot some
> inter-machine dependencies and wrong settings. I still not clear what
> might be causing this yet.
>
linux_prep/Makefile has :
LIBGCCDIR = $(dir $(shell $(CC) -print-libgcc-file-name))
CFLAGS = -Wall -I$(INCLUDEDIR) -nostdinc -fno-builtin -O
LDFLAGS = -static -nostdlib -T $(BOOT_LAYOUT_OUT) -L$(LIBGCCDIR) -lgcc
I remember I had to hack this when building bootlets with some
toolchains.
Eric
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-17 14:38 ` Otavio Salvador
2013-09-17 15:12 ` Eric Bénard
@ 2013-09-21 7:48 ` Alexandre Belloni
2013-09-21 21:37 ` Otavio Salvador
1 sibling, 1 reply; 8+ messages in thread
From: Alexandre Belloni @ 2013-09-21 7:48 UTC (permalink / raw)
To: Otavio Salvador; +Cc: meta-freescale@yoctoproject.org
On 17/09/2013 16:38, Otavio Salvador wrote:
>
> Yes, this is weird indeed.
>
> This has been done using my autobuilder and it helps to spot some
> miss-use or weird things like that.
>
> So it uses same tmp directory for all builds and it helps to spot some
> inter-machine dependencies and wrong settings. I still not clear what
> might be causing this yet.
>
Ok, so I can reproduce it, using the following steps:
MACHINE=cfa10036 . ./setup-environment build
bitbake core-image-minimal
rm -rf tmp/
cd ..
mv build/ build1
. ./setup-environment build1/
bitbake core-image-minimal
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-21 7:48 ` Alexandre Belloni
@ 2013-09-21 21:37 ` Otavio Salvador
2013-09-22 10:48 ` Alexandre Belloni
0 siblings, 1 reply; 8+ messages in thread
From: Otavio Salvador @ 2013-09-21 21:37 UTC (permalink / raw)
To: Alexandre Belloni; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Sat, Sep 21, 2013 at 4:48 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 17/09/2013 16:38, Otavio Salvador wrote:
>>
>> Yes, this is weird indeed.
>>
>> This has been done using my autobuilder and it helps to spot some
>> miss-use or weird things like that.
>>
>> So it uses same tmp directory for all builds and it helps to spot some
>> inter-machine dependencies and wrong settings. I still not clear what
>> might be causing this yet.
>>
>
> Ok, so I can reproduce it, using the following steps:
>
> MACHINE=cfa10036 . ./setup-environment build
> bitbake core-image-minimal
> rm -rf tmp/
> cd ..
> mv build/ build1
> . ./setup-environment build1/
> bitbake core-image-minimal
I am attaching the patch that fixes the issue for me. Can you give it a try?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
[-- Attachment #2: 0001-imx-bootlets-Pass-sysroot-for-compiler-and-linker.patch --]
[-- Type: application/octet-stream, Size: 1526 bytes --]
From 662b33a2fd0405e7a080ad061508fd926e05572b Mon Sep 17 00:00:00 2001
From: Otavio Salvador <otavio@ossystems.com.br>
Date: Sat, 21 Sep 2013 18:22:20 -0300
Subject: [PATCH] imx-bootlets: Pass sysroot for compiler and linker
Organization: O.S. Systems Software LTDA.
The build need to have the sysroot information explicit; the build
system of the imx-bootlets is horrible and does not reuse the values
provided by the environment so we need to force them.
This fixes a build failure in Crystal boards.
Change-Id: Ie5f0bd7271c90f219fdded320da579fa95ace159
Reported-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
recipes-bsp/imx-bootlets/imx-bootlets_10.12.01.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/recipes-bsp/imx-bootlets/imx-bootlets_10.12.01.bb b/recipes-bsp/imx-bootlets/imx-bootlets_10.12.01.bb
index 1ddfb6f..dd34ba8 100644
--- a/recipes-bsp/imx-bootlets/imx-bootlets_10.12.01.bb
+++ b/recipes-bsp/imx-bootlets/imx-bootlets_10.12.01.bb
@@ -39,7 +39,9 @@ do_configure () {
do_compile () {
oe_runmake BOARD=${IMXBOOTLETS_MACHINE} linux_prep \
boot_prep \
- power_prep
+ power_prep \
+ 'CC=${TARGET_PREFIX}gcc --sysroot="${STAGING_DIR_TARGET}"' \
+ 'LD=${TARGET_PREFIX}ld --sysroot="${STAGING_DIR_TARGET}"'
}
do_install () {
--
1.8.4.rc3
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-21 21:37 ` Otavio Salvador
@ 2013-09-22 10:48 ` Alexandre Belloni
2013-09-22 20:27 ` Otavio Salvador
0 siblings, 1 reply; 8+ messages in thread
From: Alexandre Belloni @ 2013-09-22 10:48 UTC (permalink / raw)
To: Otavio Salvador; +Cc: meta-freescale@yoctoproject.org
On 21/09/2013 23:37, Otavio Salvador wrote:
> On Sat, Sep 21, 2013 at 4:48 AM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> On 17/09/2013 16:38, Otavio Salvador wrote:
>>> Yes, this is weird indeed.
>>>
>>> This has been done using my autobuilder and it helps to spot some
>>> miss-use or weird things like that.
>>>
>>> So it uses same tmp directory for all builds and it helps to spot some
>>> inter-machine dependencies and wrong settings. I still not clear what
>>> might be causing this yet.
>>>
>> Ok, so I can reproduce it, using the following steps:
>>
>> MACHINE=cfa10036 . ./setup-environment build
>> bitbake core-image-minimal
>> rm -rf tmp/
>> cd ..
>> mv build/ build1
>> . ./setup-environment build1/
>> bitbake core-image-minimal
> I am attaching the patch that fixes the issue for me. Can you give it a try?
>
Working fine on my side !
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: imx-bootlets build failure
2013-09-22 10:48 ` Alexandre Belloni
@ 2013-09-22 20:27 ` Otavio Salvador
0 siblings, 0 replies; 8+ messages in thread
From: Otavio Salvador @ 2013-09-22 20:27 UTC (permalink / raw)
To: Alexandre Belloni; +Cc: meta-freescale@yoctoproject.org
On Sun, Sep 22, 2013 at 7:48 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 21/09/2013 23:37, Otavio Salvador wrote:
>> On Sat, Sep 21, 2013 at 4:48 AM, Alexandre Belloni
>> <alexandre.belloni@free-electrons.com> wrote:
>>> On 17/09/2013 16:38, Otavio Salvador wrote:
>>>> Yes, this is weird indeed.
>>>>
>>>> This has been done using my autobuilder and it helps to spot some
>>>> miss-use or weird things like that.
>>>>
>>>> So it uses same tmp directory for all builds and it helps to spot some
>>>> inter-machine dependencies and wrong settings. I still not clear what
>>>> might be causing this yet.
>>>>
>>> Ok, so I can reproduce it, using the following steps:
>>>
>>> MACHINE=cfa10036 . ./setup-environment build
>>> bitbake core-image-minimal
>>> rm -rf tmp/
>>> cd ..
>>> mv build/ build1
>>> . ./setup-environment build1/
>>> bitbake core-image-minimal
>> I am attaching the patch that fixes the issue for me. Can you give it a try?
>>
>
> Working fine on my side !
I have put this in master-next for testing; I am running this in my
auto-builder for testing.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2013-09-22 20:27 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-17 14:03 imx-bootlets build failure Otavio Salvador
2013-09-17 14:24 ` Alexandre Belloni
2013-09-17 14:38 ` Otavio Salvador
2013-09-17 15:12 ` Eric Bénard
2013-09-21 7:48 ` Alexandre Belloni
2013-09-21 21:37 ` Otavio Salvador
2013-09-22 10:48 ` Alexandre Belloni
2013-09-22 20:27 ` Otavio Salvador
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.