From: "David S. Miller" <davem@redhat.com>
To: kai-germaschewski@uiowa.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild news
Date: Mon, 07 Oct 2002 07:24:26 -0700 (PDT) [thread overview]
Message-ID: <20021007.072426.93474936.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210070919330.14294-100000@chaos.physics.uiowa.edu>
From: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Date: Mon, 7 Oct 2002 09:22:51 -0500 (CDT)
I'll take a look on how to do sparc's btfixup in a similar way, without
messing up the common code too much. BTW, the combination kallsyms +
btfixup, does that need a particular ordering?
No, the kallsyms object file would not need to be seen by
the btfixup.o generator. It could therefore be done validly
as:
1) build .tmp_vmlinux
2) build btfixup.o
3) build kallsyms
4) link final vmlinux image
The order of #2 and #3 could be transposed and that would be fine too.
next prev parent reply other threads:[~2002-10-07 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 2:10 Kai Germaschewski
2002-10-07 8:08 ` David S. Miller
2002-10-07 14:22 ` Kai Germaschewski
2002-10-07 14:24 ` David S. Miller [this message]
2002-10-07 14:35 ` Kai Germaschewski
2002-10-08 9:39 ` Keith Owens
[not found] <mailman.1034070360.25457.linux-kernel2news@redhat.com>
2002-10-08 14:42 ` Pete Zaitcev
2002-10-08 20:11 ` David S. Miller
2002-10-08 20:25 ` Pete Zaitcev
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=20021007.072426.93474936.davem@redhat.com \
--to=davem@redhat.com \
--cc=kai-germaschewski@uiowa.edu \
--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®