From: Jay K <jayk123@hotmail.com>
To: Mark Butt <mark@markwbutt.com>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
"me@larbob.org" <me@larbob.org>
Subject: Re: Libffi on Tru64?
Date: Sun, 18 Feb 2024 07:54:26 +0000 [thread overview]
Message-ID: <SN7PR14MB6081857ACEFEE09C4CA2ED6AE6522@SN7PR14MB6081.namprd14.prod.outlook.com> (raw)
In-Reply-To: <5EA164C8-1CE5-4EA6-B4C5-6FD656BAA07B@markwbutt.com>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Mark, I don't remember, but I think so maybe?
"me" should have some record..and I can try to look.
Sorry for the lack of information so far.
I know I had Python 2.x working, enough to run my build scripts.
I still haven't managed to port to Python 3.
The larger goal of modern gcc definitely didn't work out. 🙁
You can build old gcc, from native cc.
cmake was challenging.
Lots of stuff worked reasonably though. autoconf/automake really shown well imho.
git worked. Many things worked. Modula-3 worked. 🙂
These old systems are kinda fun. 🙂
I just wish they were a little easier to setup, and CI was run for the various projects.
I guess we should run Linux on these systems, NT, VMS, FreeBSD, etc. 🙂
* Jay
________________________________
From: Mark Butt <mark@markwbutt.com>
Sent: Thursday, February 15, 2024 4:43 AM
To: jayk123@hotmail.com <jayk123@hotmail.com>
Cc: libffi-discuss@sourceware.org <libffi-discuss@sourceware.org>; me@larbob.org <me@larbob.org>
Subject: Re: Libffi on Tru64?
Hello Jay,
I was wondering if you ever managed to figure out the error when trying to build libffi with gcc on Tru64.
#error "osf.S out of sync with ffi.h”
I currently have libffi-3.1 installed. I am trying to build Python 2.7.18 but many modules are failing to build and I am wondering if it might be because my libffi is too old… hence wanting to try a newer version.
Thanks!
-M
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2024-02-18 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 12:43 Mark Butt
2024-02-18 7:54 ` Jay K [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-04 22:54 Jay K
2021-07-05 11:42 ` Jay K
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=SN7PR14MB6081857ACEFEE09C4CA2ED6AE6522@SN7PR14MB6081.namprd14.prod.outlook.com \
--to=jayk123@hotmail.com \
--cc=libffi-discuss@sourceware.org \
--cc=mark@markwbutt.com \
--cc=me@larbob.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).