mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Ingo Molnar <mingo@elte.hu>,
	rostedt@goodmis.org, fweisbec@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: cannot compile linux-2.6-tip tree
Date: Wed, 25 Nov 2009 10:00:18 +0100	[thread overview]
Message-ID: <20091125090018.GD1940@jolsa.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <1259101632.6188.6.camel@gimli.petrovitsch.priv.at>

On Tue, Nov 24, 2009 at 11:27:12PM +0100, Bernd Petrovitsch wrote:
> On Die, 2009-11-24 at 18:22 +0100, Jiri Olsa wrote: 
> > On Tue, Nov 24, 2009 at 04:45:11PM +0100, Ingo Molnar wrote:
> [...] 
> > > It's rare but happens. 'make clean' will cure that.
> Apart from disk full, hitting quota limits may give similar errors.
no quota..

>
> [...] 
> > I tried make clean and it did not help..
> 
> - Did you change the architecture without `make mrproper` in between?
>   Yes, `make clean` should cure that but ....
it did not :) new tree clone did

> - Did some cross-gcc, cross-objdump, ... get in the PATH?
nope

> 
> Save .config, `make mrproper`, put .config back, `make` and see it it
> persists.
I did "git clean -xdf" to wipe all out and hit the same issue

thanks,
jirka
> 
> Bernd
> -- 
> Firmix Software GmbH                   http://www.firmix.at/
> mobil: +43 664 4416156                 fax: +43 1 7890849-55
>           Embedded Linux Development and Services
> 

  parent reply	other threads:[~2009-11-25  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 12:41 Jiri Olsa
2009-11-24 14:52 ` Steven Rostedt
2009-11-24 15:05   ` Jiri Olsa
2009-11-24 15:12     ` Steven Rostedt
2009-11-24 15:45 ` Ingo Molnar
2009-11-24 17:22   ` Jiri Olsa
2009-11-24 22:27     ` Bernd Petrovitsch
2009-11-25  4:55       ` Steven Rostedt
2009-11-25  9:02         ` Jiri Olsa
2009-11-25  9:00       ` Jiri Olsa [this message]
2009-11-25 11:44         ` Bernd Petrovitsch

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=20091125090018.GD1940@jolsa.lab.eng.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=bernd@firmix.at \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /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®