From: "Mat Kovach" <mek@mek.cc>
To: 9fans@9fans.net
Subject: Re: [9fans] Tcl 8.7a3 port to Plan 9
Date: Sun, 21 Jun 2020 08:54:06 -0400 [thread overview]
Message-ID: <bd9b73b9-ea17-4262-9ae3-8d094bdda234@www.fastmail.com> (raw)
In-Reply-To: <CAL6pNZ-D3rzUtWu7g25VUXFLfrE+AR-cPb_xwvb4+Ft4Qo0PFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
TCL 8.6.10 is the latest release. 8.7 is an alpha release, with some significant changes and is still a bit of a moving target, if memory serves me right.
The 8.6 version might be a better release tree to port.
--
Mat Kovach
mek@mek.cc
On Sun, Jun 21, 2020, at 06:27, Conor Williams wrote:
> hi 9Fans
>
> I'm porting the latest Tcl to Plan 9. Any help greatly appreciated.
> I have it down to about 15 'c' files with bugs. See Ps.
>
> Kind Regards
> Conor (Williams)
>
> Ps:
> o. stat64 issue
> o. VOID for OP dot
> o. sizeof issue
> o. addrinfo issue
> o stat64 again...
> o. not a member issue
> o.VOID OP issue again
>
> in 'c' code files such as:
> tclOOCall.c
> tclSelectNotfy.c
> tclUnixCompat.c
> tclUnixThrd.c
> etc...
> using the standard ape env with standard 'cc'....
>
>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions <https://9fans.topicbox.com/groups/9fans> + participants <https://9fans.topicbox.com/groups/9fans/members> + delivery options <https://9fans.topicbox.com/groups/9fans/subscription> Permalink <https://9fans.topicbox.com/groups/9fans/Te76ab77b2e389ee5-M76996e9a255195f7d0766c32>
[-- Attachment #2: Type: text/html, Size: 2488 bytes --]
next prev parent reply other threads:[~2020-06-21 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 10:27 Conor Williams
2020-06-21 12:54 ` Mat Kovach [this message]
2020-06-21 13:01 ` [9fans] " Conor Williams
2020-06-21 16:20 ` ori
2020-06-21 19:34 ori
[not found] <CAL6pNZ_=-_KOertAzg=zhdcsu+0xPL-=Fy3HnwA50funft3mdw@mail.gmail.com>
[not found] ` <5F3FC59B3F854BF644300D24C6D2BBFF@eigenstate.org>
[not found] ` <CAL6pNZ9eG116b7C3Z_7CFw57jU7tB36vLQkj6YDi5dF_OOYrXA@mail.gmail.com>
2020-06-21 19:47 ` Conor Williams
2020-06-21 19:50 ` ori
2020-06-21 20:41 ` Conor Williams
2020-06-21 21:24 ` Conor Williams
2020-06-21 22:40 ` Conor Williams
2020-06-21 23:01 ` ori
[not found] ` <CAL6pNZ9iHNNKYYvOFzGF6AweZXFKJA-b5hY3UXGaEOONHsyz6Q@mail.gmail.com>
2020-06-21 23:27 ` Fwd: " Conor Williams
2020-06-21 23:56 ` Conor Williams
2020-06-22 0:08 ` ori
2020-06-22 0:47 ` Conor Williams
2020-06-22 0:53 ` ori
2020-06-22 1:32 ` Conor Williams
2020-06-22 11:18 ` Conor Williams
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=bd9b73b9-ea17-4262-9ae3-8d094bdda234@www.fastmail.com \
--to=mek@mek.cc \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).