public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, rmk-lkml@arm.linux.org.uk
Subject: Re: 2.6.8-rc2-mm1
Date: Sun, 1 Aug 2004 16:57:29 -0700	[thread overview]
Message-ID: <20040801235729.GZ2334@holomorphy.com> (raw)
In-Reply-To: <20040801211146.GA7954@mars.ravnborg.org>

[-- Attachment #1: brief message --]
[-- Type: text/plain, Size: 898 bytes --]

On Sun, Aug 01, 2004 at 11:11:46PM +0200, Sam Ravnborg wrote:
> Took a look at this and atm compiling a sparc tool-chain to try it out.
> What about moving the check added by rmk to kallsyms.c?
> This would remove the extra pass on vmlinux which is for no use for
> most people anyway. On the other hand an error could go unpassed
> because we (for now) do not do the kallsyms stuff if not configured in.
> We could make the kallsyms run independent on the configuration, but
> only link in the symbols if required to do so.
> This would also allow us to have architecture specific final-linking
> rules in one place if sparc needs special rules.
> Today kallsyms already knows about 'SDA_BASE*_' only valid for ppc.
> wli - can you post the output of a failing sparc compile?

The only part that fails is the ldchk part (unique to -mm), which is
just happening prematurely. Here's a log.


-- wli

[-- Attachment #2: sparc.compile.log.1.gz --]
[-- Type: application/octet-stream, Size: 19302 bytes --]

  reply	other threads:[~2004-08-01 23:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28  9:04 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 16:36 ` 2.6.8-rc2-mm1 Jesse Barnes
2004-07-28 17:08 ` 2.6.8-rc2-mm1 (compile stats) John Cherry
2004-07-28 19:37 ` 2.6.8-rc2-mm1 Peter Osterlund
2004-07-28 22:24 ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-28 22:44   ` 2.6.8-rc2-mm1 viro
2004-07-28 23:24     ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-28 23:34       ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-29  0:08         ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-29  6:42           ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-29 19:35       ` 2.6.8-rc2-mm1 Michael Hunold
2004-07-29 21:02         ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 22:49 ` 2.6.8-rc2-mm1 Adam Kropelin
2004-07-28 23:20   ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 23:13 ` 2.6.8-rc2-mm1 Paul Jackson
2004-07-29 14:36 ` 2.6.8-rc2-mm1 Adrian Bunk
2004-07-29 19:36   ` 2.6.8-rc2-mm1 David Woodhouse
2004-07-29 14:41 ` 2.6.8-rc2-mm1: NTFS compile error with gcc 2.95 Adrian Bunk
2004-07-29 15:54   ` Jan-Benedict Glaw
2004-07-29 20:42     ` [patch] " Adrian Bunk
     [not found]       ` <Pine.LNX.4.60.0407292249120.25661@hermes-1.csi.cam.ac.uk>
2004-07-29 23:18         ` Adrian Bunk
2004-07-29 21:27 ` 2.6.8-rc2-mm1: DVB: "errno" undefined Adrian Bunk
2004-07-29 22:44   ` Kenneth Aafløy
2004-07-29 23:24     ` Adrian Bunk
2004-07-30 14:30       ` Arnd Bergmann
2004-07-31 10:09 ` 2.6.8-rc2-mm1 breaks PPPoE for me (was: 2.6.8-rc2-mm1) Matthias Andree
2004-07-31 16:39 ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 18:47   ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-31 19:54     ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 20:09       ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 20:21         ` 2.6.8-rc2-mm1 Andrew Morton
2004-08-01  4:21           ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-08-01 11:16           ` 2.6.8-rc2-mm1 Ingo Molnar
2004-08-01 11:05     ` 2.6.8-rc2-mm1 Ingo Molnar
2004-08-01  2:36 ` 2.6.8-rc2-mm1 William Lee Irwin III
2004-08-01  8:05   ` 2.6.8-rc2-mm1 Andrew Morton
2004-08-01 12:33     ` 2.6.8-rc2-mm1 William Lee Irwin III
2004-08-01 21:11       ` 2.6.8-rc2-mm1 Sam Ravnborg
2004-08-01 23:57         ` William Lee Irwin III [this message]
2004-08-03 20:46           ` 2.6.8-rc2-mm1 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=20040801235729.GZ2334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk-lkml@arm.linux.org.uk \
    --cc=sam@ravnborg.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