On Fri, Nov 8, 2019 at 4:24 PM Chris Johns <chr...@rtems.org> wrote:
> On 9/11/19 3:04 am, Joel Sherrill wrote:
> > When building the rtems-all.bset, the build log is quite large,
> especially when
> > there are failures.
>
> I have increased the limit on that list.
>
> > Would it make more sense for automated testing to build each target
> > independently? This would result in more, smaller emails.
>
> It is easier to track failures.
>
> > I am thinking it might be easier to figure out the specific failures as
> well as
> > avoid having messages blocked to build@ for size.
>
> Yes.
>
> > I started this thought from having a msys2 build that took almost 3 days
> to
> > complete have multiple failures and get blocked for size at build@
>
> There is no pending email to that list from you for a Windows build. There
> were
> 3 emails of 1.1M pending, two from Sebastian and one from you. I have
> accepted
> all 3.
>
Grrr... is anything wrong with this command line?
../source-builder/sb-set-builder --prefix=/home/jrs007/mingw-tools-5
--keep-going --mail --mail-to=bu...@rtems.org --mail-from=j...@rtems.org
--log=l-all.txt 5/rtems-all
I wonder why no email got out. Any ideas? Might there be a hint in the log?
FWIW only 12 gcc's got installed.
$ ls ~/mingw-tools-5/bin/*gcc.exe
/home/jrs007/mingw-tools-5/bin/aarch64-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/bfin-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/i386-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/m68k-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/microblaze-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/mips-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/or1k-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/powerpc-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/sh-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/sparc64-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/v850-rtems5-gcc.exe
/home/jrs007/mingw-tools-5/bin/x86_64-rtems5-gcc.exe
I don't see arm, epiphany, lm32, moxie, nios2, riscv, or sparc.
ARM failed for this:
In file included from
../../../../../../../../../../gnu-mirror-gcc-fb371a33fa6/newlib/libm/machine/arm/s_floor.c:39:0:
../../../../../../../../../../gnu-mirror-gcc-fb371a33fa6/newlib/libm/machine/arm/../../math/s_floor.c:65:10:
fatal error: fdlibm.h: No such file or directory
#include "fdlibm.h"
^~~~~~~~~~
compilation terminated.
That looks quite odd. Is there still some issue with path length on the
build
system that I should have done something special for?
Any other ideas?
>
> Chris
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
