From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: .config file attached for your perusal..build stopped... Linux 5.9-rc1
Date: Tue, 18 Aug 2020 06:13:28 +0530 [thread overview]
Message-ID: <20200818004325.GA25134@debian> (raw)
In-Reply-To: <CAHk-=whm2fcvovhvtXceNzQGet=hZspqSBRrpoYzwe2ZhX=UNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On 16:32 Mon 17 Aug 2020, Linus Torvalds wrote:
>On Mon, Aug 17, 2020 at 2:25 PM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>>
>> Thanks, Linus ...I have attached the .config file with this mail for your
>> perusal.
>
>There's something wrong with your setup - like Randy, I cannot
>recreate the problem.
>
>I wonder if you perhaps have some buggy version of ccache installed,
>or something like that, which could mess up the build subtly?
>Corrupted ccache files can result in some really hard-to-debug stuff,
>because what the compiler sees isn't actually what you see when you
>look at the source files...
>
> Linus
I take your and Randy's word as it seems plausible. Let me bisect my
setup and see what bad introduced and importantly how it introduced.
Thanks a bunch to both of you!!
~Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-18 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:50 Linux 5.9-rc1 Linus Torvalds
2020-08-16 22:58 ` Re:..build stopped... " Bhaskar Chowdhury
2020-08-17 16:44 ` ..build " Linus Torvalds
2020-08-17 21:25 ` .config file attached for your perusal..build " Bhaskar Chowdhury
2020-08-17 23:22 ` Randy Dunlap
2020-08-17 23:32 ` Linus Torvalds
2020-08-18 0:43 ` Bhaskar Chowdhury [this message]
2020-08-17 1:35 ` Linux 5.9-rc1 (sparse? kernel/time/timekeeping.c) Randy Dunlap
2020-08-17 2:15 ` Luc Van Oostenryck
2020-08-17 2:17 ` Randy Dunlap
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=20200818004325.GA25134@debian \
--to=unixbhaskar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).