From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: offsets.h and 32 -> 64 bit cross-compiling
Date: Wed, 11 Feb 2004 06:17:53 +0000 [thread overview]
Message-ID: <6299.1076480273@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <401DA58C.8070105@kegel.com>
On Tue, 10 Feb 2004 21:59:58 -0800,
Dan Kegel <dank@kegel.com> wrote:
>David Mosberger wrote:
>> Umh, you're using the wrong compiler. You must use the IA-64
>> cross-compiler for print_offsets.c. That's the entire point of
>> generating offsets.h at build-time: to ensure the definitions match
>> your (IA-64) compiler (and kernel-configuration).
>
>But how do I do that when I'm building the cross-compiler?
>As far as I can tell, it looks like offsets.h is needed to
>compile the cross-compiler. Perhaps I can compile the bootstrap
>compiler with a dummy version of offsets.h?
Which compiler file needs asm/offsets.h? I doubt that any user space
code should be using that file, it is probably being included by
mistake.
QAD workaround, copy /usr/include/asm/offsets.h from an ia64 system to
/usr/include/asm.
prev parent reply other threads:[~2004-02-11 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 1:19 offsets.h and 32 -> 64 bit cross-compiling Dan Kegel
2004-02-10 21:16 ` David Mosberger
2004-02-11 5:59 ` Dan Kegel
2004-02-11 6:17 ` Keith Owens [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=6299.1076480273@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-ia64@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