Re: imx-bootlets build failure

["Eric Bénard" <eric@eukrea.com>]

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