[U-Boot] Fwd: Parallel build is broken

[Alex Kiernan]

On Tue, Sep 4, 2018 at 3:54 PM Andy Shevchenko
<andy.shevchenko at gmail.com> wrote:
>
> On Tue, Sep 4, 2018 at 5:50 PM Andy Shevchenko
> <andy.shevchenko at gmail.com> wrote:
> >
> > On Tue, Sep 4, 2018 at 5:00 PM Tom Rini <trini at konsulko.com> wrote:
> > >
> > > On Tue, Sep 04, 2018 at 03:42:05PM +0300, Andy Shevchenko wrote:
> > >
> > > > ---------- Forwarded message ---------
> > > > From: Andy Shevchenko <andy.shevchenko at gmail.com>
> > > > Date: Tue, Sep 4, 2018 at 3:40 PM
> > > > Subject: Parallel build is broken
> > > > To: Tom Rini <trini at konsulko.com>
> > > > Cc: Bin Meng <bmeng.cn at gmail.com>, Simon Glass <sjg at chromium.org>
> > > >
> > > >
> > > > U-Boot can't be build with make -j16.
> > > >
> > > > Second pass passes fine.
> > > >
> > > > Didn't investigate myself and probably will not have time (near to
> > > > vacation time for me).
> > > > So, please, fix it before release.
> > > >
> > > > sh: echo: I/O error
> > > > make[1]: *** [scripts/Makefile.build:278: common/malloc_simple.o] Error 1
> > > > make[1]: *** Waiting for unfinished jobs....
> > > >  CC      drivers/serial/ns16550.o
> > > >  CC      drivers/spi/spi.o
> > > >  CC      cmd/mmc.o
> > > >  CC      drivers/watchdog/tangier_wdt.o
> > > >  CC      drivers/serial/serial_intel_mid.o
> > > >  CC      cmd/net.o
> > > >  CC      drivers/usb/common/common.o
> > > >  CC      arch/x86/lib/acpi.o
> > > >  LD      drivers/timer/built-in.o
> > > >  CC      arch/x86/lib/acpi_table.o
> > > >  CC      drivers/video/console_normal.o
> > > > make: *** [Makefile:1377: common] Error 2
> > > > make: *** Waiting for unfinished jobs....
> > >
> > > What build target (and O= or not?) is this with?  Thanks!
> >
> > make clean && make edison_defconfig && make -j16
> >
> > gcc (Debian 8.2.0-4) 8.2.0
> > Copyright (C) 2018 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> So, first time it's being built, consequent runs usually failed.
>

I've seen this problem - building inside a VMware VM. I've always
found that logging out and back in appears to fix it, so possibly
something related to the session... I've similarly failed to figure
out what the problem is as it comes and goes.

-- 
Alex Kiernan