public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
To: linux-8086@vger.kernel.org
Subject: Re: Riddles in the dark
Date: Wed, 14 Jul 2004 11:38:00 -0300	[thread overview]
Message-ID: <20040714143800.GE2830@duckman.distro.conectiva> (raw)
In-Reply-To: <20040713004957.54461.qmail@web51309.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]


On Mon, Jul 12, 2004 at 05:49:57PM -0700, Tommy McCabe wrote:
> ps.c can't compile because of these errors:
> 
<lots of errors>
> 
> Note that the file linuxmt/sc doesn't exist- I assume
> it to be linxumt/sched.h. The compiler thinks seg_t is
> a variable name but it's a variable type. Is ps.c
> itself, I see this: int read_task(fd, off, ds,
> task_table). What the heck is this? A function
> declaration? An array? It looked as if it should have
> a semicolon put after it, but then ps.c returned these
> errors:
> 

Hi, Tommy,

Did you copied the current kernel include files on the bcc include path?

You are supposed to do that, before building elkscmd, elksnet and others.

BTW, we need to include this on the documentation, somewhere. I don't know
if the web page warns the user about that.


<more errors>
> 
> And back at linuxmt/sched.h, it ends with a #endif
> which isn't preceded by a #indef! What gives?

linuxmt/sched.h here looks like:

===
#ifndef LX86_LINUXMT_SCHED_H
#define LX86_LINUXMT_SCHED_H

<lots of content>

#endif
===

The '%' key on VIM here says that the #if* are correctly closed.

-- 
Eduardo

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-07-14 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  0:49 Riddles in the dark Tommy McCabe
2004-07-14 14:38 ` Eduardo Pereira Habkost [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=20040714143800.GE2830@duckman.distro.conectiva \
    --to=ehabkost@conectiva.com.br \
    --cc=linux-8086@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