From: "Frank B. Pound" <fpound@fallschurch.esys.com>
To: Jeff Harrell <jharrell@ti.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: SGI, MIPS, Hardhat Linux question...
Date: Mon, 08 Nov 1999 12:59:59 -0500 [thread overview]
Message-ID: <38270F9F.BA484C3C@fallschurch.esys.com> (raw)
In-Reply-To: 19991102.21303700@jharrell_dt.
I got the same message when trying to compile the ftape driver on an x86
box.
It's been a long time since I tried it but I do distinctly remember
tracing it to
what you were talking about.
"It seems to have problems with the #include <asm/current.h>."
I'm not sure if your problem is related to mine but could be.
It happened after a kernel upgrade, using RH.
Frank
--
_______________________________________________________________
Frank B. Pound Phone: 703-560-5000 ext. 4008
Raytheon Systems Company Strategic Systems Division
E-mail: fpound@fallschurch.esys.com
Web: http://www.raytheon.com/rsc/c3/c300.htm
_______________________________________________________________
prev parent reply other threads:[~1999-11-08 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 21:30 SGI, MIPS, Hardhat Linux question Jeff Harrell
1999-11-02 23:42 ` Juan J. Sierralta P.
1999-11-02 23:53 ` Ulf Carlsson
1999-11-08 17:59 ` Frank B. Pound [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=38270F9F.BA484C3C@fallschurch.esys.com \
--to=fpound@fallschurch.esys.com \
--cc=jharrell@ti.com \
--cc=linux@cthulhu.engr.sgi.com \
/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