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: Re: Problems building 2.6.31.6 with 64bit Fedora-11
Date: Fri, 20 Nov 2009 10:51:21 -0700	[thread overview]
Message-ID: <200911201751.nAKHpLpk012212@deneb.dwf.com> (raw)

I sent this message to the list yesterday, but it never appeared,
Probably a side effect of my new Fedora-11 install.  In any case
here is another try. The question is about a failue of a build
of linux 2.6.31.6 on a 64bit Pentium 4.

---

> What arch are you building on?

a 64bit Pentium 4.
> 
> What does 'file' say about the bad object files?
>

A File shows:

reg@deneb kernel]$ file *.o
microcode.o:       ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not 
stripped
microcode_amd.o:   ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not 
stripped
microcode_core.o:  ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not 
stripped
microcode_intel.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not 
stripped
test_nx.o:         ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not 
stripped

while nm shows

[reg@deneb kernel]$ nm *.o
nm: microcode.o: File format not recognized
nm: microcode_amd.o: File format not recognized
nm: microcode_core.o: File format not recognized
nm: microcode_intel.o: File format not recognized
nm: test_nx.o: File format not recognized

Almost looks like the wrong version of nm, but Im sure someone
out there will have a better idea.


-- 
                                        Reg.Clemens
                                        reg@dwf.com



             reply	other threads:[~2009-11-20 17:51 UTC|newest]

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

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=200911201751.nAKHpLpk012212@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®