From: Mirco Tischler <mt-ml@gmx.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [BUG: 2.6.26-rc3] ERROR: "____ilog2_NaN" undefined
Date: Sun, 25 May 2008 23:49:11 +0200 [thread overview]
Message-ID: <1211752151.16921.25.camel@mtlp.tischlernetz> (raw)
In-Reply-To: <20080525210329.GN1791@cs181133002.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On Mo, 2008-05-26 at 00:03 +0300, Adrian Bunk wrote:
> Can you try building without ccache?
>
Doesn't help, as expected. Man, I just realised what a great piece of
software ccache is;)
> Can you also try downloading the kernel sources as a tarball from
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing ?
Why should I? A fresh checkout of the mainline git-tree in combination with make clean should have the same effect, shouldn't it?(I already did that)
> > Btw: you noticed that this is x86_64 and not i386?
>
> I noticed (but I currently only have a 32bit userspace, and for this
> kind of error it shouldn't matter).
Ok. I just wanted to make sure it's no difference.
> cu
> Adrian
>
Thanks
Mirco
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-25 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 17:13 Mirco Tischler
2008-05-25 18:11 ` Adrian Bunk
2008-05-25 19:03 ` Mirco Tischler
2008-05-25 20:18 ` Adrian Bunk
2008-05-25 20:57 ` Mirco Tischler
2008-05-25 21:03 ` Adrian Bunk
2008-05-25 21:49 ` Mirco Tischler [this message]
2008-05-26 21:16 ` Mirco Tischler
2008-05-27 23:56 ` Adrian Bunk
2008-06-08 12:41 ` Mirco Tischler
2008-06-09 22:14 ` Greg KH
2008-06-10 10:15 ` Adrian Bunk
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=1211752151.16921.25.camel@mtlp.tischlernetz \
--to=mt-ml@gmx.de \
--cc=bunk@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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®