public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@tuxonice.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "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: Mon, 13 Sep 2010 15:01:37 +1000	[thread overview]
Message-ID: <4C8DB031.6050008@tuxonice.net> (raw)
In-Reply-To: <20100912201152.a4ada04a.randy.dunlap@oracle.com>

Hi.

On 13/09/10 13:11, Randy Dunlap wrote:
> On Mon, 13 Sep 2010 09:07:45 +1000 Nigel Cunningham wrote:
>
>> Hi.
>>
>> On 13/09/10 03:34, Rafael J. Wysocki wrote:
>>> On Sunday, September 12, 2010, Nigel Cunningham wrote:
>>>> Hi all.
>>>>
>>>> I'm unable to compile the latest kernel and git bisect isn't helping:
>>>
>>> Did you try to save .config, run "make distclean" and restore .config?
>>
>> I hadn't tried that, but had done git reset --hard and make clean
>> menuconfig bzImage. Trying distclean doesn't help, I'm afraid. Perhaps I
>> should attach my .config. I'm running a 32 bit kernel/distro on a 64 bit
>> machine if that makes any difference.
>
>
> Try to strace scripts/mod/mk_elfconfig to see why it is producing
> that error message:
>
>     scripts/mod/mk_elfconfig<  scripts/mod/empty.o>  scripts/mod/elfconfig.h
> Error: input truncated
>
> I guess that the empty.o file is not in the expected format.

Yeah. It's zero bytes long.

> Who owns that stuff, anyway?

I figured the kbuild guys did, which is why I cc'd them.

> You should probably post the empty.o file so that interested parties can
> try to debug the problem.
>
> I built the kernel just fine with the .config file that you posted.

Okay. So it's probably something specific to Ubuntu Lucid then. I'll see 
if I can find the time to do a bisection by hand.

Nigel

  reply	other threads:[~2010-09-13  5:01 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 [this message]
2010-09-13  5:28         ` Justin P. Mattock
2010-09-13  6:09           ` Nigel Cunningham
2010-09-13  6:37             ` Justin P. Mattock
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=4C8DB031.6050008@tuxonice.net \
    --to=nigel@tuxonice.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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