From: andrew@walrond.org
To: linux-kernel@vger.kernel.org
Subject: Re: make headers_install headers problem on sparc64
Date: Thu, 19 Oct 2006 09:03:11 +0000 [thread overview]
Message-ID: <20061019090311.GA17882@pelagius.h-e-r-e-s-y.com> (raw)
In-Reply-To: <1161244222.3376.470.camel@pmac.infradead.org>
On Thu, Oct 19, 2006 at 08:50:22AM +0100, David Woodhouse wrote:
>
> Hm, yes. There's still a lot of crap being exposed there that we really
> don't need to be showing. Try this entirely untested patch...
>
> The sparc64 version could do with something similar, too.
>
I'm on sparc64 (pure 64bit) so I can't test your patch. For reference,
I used this (not as smart as yours) patch:
diff -Naur linux-2.6.18.1/include/asm-sparc64/elf.h linux-2.6.18.1-fix/include/asm-sparc64/elf.h
--- linux-2.6.18.1/include/asm-sparc64/elf.h 2006-09-20 03:42:06.000000000 +0000
+++ linux-2.6.18.1-fix/include/asm-sparc64/elf.h 2006-10-19 08:57:11.000000000 +0000
@@ -142,6 +142,7 @@
#define ELF_ET_DYN_BASE 0x0000010000000000UL
#endif
+#ifdef __KERNEL__
/* This yields a mask that user programs can use to figure out what
instruction set this cpu supports. */
@@ -163,6 +164,8 @@
#define ELF_HWCAP sparc64_elf_hwcap();
+#endif
+
/* This yields a string that ld.so will use to load implementation
specific libraries for optimization. This is more specific in
intent than poking at uname or /proc/cpuinfo. */
Andrew Walrond
next prev parent reply other threads:[~2006-10-19 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 22:37 andrew
2006-10-19 7:50 ` David Woodhouse
2006-10-19 9:03 ` andrew [this message]
2006-10-19 10:54 ` andrew
2006-10-19 11:10 ` andrew
2006-10-19 11:34 ` David Woodhouse
2006-10-19 11:37 ` andrew
2006-10-19 11:43 ` David Woodhouse
2006-12-30 10:38 ` Mike Frysinger
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=20061019090311.GA17882@pelagius.h-e-r-e-s-y.com \
--to=andrew@walrond.org \
--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®