From: Kyle Nusbaum <knusbaum@sdf.org>
To: ori@eigenstate.org, jamos@oboj.net, 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Fri, 17 Apr 2020 20:09:38 -0500 [thread overview]
Message-ID: <E8469F2C-EBB9-415A-863E-BDB4E385A6CA@sdf.org> (raw)
In-Reply-To: <F27EAE1FB23382A8E2B77807BCA75B5F@eigenstate.org>
Thanks, Ori.
I nuked everything and rebuilt. Had to delete all the netsurf Lin directories and re-fetch too.
It seems weird to me that syntax errors arise from old compilations, not linker errors. Are we doing code generation?
Anyway, I have it building now. Thanks!
On April 15, 2020 3:24:39 PM CDT, ori@eigenstate.org wrote:
>> 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
>
>Yeah. That just means that we changed some of the types, but the
>code using them hasn't been recompiled. The commit that changed
>them is probably abeb350f0cb8 or 026c1d87dd3e The answer to that
>error is almost always:
>
> cd /sys/src
> mk clean
> mk all
>
>to rebuild the libraries.
-- Kyle
next prev parent reply other threads:[~2020-04-18 1:09 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
2020-04-15 20:24 ` ori
2020-04-18 1:09 ` Kyle Nusbaum [this message]
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=E8469F2C-EBB9-415A-863E-BDB4E385A6CA@sdf.org \
--to=knusbaum@sdf.org \
--cc=9front@9front.org \
--cc=jamos@oboj.net \
--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).