mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reg Clemens <reg@dwf.com>
To: linux-kernel@vger.kernel.org
Subject: Problems building 2.6.31.6 with 64bit Fedora-11
Date: Thu, 19 Nov 2009 22:01:28 -0700	[thread overview]
Message-ID: <200911200501.nAK51SYc019858@deneb.dwf.com> (raw)

OK, Im new to Fedora-11, and this will be my first 64bit
kernel build, so this is probably going to be something
stupid, but I dont see it.

The top of my .config file reads:

---

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.31.6-PPS
# Thu Nov 19 20:08:27 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y

--- 

So it seems that I am really doing a 64bit build, but the problems
start with the first cc/ld, viz

---

[root@deneb linux-2.6.31.6-PPS]# make -j3 mod
ules ; make -j3 bzImage
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  HOSTCC  scripts/kallsyms
  CC      scripts/mod/empty.o
  HOSTCC  scripts/selinux/mdp/mdp
nm: scripts/mod/empty.o: File format not recognized
objdump: scripts/mod/empty.o: File format not recognized
  HOSTCC  scripts/mod/mk_elfconfig
  HOSTCC  scripts/pnmtologo
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTCC  scripts/conmakehash
  HOSTLD  scripts/mod/modpost
  CC      kernel/bounds.s
  GEN     include/linux/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/asm/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  CC [M]  arch/x86/crypto/crc32c-intel.o
  CC [M]  arch/x86/kernel/test_nx.o
  CC [M]  arch/x86/kernel/microcode_core.o
nm: arch/x86/crypto/crc32c-intel.o: File format not recognized
nm: arch/x86/kernel/test_nx.o: File format not recognized
objdump: arch/x86/kernel/test_nx.o: File format not recognized
objdump: arch/x86/crypto/crc32c-intel.o: File format not recognized
  CC [M]  arch/x86/kvm/svm.o
  CC [M]  arch/x86/kvm/vmx.o
nm: arch/x86/kernel/microcode_core.o: File format not recognized

---

So whats going on here?
Why the file-format-not-recognized ???

-- 
                                        Reg.Clemens
                                        reg@dwf.com



             reply	other threads:[~2009-11-20  5:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20  5:01 Reg Clemens [this message]
2009-11-20  6:13 ` andrew hendry
2009-11-20 17:51 Reg Clemens

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=200911200501.nAK51SYc019858@deneb.dwf.com \
    --to=reg@dwf.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

all inboxes | Powered by JetHome®