All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: maximilian attems <max@stro.at>,
	linux-mips@linux-mips.org, klibc@zytor.com
Subject: Re: [klibc] klibc kernelheaders build failure on mips/mipsel
Date: Mon, 30 Jul 2007 13:05:57 +0100	[thread overview]
Message-ID: <20070730120557.GE11436@linux-mips.org> (raw)
In-Reply-To: <46AC997B.2030706@zytor.com>

On Sun, Jul 29, 2007 at 06:43:23AM -0700, H. Peter Anvin wrote:

> >  In file included from usr/klibc/arch/mips/crt0.S:11:
> >  usr/include/arch/mips/machine/asm.h:8:24: error: asm/regdef.h: No such
> >  file or directory
> >  usr/include/arch/mips/machine/asm.h:9:21: error: asm/asm.h: No such file
> >  or directory
> >
> >  i'm not sure if you want to export both headers in the make
> >  kernelheaders target or if it is the fault of klibc to assume
> >  that those are available?
> >
> 
> If I remember correctly (sorry, I'm on the road at the moment), those 
> files should be exportable.  They wouldn't be all that hard to replicate 
> in klibc, though.

<asm/asm.h> would need to add __KERNEL__ wrappers around the CONFIG_* bits.
In addition you probably want to have <asm/fpregdef.h> exported.  With a
few changes you should be able to get away without using <asm/sgidefs.h>.

  Ralf

  parent reply	other threads:[~2007-07-30 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29  9:52 klibc kernelheaders build failure on mips/mipsel maximilian attems
2007-07-29 13:43 ` [klibc] " H. Peter Anvin
2007-07-29 14:44   ` Christoph Hellwig
2007-07-30 12:05   ` Ralf Baechle [this message]
2007-07-30 12:12     ` Ralf Baechle
2007-07-30 12:41       ` H. Peter Anvin

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=20070730120557.GE11436@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=linux-mips@linux-mips.org \
    --cc=max@stro.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.