public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: Linux-8086@vger.kernel.org
Subject: Re: Hi everybody
Date: Wed, 9 Oct 2002 20:50:12 -0400	[thread overview]
Message-ID: <000801c26ff7$040f1de0$4f73580c@who> (raw)
In-Reply-To: CF3E4F0EA4465B44931D2D900A289CBB3C994A@mercurio.pito.pioneerinvest.it

Hello from Gregg C Levine
Um, have you checked the links pages at http://elks.sourceforge.net It
should have that locations listed. It happens I am in a similar fix for a
different project.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "BODRATO Stefano" <Stefano.Bodrato@pioneerinvest.it>
To: <Linux-8086@vger.kernel.org>
Sent: Monday, October 07, 2002 5:23 AM
Subject: Hi everybody


> Hi all,
> just signed, still haven't got a single mail but.. I'd like to ask a
couple of things:
>
> I'm trying to compile ELKS with my Win2000 box w/CygWin.  (and, of course
a hand-compiled "bcc" rel. 0.16.3)
> The compile session goes fine up to the boot/config modules, which are
written in assembly.
>
> Now the question:  it seems to me that the assembler I'm using doesn't
recognize the "C" style include definitions.  I could go on by specifying
the EQUs insted of the #IFDEFs, but.. I'm messing up the souces !!
>
> Suggestions ?  Where can I pick the updated AS86 source, if any ?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2002-10-10  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  9:23 Hi everybody BODRATO Stefano
2002-10-10  0:50 ` Gregg C Levine [this message]
2002-10-10  8:15 ` Paul Nasrat

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='000801c26ff7$040f1de0$4f73580c@who' \
    --to=obiwanthejediknight@worldnet.att.net \
    --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