From: Norman Ramsey <norman@bellcore.com>
To: Werner Lemberg <A7621GAC@helios.edvz.univie.ac.at>
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: samx2 and sam 3/12/93
Date: Thu, 18 Aug 1994 13:46:24 -0400 [thread overview]
Message-ID: <199408181746.NAA19455@flaubert.bellcore.com> (raw)
In-Reply-To: Your message of "Thu, 18 Aug 1994 02:40:34 EDT." <94Aug18.014501edt.9063@ugw.utcc.utoronto.ca>
> Another question: Has anybody ported sam(term) to Linux? After some tries
> I succeeded in porting, but I'm not familiar with UNIX programming, and
> indeed I really don't know exactly what I've done :-)
I had no trouble compiling the current ATT&T sam distribution for
linux. I used the default makefiles with -DLINUX -ansi -D_POSIX_SOURCE.
I didn't have to touch and code.
next prev parent reply other threads:[~1994-08-18 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-08-18 6:40 Werner Lemberg
1994-08-18 17:46 ` Norman Ramsey [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-08-18 9:21 Pete Fenelon
1994-08-18 10:34 ` Markus Friedl (CIP 92)
1994-08-18 13:01 ` Mark C. Chu-Carroll
1994-08-17 14:43 hc05
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=199408181746.NAA19455@flaubert.bellcore.com \
--to=norman@bellcore.com \
--cc=A7621GAC@helios.edvz.univie.ac.at \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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;
as well as URLs for NNTP newsgroup(s).