From: "John E. Malmberg" <wb8tyw@qsl.net>
To: libffi-discuss@sourceware.org
Subject: Trying to port libffi to OpenVMS.
Date: Fri, 13 Feb 2015 13:59:00 -0000 [thread overview]
Message-ID: <54DE0378.8040609@qsl.net> (raw)
Hello,
I am one of the current developers of the GNV and VMS-PORTS Sourceforge
projects. References below:
The build of cPython from the mercurial repository on VMS now
effectively requires a port of libffi in order to complete.
I was able to apply Philippe Vouters patches for Libffi 3.0.9 to libffi
3.1 and get the code building. I was unable to get the tests to run
under GNV though.
I am now trying to build master from a git checkout, and have gotten
lost with the changes to src/alpha/ffi.c since then, so I am looking for
some guidance on how to get libffi from master building.
I have been unable to locate the WIKI for libffi. The link at github
just gives a 404, not found.
On VMS, the compilers do not support the "asm" directive.
I have e-mailed Philippe, but so far I have not received a response from
him.
Regards,
-John
References:
https://sourceforge.net/projects/gnv/
https://sourceforge.net/projects/vms-ports/
GNV is the GNU on VMS tool kit and tries to simulate a Linux build
environment on VMS.
VMS-PORTS is for other programs ported to OpenVMS such as cPython 3.5a.
VMS has free hobby licenses for non-commercial hobby use, or free
software developers Alliance One licenses for commercial software
companies. Free VAX and Alpha emulators are also available.
next reply other threads:[~2015-02-13 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 13:59 John E. Malmberg [this message]
2015-02-13 14:41 ` Richard Henderson
2015-02-13 23:47 ` John E. Malmberg
2015-02-16 17:13 ` Richard Henderson
2015-02-16 19:41 ` John E. Malmberg
2015-02-17 13:35 ` John E. Malmberg
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=54DE0378.8040609@qsl.net \
--to=wb8tyw@qsl.net \
--cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).