[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080503224018.GB18344@elte.hu>
Date: Sun, 4 May 2008 00:40:18 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Daniel Hazelton <dhazelton@...er.net>
Cc: Sam Ravnborg <sam@...nborg.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
LKML <linux-kernel@...r.kernel.org>,
Pavel Machek <pavel@...e.cz>, linux-next@...r.kernel.org
Subject: Re: Strange linux-next build error
* Daniel Hazelton <dhazelton@...er.net> wrote:
> > Can you try to do a:
> > make V=1 and post the output a few screen fulls before and until
> > the bug triggers.
> > They I will see if I can work out what is happening.
> >
> > Thanks,
> > Sam
>
> I've been unable to trigger it with "make V=1 bzImage" - does the
> verbosity change, somehow, the default number of makes that get run ?
>
> If it does, I could try adding -j2 or similar to see if that causes it
> to trigger.
try something like:
make -j2 V=1 bzImage >log.txt 2>&1
and see whether the error shows up in log.txt. Console output caused by
the increased verbosity (especially if it's a slower console like an
xterm) can hide build races.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists