From: andrew@walrond.org
To: linux-kernel@vger.kernel.org
Cc: dwmw2@infradead.org
Subject: make headers_install headers problem on sparc64
Date: Wed, 18 Oct 2006 22:37:13 +0000 [thread overview]
Message-ID: <20061018223713.GD9350@pelagius.h-e-r-e-s-y.com> (raw)
Hi david, lkml.
I found a message where you said
"If you have problems with the exported headers (other
than that some userspace abuses headers which it shouldn't), then
_shout_. Please don't just let them go unreported."
So,
Using headers exported from vanilla linux 2.6.18.1 and compiling the
elftoaout part of the debian sparc-utils package, I get some breakage
here:
In file included from /usr/include/asm/elf.h:5,
from /usr/include/linux/elf.h:7,
from elftoaout.c:24:
due to tlb_type, cheetah et al being undefined in this part of
asm-sparc64/elf.h:
bash-3.1# tail -n30 /pkg/linux/include/asm-sparc64/elf.h
/* This yields a mask that user programs can use to figure out what
instruction set this cpu supports. */
/* On Ultra, we support all of the v8 capabilities. */
static __inline__ unsigned int sparc64_elf_hwcap(void)
{
unsigned int cap = (HWCAP_SPARC_FLUSH | HWCAP_SPARC_STBAR |
HWCAP_SPARC_SWAP | HWCAP_SPARC_MULDIV |
HWCAP_SPARC_V9);
if (tlb_type == cheetah || tlb_type == cheetah_plus)
cap |= HWCAP_SPARC_ULTRA3;
else if (tlb_type == hypervisor)
cap |= HWCAP_SPARC_BLKINIT;
return cap;
}
#define ELF_HWCAP sparc64_elf_hwcap();
/* 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. */
#define ELF_PLATFORM (NULL)
#endif /* !(__ASM_SPARC64_ELF_H) */
Hope this is useful
Andrew Walrond
next reply other threads:[~2006-10-18 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 22:37 andrew [this message]
2006-10-19 7:50 ` David Woodhouse
2006-10-19 9:03 ` andrew
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=20061018223713.GD9350@pelagius.h-e-r-e-s-y.com \
--to=andrew@walrond.org \
--cc=dwmw2@infradead.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®