From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Nigel Cunningham <nigel@tuxonice.net>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: 2.6.36-rc3 - Unable to build: "Error: input truncated"
Date: Sun, 12 Sep 2010 23:37:45 -0700 [thread overview]
Message-ID: <4C8DC6B9.3050701@gmail.com> (raw)
In-Reply-To: <4C8DC01A.4030206@tuxonice.net>
On 09/12/2010 11:09 PM, Nigel Cunningham wrote:
> Hi.
>
> On 13/09/10 15:28, Justin P. Mattock wrote:
>> probably the same thing I was hitting last week or similar... bisected
>> resulted in crazy numbers(way back in may) long story short
>> git clean -fx resolved the error over here..(so tied up with other
>> things something as simple as that, I forgot)
>>
>> hope this helps..
>
> 'fraid not.
>
> What I have since noticed, though, is that my currently running (2.6.34)
> .config doesn't trigger it, whereas the one with some changes I made the
> other day does. Looks like I have a couple of ways in which to find out
> the cause :)
>
> Nigel
>
ahh.. I see.. yeah over here it was the same .config lots of commits
here and there, numerous recompiles of a same module that probably
triggered my error(stale files and such).. but if your hitting a .config
change then that's different..(hopefully you remember what you
changed...can be a bit daunting if going in and feeling generous and
such..(but then again maybe that's just me..)).
Justin P. Mattock
next prev parent reply other threads:[~2010-09-13 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 11:12 2.6.36-rc3 - Unable to build: "Error: input truncated" Nigel Cunningham
2010-09-12 16:27 ` Anca Emanuel
2010-09-12 17:34 ` Rafael J. Wysocki
2010-09-12 23:07 ` Nigel Cunningham
2010-09-13 3:11 ` Randy Dunlap
2010-09-13 5:01 ` Nigel Cunningham
2010-09-13 5:28 ` Justin P. Mattock
2010-09-13 6:09 ` Nigel Cunningham
2010-09-13 6:37 ` Justin P. Mattock [this message]
2010-09-13 6:52 ` Nigel Cunningham
2010-09-13 7:19 ` Justin P. Mattock
2010-09-14 22:52 ` Nigel Cunningham
2010-09-14 23:06 ` Justin P. Mattock
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=4C8DC6B9.3050701@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@tuxonice.net \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
/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