From: "John E. Malmberg" <wb8tyw@qsl.net>
To: Richard Henderson <rth@redhat.com>, libffi-discuss@sourceware.org
Subject: Re: Trying to port libffi to OpenVMS.
Date: Fri, 13 Feb 2015 23:47:00 -0000 [thread overview]
Message-ID: <54DE8D61.803@qsl.net> (raw)
In-Reply-To: <54DE0D25.8020300@redhat.com>
On 2/13/2015 8:41 AM, Richard Henderson wrote:
> On 02/13/2015 06:00 AM, John E. Malmberg wrote:
>> 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've never seen those patches but...
Not sure if I got them via E-mail from someone else, or from his site.
His site is not responding at this time.
The readme says that they include HP-UX/ia64 and VMS/Alpha and VMS/ia64.
What I have appears to be bunch of concatenated unified diffs. I can
gzip it and forward it to anyone that is interested, uncompressed it is
126 KB.
>> 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 know that the ABI for vms is significantly different from unix.
> I'd be surprised if the patches were small.
I think VMS and Tru64 share a calling standard on Alpha, but I am not
sure. VMS on Itanium uses ELF binaries and calling standard with a few
extensions to ELF.
In any case, on VMS, the "int lib$callg(void **args, int (*func)())"
hides all that though.
> I don't know that there's a wiki, per se...
That is what the text at that web site says. It actually implies that
it is posted on a WIKI.
What I should have done is read the libffi online manual instead of
trying just to understand what Philippe did.
The use of the lib$callg() routine means I should not need any assembly
language code at all. Probably almost the same source for all three
current VMS harware platforms.
Thanks for the reply.
Regards,
-John
next prev parent reply other threads:[~2015-02-13 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 13:59 John E. Malmberg
2015-02-13 14:41 ` Richard Henderson
2015-02-13 23:47 ` John E. Malmberg [this message]
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=54DE8D61.803@qsl.net \
--to=wb8tyw@qsl.net \
--cc=libffi-discuss@sourceware.org \
--cc=rth@redhat.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).