Re: i386 -current build failure

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Mon, 14 Aug 2023 at 13:50, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> On Mon, 14 Aug 2023 at 10:35, Martin Husemann <martin%duskware.de@localhost> wrote:
> >
> > On Mon, Aug 14, 2023 at 09:23:37AM +0100, Chavdar Ivanov wrote:
> > > Hi,
> > > ERROR: nbctfmerge: Input file adiantum_selftest.o was partially built
> > > from C sources, but no CTF data was present
> >
> > Can you reproduce it after removing that .o file (or the whole kernel build
> > directory)?
>
> I did reproduce it once more after removing that .o file. Subsequently
> I nuked the entire obj directory and restarted.
>
> I suspect this was a result of my previous attempt to build it on that
> particular host using NJOBS=4 - it is a quite old now system with an
> i7-2600K CPU on an Intel motherboard; it has some memory problems
> under heavier multicore load (memtest+ passes each individual stick
> fine, but whenever more than one stick is in use, any conbination of
> the four, two tests fail, one of them Intel says is not actually a
> failure, but apparently the other is...). I run the builds normally
> with NJOBS=1 and I am now so repeating the full i386 build.

.... which completed OK; there were no intervening cvs updates at all,
so the reason for the failure must have been exactly the above.

> >
> > This symptom often shows up when one of the ctf tools died in an earlier
> > run.
> >
> > Martin
>
> Chavdar
>
>
> --
> ----



-- 
----