From: Phil Goembel <phil-goembel@wi.rr.com>
To: Paul Nasrat <pauln@truemesh.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: ELKS port of Adventure - help needed :)
Date: 11 Dec 2002 02:19:30 -0600 [thread overview]
Message-ID: <1039594769.1511.27.camel@Castle.goembel> (raw)
In-Reply-To: <20021210130728.GA12336@raq465.uk2net.com>
For the heck of it, and for nostalgia's sake,
I edited the Makefile to compile and run on
my Linux PC (changed CC=mcc to CC=gcc, got
rid of -S switch).
It runs fine on my PC - no problems parsing
commands. I'm guessing, without having looked
at the code, that this is not a source code
problem.
Phil
--------------
phil@castle:advent$ diff -u Makefile.old Makefile
--- Makefile.old Mon Sep 22 09:46:59 1997
+++ Makefile Wed Dec 11 01:48:14 2002
@@ -2,17 +2,17 @@
# Where to put the adventure text files, and the binary executable.
# Need the trailing "/"s.
-TEXTDIR = /usr/lib/advent/
+TEXTDIR = ./
# Flags you may want to add to CFLAGS:
# -DHAS_STDC=0 or 1 We have Standard C. Default=1 iff __STDC__ is
nonzero.
#
# On Minix, use '-m' in CFLAGS and '-i' in LDFLAGS.
-CC = mcc
+CC = /usr/bin/gcc
CFLAGS = -D_POSIX_SOURCE
LDFLAGS =
-GCC = /usr/local/bin/gcc
+GCC = /usr/bin/gcc
OBJS = advent.o database.o english.o initial.o itverb.o score.o\
travel.o turn.o utility.o verb.o vocab.o
@@ -22,7 +22,8 @@
all: $(DAT) advent
advent: $(OBJS)
- $(CC) $(LDFLAGS) -o advent -S 16kw $(OBJS)
+# $(CC) $(LDFLAGS) -o advent -S 16kw $(OBJS)
+ $(CC) $(LDFLAGS) -o advent $(OBJS)
setup: setup.c advent.h
$(GCC) -o setup setup.c
phil@castle:advent$ make
/usr/bin/gcc -o setup setup.c
./setup
Processing file advent1.txt completed
Processing file advent2.txt completed
Processing file advent3.txt completed
Processing file advent4.txt completed
/usr/bin/gcc -c -D_POSIX_SOURCE -DTEXTDIR='"./"' advent.c
/usr/bin/gcc -D_POSIX_SOURCE -c -o database.o database.c
...
phil@castle:advent$ ./advent
<Generic Adventure -- Version:7.0, July 1994>
Welcome to ADVENTURE!
...
Would you like instructions?
> no
You are standing at the end of a road before a small brick building.
Around you is a forest. A small stream flows out of the building and
down a gully.
> north
You are in open forest, with a deep valley to one side. Not far
is a large billboard.
> read
The billboard reads:
"Visit Beautiful Colossal Cave. Open Year Around. Fun for
the entire family, or at least for those who survive."
Below the headline is an impossibly complicated map showing how
to find Colossal Cave. Not that it matters, because all the
directions are written in Elvish.
> ...
next prev parent reply other threads:[~2002-12-11 8:19 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 [this message]
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
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=1039594769.1511.27.camel@Castle.goembel \
--to=phil-goembel@wi.rr.com \
--cc=linux-8086@vger.kernel.org \
--cc=pauln@truemesh.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