From: Mike Timmons <mike_timmons@trimble.com>
To: linuxppc-dev@ozlabs.org
Subject: toolchain for building linux-2.6.27.8 or 2.6.28.1 ...
Date: Thu, 29 Jan 2009 13:52:00 -0600 [thread overview]
Message-ID: <498208E0.7000707@trimble.com> (raw)
I wrote a couple days ago needing advice on USB wi fi. I made some
progress but then I hit a snag loading the USB wi fi adapter firmware.
Jon schooled me on the firmware topic (thanks Jon), and advised me to
select the following Kconfig options
Kconfig
Device drivers
generic driver options
user space firmware support
check - include in-kernel firmware blobs in kernel binary
My 2.6.24 kernel didn't offer these options, and I also suspected that
since 2.6.24 some progress on the ralink drivers I need has been made I
figured I'd just try a new kernel build and try to get my
ralink-equipped Linksys WUSB54GC to work.
Trouble:
-I was using Ltib Toolchain (gcc-3.4.3-glibc-2.3.6 (for 603e)) to build
my 2.6.24 kernel.
-It looks like somewhere after 2.6.24 this toolchain stopped
successfully compiling the kernel.
So,
-I used crosstool and built 4.1.0 and 4.1.1 toolchains. Both produce the
following error:
OBJCOPY arch/powerpc/kernel/vdso32/vdso32.so
objcopy: Unable to recognise the format of the input file
`arch/powerpc/kernel/vdso32/vdso32.so.dbg'
make[3]: *** [arch/powerpc/kernel/vdso32/vdso32.so] Error 1
make[2]: *** [arch/powerpc/kernel/vdso32] Error 2
Questions:
1) if I want to cross-compile a kernel later than 2.6.24 to hopefully
get better WAN device support (and clearer options for fw loading),
which kernel should I try, and which toolchain?
the ltib repository does not appear to have a toolchain newer than
gcc-3.4.3-glibc-2.3.6 (for 603e)
Admissions, disclaimers, etc
1) I'm using the same ltib script I have used for the 2.6.24 build with
toolchain gcc-3.4.3-glibc-2.3.6 (for 603e).
I'm simply modifying the kernel spec file to use 2.6.28.1 (and specifyin
a custom toolchain).
I've also tried to compile 2.6.27.8. I get the same error.
I think I'm slipping into version compatibility hell at this point.
Please throw me a rope if you can by way of advice if you can.
Thanks!
-Mike
next reply other threads:[~2009-01-29 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 19:52 Mike Timmons [this message]
2009-01-29 20:16 ` toolchain for building linux-2.6.27.8 or 2.6.28.1 Bruno Monteiro
2009-01-29 20:40 ` Grant Erickson
2009-01-30 21:39 ` toolchain for building linux-2.6.27.8 or 2.6.28.1 AND USB wi fi SUCCESS Mike Timmons
2009-01-30 23:08 ` toolchain for building linux-2.6.27.8 or 2.6.28.1 Robert Schwebel
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=498208E0.7000707@trimble.com \
--to=mike_timmons@trimble.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).