mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Hazelton <dhazelton@enter.net>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@suse.cz>,
	linux-next@vger.kernel.org
Subject: Re: Strange linux-next build error
Date: Sun, 4 May 2008 00:40:18 +0200	[thread overview]
Message-ID: <20080503224018.GB18344@elte.hu> (raw)
In-Reply-To: <200805031825.50914.dhazelton@enter.net>


* Daniel Hazelton <dhazelton@enter.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

  reply	other threads:[~2008-05-03 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03  5:21 Daniel Hazelton
2008-05-03  5:52 ` Stephen Rothwell
2008-05-03  6:40   ` Sam Ravnborg
2008-05-03 16:10     ` Daniel Hazelton
2008-05-03 22:25     ` Daniel Hazelton
2008-05-03 22:40       ` Ingo Molnar [this message]
2008-05-04  1:37         ` Daniel Hazelton
2008-05-04  5:36           ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080503224018.GB18344@elte.hu \
    --to=mingo@elte.hu \
    --cc=dhazelton@enter.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®