Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Takeshi Hakamada <hakamada@nsg.sgi.com>
To: tsbogend@alpha.franken.de
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Compiling kernel on HardHat
Date: Fri, 07 Aug 1998 09:33:47 +0900 (JST)	[thread overview]
Message-ID: <19980807093347Z.hakamada@nsg.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 6 Aug 1998 21:25:51 +0200" <19980806212551.61171@alpha.franken.de>

Hi Thomas,

Thanks for your help. I'll try to remove #include in setup.c and build
kernel tonight.

Cheers,
Takeshi

From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Message-ID: <19980806212551.61171@alpha.franken.de>
> On Thu, Aug 06, 1998 at 04:13:25PM +0900, Takeshi Hakamada wrote:
> > I tried to compile kernel on HardHat using RPM kernel(2.1.100) source,
> > I can't build kernel due to following error.
> > In arch/mips/sgi/kernel/setup.c, 
> > 
> > setup.c:18: asm/vector.h: No such file or directory
> 
> that's already fixed in the CVS repository. You just have to remove
> the #include in setup.c.
> 
> > Error message shows that I need to have include/asm/vector.h.
> > How can I get vector.h? Do I have to get latest kernel source from
> > ftp.linux.sgi.com?
> 
> As this should be the only change, you don't need to.
> 
> Thomas.
> 
> -- 
> See, you not only have to be a good coder to create a system like Linux,
> you have to be a sneaky bastard too ;-)
>                    [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

  reply	other threads:[~1998-08-07  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-06  7:13 Compiling kernel on HardHat Takeshi Hakamada
1998-08-06 19:25 ` Thomas Bogendoerfer
1998-08-07  0:33   ` Takeshi Hakamada [this message]
1998-08-10  8:26   ` Takeshi Hakamada

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=19980807093347Z.hakamada@nsg.sgi.com \
    --to=hakamada@nsg.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=tsbogend@alpha.franken.de \
    /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