From: Jay <jay.krell@cornell.edu>
To: "<jhi@iki.fi>" <jhi@iki.fi>
Cc: "<libffi-discuss@sourceware.org>" <libffi-discuss@sourceware.org>
Subject: Re: [PATCH] libffi 3.2.1 on Tru64 5.1B
Date: Thu, 12 Mar 2015 02:07:00 -0000 [thread overview]
Message-ID: <1C1E0842-1D59-4CB4-A982-892243B8C8ED@gmail.com> (raw)
In-Reply-To: <5500EED1.8000405@iki.fi>
Fwiw, I had those systems up & running fairly recently -- getting newer (4.x) gcc working is quite possible. OSF /1 I got through gcc make check. I didn't necessarily build libffi. Fun stuff. :)
That is, don't be dismayed by your gcc 2.9/3.3.
- Jay
On Mar 11, 2015, at 6:41 PM, Jarkko Hietaniemi <jhi@iki.fi> wrote:
> The attached patch makes libffi compile on Tru64 5.1B. Without it,
> the compilation stops on this in src/alpha/osf.S:
>
> #error "osf.S out of sync with ffi.h"
>
> Since "make check" requires dejagnu but I don't have it, I tried
> the "puts" example from http://www.atmark-techno.com/~yashi/libffi.html, and it worked.
>
> (It would be good to have some trivial test suite that works
> without dejagnu...)
>
> Compiled with the ancient gcc 2.9 the system has.
>
> The patch simply removes the check of FFI_TYPE_LAST being 14 or FFI_TYPE_POINTER. Not necessarily the most correct thing to do,
> but hey.
>
> I have also access to an IRIX 6.5 box, but there the situation
> seems to be more dire. (gcc 3.3, FWIW.)
>
>
>
>
>
>
> <libffi-tru64.pat>
prev parent reply other threads:[~2015-03-12 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 1:41 Jarkko Hietaniemi
2015-03-12 2:07 ` Jay [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=1C1E0842-1D59-4CB4-A982-892243B8C8ED@gmail.com \
--to=jay.krell@cornell.edu \
--cc=jhi@iki.fi \
--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).