From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: segaloco <segaloco@protonmail.com>, tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu, mj@broniarz.net, COFF <coff@tuhs.org>
Subject: [TUHS] Re: [COFF] Re: Help needed with some old VAX Machines (moved from TUHS)
Date: Thu, 23 Feb 2023 08:37:11 +0100 [thread overview]
Message-ID: <20230223073711.5ztisknhpol3lzp2@lug-owl.de> (raw)
In-Reply-To: <GBYhoReLSzhhpYhr48yr23-0tFMMXeDiqN82gE6LBKAc9l_N5i9xtqC3yFrRsR44i90qgafXn9ZXXc1udgKJc2ScDfY2l7PJN_9R2YY_JAo=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hi!
On Wed, 2023-02-22 19:41:35 +0000, segaloco via TUHS <tuhs@tuhs.org> wrote:
> COFF transfer, TUHS Bcc'd to know where this thread went.
Not yet subscribed there, sorry. But on the way!
> If you're feeling particularly adventurous, NetBSD still supports VAX in some manner: http://wiki.netbsd.org/ports/vax/
I regularly build NetBSD HEAD (on NetBSD amd64 and also as a
cross-build from Linux amd64). Sometimes (rarely) I start it on
regular desktop VAX hardware, and always in SIMH. Works well!
> YMMV, but I've had some success with NetBSD on some pretty oddball stuff. As the old saying goes, "Of course it runs NetBSD". You might be able to find some old VMS stuff for them as well, but I wouldn't know where to point you other than bitsavers. There's some other archival site out there with a bunch of old DEC stuff but I can never seem to find it when I search for it, only by accident. Best of luck!
Many pkgsrc packages are missing due to compiler bugs in the GCC
version that NetBSD ships. However, Maciej recently did some great
work on GCC's VAX backend and that will fix most of the issues. Right
now, it usually helps to have CFLAGS+=-O0 to not run into issues.
MfG, JBG
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2023-02-23 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:41 segaloco via TUHS
2023-02-23 7:37 ` Jan-Benedict Glaw [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=20230223073711.5ztisknhpol3lzp2@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=coff@tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
--cc=mj@broniarz.net \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).