public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: ELKS port of Adventure - help needed :)
Date: Thu, 12 Dec 2002 08:18:07 +0000	[thread overview]
Message-ID: <20021212081807.GE10355@raq465.uk2net.com> (raw)
In-Reply-To: <20021212073945.GC10355@raq465.uk2net.com>

On Thu, Dec 12, 2002 at 07:39:46AM +0000, Paul Nasrat wrote:
 
> Two possible fixes - there is a new dev86 out which string.c has
> changed in  (0.16.10).  I'm going to test this out later when I get into
> work.  Thanks Robert :)

I can confirm adventure *works* with bcc 0.16.10 which was released on the
5th of December.

This is a bleeding edge bcc with pre-processor, etc.  But other than a
complaint about:

advent.h:265: warning: Unexpected text following preprocessor command

But it compiles and runs :) 

At least I get to play a game at the lan party now...

Paul

  reply	other threads:[~2002-12-12  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 13:07 ELKS port of Adventure - help needed :) Paul Nasrat
2002-12-11  8:19 ` Phil Goembel
2002-12-11 21:27   ` Richard Wallman
2002-12-11 22:22     ` Richard Wallman
2002-12-11 22:46       ` Richard Wallman
2002-12-11 22:51       ` Paul Nasrat
2002-12-11 23:59       ` Phil Goembel
2002-12-12  7:39         ` Paul Nasrat
2002-12-12  8:18           ` Paul Nasrat [this message]
2002-12-12 19:11         ` Adventure - the answer to what went wrong? Richard Wallman
2002-12-12 20:21           ` Harry Kalogirou
2002-12-12 20:52           ` Alan Cox
2002-12-12 20:27             ` Dan Olson
2002-12-12 20:29               ` Harry Kalogirou
2002-12-12 20:41                 ` Dan Olson
2002-12-12 21:15               ` Alan Cox

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=20021212081807.GE10355@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --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