Hi mpe,
>> Further analysis suggests that making with -j1 triggers the issue, but
>> everything works with -j2 and above. That would make sense with the
>> timeline of when I discovered the issue because I changed my build
>> script to not build in parallel.
>
> I don't get why -j makes a differen
Hi dja,
Daniel Axtens writes:
> Right, so as both 0-day and snowpatch tell me, this patch is wrong.
>
> It turns out that this:
>> $(obj)/serial.c: $(obj)/autoconf.h
>> +$(Q)cp $< $@
> is identical to:
> cp arch/powerpc/boot/autoconf.h arch/powerpc/boot/serial.c
>
> (Clearly my make mastery
Right, so as both 0-day and snowpatch tell me, this patch is wrong.
It turns out that this:
> $(obj)/serial.c: $(obj)/autoconf.h
> + $(Q)cp $< $@
is identical to:
cp arch/powerpc/boot/autoconf.h arch/powerpc/boot/serial.c
(Clearly my make mastery is inadequate.)
Amusingly this which works f
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.20-rc4 next-20181128]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/c
A couple of weeks ago, I found my powerpc64e builds were broken
when building out-of-tree with make O=../destination:
BOOTCC arch/powerpc/boot/serial.o
powerpc64-linux-gnu-gcc: error: arch/powerpc/boot/serial.c: No such file or
directory
powerpc64-linux-gnu-gcc: fatal error: no input files
Th
