From: Gianni Tedesco <gianni@ecsc.co.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kai Germaschewski <kai-germaschewski@uiowa.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] kksymoops-2.5.38-C9
Date: 02 Oct 2002 12:16:05 +0100 [thread overview]
Message-ID: <1033557365.27033.75.camel@lemsip> (raw)
In-Reply-To: <Pine.LNX.4.44.0209261536020.18328-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Thu, 2002-09-26 at 15:01, Ingo Molnar wrote:
> --- linux/Makefile.orig Thu Sep 26 15:26:53 2002
> +++ linux/Makefile Thu Sep 26 15:27:16 2002
> @@ -138,6 +138,7 @@
> MAKEFILES = $(TOPDIR)/.config
> GENKSYMS = /sbin/genksyms
> DEPMOD = /sbin/depmod
> +KALLSYMS = /sbin/kallsyms
> PERL = perl
> MODFLAGS = -DMODULE
> CFLAGS_MODULE = $(MODFLAGS)
> @@ -291,32 +292,64 @@
> vmlinux-objs := $(HEAD) $(INIT) $(CORE_FILES) $(LIBS) $(DRIVERS) $(NETWORKS)
Ingo, this breaks cross compiles because kallsyms expects a host
executable:
$ /sbin/kallsyms .tmp_vmlinux > .tmp_kallsyms.o
.tmp_vmlinux: ELF file .tmp_vmlinux not for this architecture
You can't even do $(CROSS_COMPILE)kallsyms because that isn't part of
most peoples toolchains. (and /sbin might not be in the $PATH).
I'm not sure what kallsyms does *exactly* but it sounds like the same
functionality can be had from objcopy...
--
// Gianni Tedesco (gianni at ecsc dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-10-02 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 14:01 [patch] kksymoops-2.5.38-C9 Ingo Molnar
2002-09-26 14:36 ` Kai Germaschewski
2002-10-02 11:16 ` Gianni Tedesco [this message]
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=1033557365.27033.75.camel@lemsip \
--to=gianni@ecsc.co.uk \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/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).