From: jamos@oboj.net
To: 9front@9front.org
Cc: knusbaum@sdf.org, ori@eigenstate.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Wed, 15 Apr 2020 23:05:56 +0300 [thread overview]
Message-ID: <165169b76b03f24b94de290997633534@oboj.net> (raw)
In-Reply-To: <D22D0F25-7EB7-4C8A-A389-38865BEB06C8@sdf.org>
I think something happened in 9front. Netsurf compiles well on a "fairly
recent" install here. So I decided to do a clean install of 7508 "No
Thinkpad" plus a sysupdate.
It seems that neither git9, nor netsurf, compiles on this latest
configuration. For git9 I get "incompatible type signatures" (in lib9p I
think, not completely sure). In netsurf I get errors in duktape.c:1155
that it doesn't recognise the type duk_int64_t.
So I did another clean install of 7508 this time without making a
sysupdate. Then git9 compiles, but some other type-related problems
arise in netsurf, as the current source assumes some changes to 9front
that happened since 7508.
To answer your question, the installation instructions for netsurf
hasn't changed. Only that one might need to invoke a 'mk 9res' in
nsport/netsurf before 'mk install', but that is purely to prepare files
for run-time, and doesn't affect compiling.
/Jonas
On 2020-04-15 00:53, Kyle Nusbaum wrote:
> I'm getting all kinds of compile errors with a clean checkout of
> nsport. I'm running an up-to-date 9front and following the instructions
> in the readme.
>
> Do we have instructions on how to compile netsurf now?
next prev parent reply other threads:[~2020-04-15 20:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 5:04 kokamoto
2020-04-14 21:53 ` Kyle Nusbaum
2020-04-15 20:05 ` jamos [this message]
2020-04-15 20:24 ` ori
2020-04-18 1:09 ` Kyle Nusbaum
2020-04-18 1:19 ` ori
2020-04-18 17:11 ` Eli Cohen
2020-04-18 17:15 ` telephil9
2020-04-18 17:17 ` ori
-- strict thread matches above, loose matches on Subject: below --
2020-04-13 23:46 kokamoto
2020-04-07 4:25 kokamoto
2020-04-06 5:48 kokamoto
2020-04-13 12:44 ` jamos
2020-04-05 4:52 kokamoto
2020-04-05 4:41 kokamoto
2020-03-22 23:47 kokamoto
2020-03-22 2:19 kokamoto
2020-03-21 3:24 kokamoto
2020-03-22 20:27 ` jamos
2020-03-22 20:54 ` ori
2020-03-22 20:54 ` ori
2020-03-20 5:49 kokamoto
2020-03-20 16:10 ` Kyle Nusbaum
2020-03-20 16:15 ` ori
2020-03-20 17:12 ` telephil9
2020-03-20 17:40 ` Jens Staal
2020-03-20 18:54 ` jamos
2020-03-21 5:00 ` Jens Staal
2020-03-21 12:24 ` Ethan Gardener
2020-03-20 22:07 ` Kyle Nusbaum
2020-03-17 11:16 kokamoto
2020-03-17 17:42 ` jamos
2020-03-15 9:42 kokamoto
2020-03-15 11:06 ` Steve Simon
2020-03-15 11:38 ` Jens Staal
2020-03-15 13:50 ` jamos
2020-03-14 1:49 kokamoto
2020-03-14 2:09 ` ori
2020-03-14 1:19 kokamoto
2020-03-14 1:34 ` ori
2020-03-13 4:33 kokamoto
2020-03-13 4:58 ` ori
2020-03-12 5:28 kokamoto
2020-03-12 2:20 kokamoto
2020-03-12 2:43 ` ori
2020-03-11 23:59 kokamoto
2020-03-11 10:27 kokamoto
2020-03-11 6:36 kokamoto
2020-03-11 9:29 ` [9front] " jamos
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=165169b76b03f24b94de290997633534@oboj.net \
--to=jamos@oboj.net \
--cc=9front@9front.org \
--cc=knusbaum@sdf.org \
--cc=ori@eigenstate.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 NNTP newsgroup(s).