From: tony@reef.cs.jcu.edu.au
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: Sam on alphas?
Date: Wed, 12 Jul 1995 19:12:50 -0400 [thread overview]
Message-ID: <9507122312.AA26419@reef.cs.jcu.edu.au> (raw)
In-Reply-To: Your message of "Tue, 11 Jul 95 03:55:09 -0400." <9507110755.AA32380@reef.cs.jcu.edu.au>
Hi,
I guess it's bad form to answer my own mail, but oh well...
> I've just started using sam on a DEC Alpha running OSF1/3.0. I
> grabbed the latest distrib from AT&T but unfortunately it crashes
> periodically. Before I attempt to track down the problem, is anyone
> else using it successfully on this platform?
It turns out that the compile on OSF1/3.0 has a different set of
predefined processor symbols. Hence the line in sam/sam.h that says:
#ifdef __alpha__
should be
#if defined(__alpha__) || defined(__alpha)
With this change made I haven't had a crash.
> Also, can someone point me to the Sam extension patches? I lost my
> record of the site.
Still looking for these...
Cheers,
Tony
prev parent reply other threads:[~1995-07-12 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-07-11 7:55 tony
1995-07-12 23:12 ` tony [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=9507122312.AA26419@reef.cs.jcu.edu.au \
--to=tony@reef.cs.jcu.edu.au \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
--cc=tony@cs.jcu.edu.au \
/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).