From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: gforth package
Date: Sat, 27 Apr 2019 05:10:00 -0000 [thread overview]
Message-ID: <CAJ1FpuPLqSaL+2yeS14DxjgSogmx8KS1eGqHJKH=Nyjfm7zx-g@mail.gmail.com> (raw)
In-Reply-To: <CAAr43iP0uP2QdPiJC5ixJHznZWAuAoMzze+-sUfzx9t9h2DgPQ@mail.gmail.com>
On Fri, 26 Apr 2019 at 21:59, Joel Rees <> wrote:
> Is anyone aware of the reason Gforth is no longer in packages?
gforth 0.7.0-2 was packaged for cygwin 1.7 about 10 years ago. It was
part of the cygport extras mirror, which contained over 2,500
un-official and un-maintained packages. This mirror was retired
several years ago due to, I think, lack of interest in the packages,
and possibly the lack of an official maintainer.
To quote the setup.hint file:
category: Interpreters
requires: libffi4 libgcc1 libltdl7 libtool
sdesc: "GNU Forth language interpreter"
ldesc: "Gforth is a fast and portable implementation of the ANS Forth
language. It works nicely with the Emacs editor, offers some nice
features such as input completion and history, backtraces, a
decompiler and a powerful locals facility, and it even has a
manual. Gforth combines traditional implementation techniques with
newer techniques for portability and performance: its inner
interpreter is direct threaded with several optimizations, but you can
also use a traditional-style indirect threaded interpreter."
The package for gforth 0.7.0-2 for cygwin 1.7 can be rebuilt using the
git repository, and upgraded to the current version of cygwin (3.0.6),
current versions of the dependencies, and then possibly to the latest
Gforth version (0.7.3). I have also seen indications that it could be
compiled using Mingw for Windows.
> Is it just a matter of lack of maintainer?
Would you like to volunteer? Otherwise, an existing or new maintainer
might be interested. Or you could build it yourself for your own use.
HTH
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-04-27 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 3:59 Joel Rees
2019-04-27 5:10 ` Doug Henderson [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='CAJ1FpuPLqSaL+2yeS14DxjgSogmx8KS1eGqHJKH=Nyjfm7zx-g@mail.gmail.com' \
--to=djndnbvg@gmail.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).