From: Dan Kegel <dank@kegel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?
Date: Mon, 20 Sep 2004 23:03:07 -0700 [thread overview]
Message-ID: <414FC41B.7080102@kegel.com> (raw)
I'm trying to verify that I can build toolchains and compile
and link kernels for a large set of CPU types using simple kernel config files.
I'm also somewhat foolishly trying to do all this with gcc-3.4.2.
So any problems I run into are a bit hard to pin down to
compiler, kernel, or user error, since this is mostly new territory for me.
Here's another issue.
When I build 2.6.8 for sparc32, using the config file
http://kegel.com/crosstool/crosstool-0.28-rc36/sparc.config ,
I get a link error:
/opt/crosstool/sparc-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/bin/sparc-unknown-linux-gnu-ld -m elf32_sparc -T arch/sparc/kernel/vmlinux.lds.s arch/sparc/kernel/head.o arch/sparc/kernel/init_task.o init/built-in.o --start-group
usr/built-in.o arch/sparc/kernel/built-in.o arch/sparc/mm/built-in.o arch/sparc/math-emu/built-in.o kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o lib/lib.a
arch/sparc/prom/lib.a arch/sparc/lib/lib.a lib/built-in.o arch/sparc/prom/built-in.o arch/sparc/lib/built-in.o drivers/built-in.o sound/built-in.o net/built-in.o --end-group .tmp_kallsyms2.o arch/sparc/boot/btfix.o -o
arch/sparc/boot/image
/opt/crosstool/sparc-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/bin/sparc-unknown-linux-gnu-ld: cannot open linker script file arch/sparc/kernel/vmlinux.lds.s: No such file or directory
make[1]: *** [arch/sparc/boot/image] Error 1
make: *** [image] Error 2
Anyone seen this?
Thanks,
Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next reply other threads:[~2004-09-21 6:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 6:03 Dan Kegel [this message]
2004-09-21 10:50 ` 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)? Sam Ravnborg
2004-09-21 10:57 ` William Lee Irwin III
2004-09-22 5:40 ` Dan Kegel
2004-09-24 20:19 ` Sam Ravnborg
2004-10-07 5:57 ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Dan Kegel
2004-10-16 21:00 ` Sam Ravnborg
2004-10-16 19:06 ` Russell King
2004-10-16 21:24 ` Sam Ravnborg
2004-10-16 19:40 ` Russell King
2004-10-16 19:04 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-16 22:04 ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Sam Ravnborg
2004-10-17 16:57 ` Herbert Poetzl
2004-10-17 16:42 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-17 18:29 ` Herbert Poetzl
2004-10-17 17:47 ` Dan Kegel
2004-10-17 19:06 ` Herbert Poetzl
2004-10-17 19:32 ` Dan Kegel
2004-10-31 21:10 ` Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?) Sam Ravnborg
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=414FC41B.7080102@kegel.com \
--to=dank@kegel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.