public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel@vger.kernel.org
Subject: Compile failure 'Bad ELF' ??
Date: Thu, 03 Mar 2011 15:00:24 -0800	[thread overview]
Message-ID: <4D701D88.2030709@candelatech.com> (raw)

I just merged in wireless-testing 2.6.38-rc7 and I'm getting
a strange build error.  This tree has a bunch of my own hacks
in it too...

[greearb@build-32 wireless-testing-ct.p4s]$ make bzImage
make -C /home/greearb/git/linux.wireless-testing-ct O=/home/greearb/kernel/2.6/wireless-testing-ct.p4s/. bzImage
   GEN     /home/greearb/kernel/2.6/wireless-testing-ct.p4s/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
   Using /home/greearb/git/linux.wireless-testing-ct as source for kernel
   GEN     /home/greearb/kernel/2.6/wireless-testing-ct.p4s/Makefile
   CHK     include/linux/version.h
   CHK     include/generated/utsrelease.h
   CALL    /home/greearb/git/linux.wireless-testing-ct/scripts/checksyscalls.sh
   MKELF   scripts/mod/elfconfig.h
Error: not ELF
make[4]: *** [scripts/mod/elfconfig.h] Error 1
make[3]: *** [scripts/mod] Error 2
make[2]: *** [scripts] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2


It appears to have something to do with how things are configured,
as I was able to build a more stripped-down version for the C3 kernel
from the same source tree.

Any ideas on what sort of thing can cause this?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2011-03-03 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03 23:00 Ben Greear [this message]
2011-03-03 23:19 ` Compile failure 'Bad ELF' ?? Ben Greear

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=4D701D88.2030709@candelatech.com \
    --to=greearb@candelatech.com \
    --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