From: Romano <unobe@cpan.org>
To: 9front@9front.org,ori@eigenstate.org,weitzeug@gmail.com
Subject: Re: [9front] perl for plan9?
Date: Fri, 26 Jun 2020 00:38:10 +0000 [thread overview]
Message-ID: <57BF54C6-7F9E-4F28-9FC9-C391C394B6F7@cpan.org> (raw)
In-Reply-To: <724E65043287CA7C8C6D78DF92D8CFB0@eigenstate.org>
I've resolved the problem with the patch applying cleanly to blead. There are two commits that I have requested to be included upstream, see https://github.com/Perl/Perl5/pull/17891 . Apllying those to commits, then doing the following should get perl built on i386*:
ape/patch -p 1 < plan9/9front.patch; cd plan9; chmod +x fndvers; rc setup.rc; cd ..; mk perl
Then running: perl - Ilib -E 'say q{hello}'
should work
*Note this is from memory. I'm not at a terminal right now so cannot check. I had sent instructions to Ori_B in May over IRC but forgot to store them before things in RealLife came up. I hope to be able to confirm by the end of the month/beginning of July.
On June 25, 2020 1:39:13 PM UTC, ori@eigenstate.org wrote:
>> I have i386 built and now just working on the tests. The patches
>> are here: https://blog.fallglow.com/misc/ . The latest blead patch
>> doesn't apply cleanly at the moment, unfortunately, and is the most
>> far along in terms of hammering out issues; I just haven't had time
>to
>> clean things up since the latest stable release when some blead
>> updates also occurred and broke the patch in yhe plan9/ directory.
>> I'll try to clean it up and get it going tomorrow night with
>> instructions on how to build. Note that it doesn't build on other
>> archs right now.
>
>Well, it builds with amd64, but has the same crash in the regex
>compilation that I've been trying to track down on-and-off for
>the last while.
>
>(If anyone else wants to look at it, Romano's patches are the
>place to start)
next prev parent reply other threads:[~2020-06-26 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 0:37 kokamoto
2020-06-25 6:18 ` [9front] " kokamoto
2020-06-25 6:30 ` Tanami Muller
2020-06-25 7:07 ` Jens Staal
2020-06-25 7:12 ` Romano
2020-06-25 13:39 ` ori
2020-06-26 0:38 ` Romano [this message]
2020-08-21 4:33 ` kokamoto
2020-02-25 4:29 kokamoto
2020-02-26 20:51 ` jamos
2020-02-27 0:14 kokamoto
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=57BF54C6-7F9E-4F28-9FC9-C391C394B6F7@cpan.org \
--to=unobe@cpan.org \
--cc=9front@9front.org \
--cc=ori@eigenstate.org \
--cc=weitzeug@gmail.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 NNTP newsgroup(s).