From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] Libpng and Zlib updates on the ports tree
Date: Thu, 13 Feb 2020 08:19:11 +0900 [thread overview]
Message-ID: <3F681F7C3CE15192499C89ECE55776A2@hera.eonet.ne.jp> (raw)
In-Reply-To: D125A0109F8BBC611458B0A94E36E43E@eigenstate.org
> Right now, the ape/lib/z takes the code from gs,
> but if we're updating from the outside world, it'd
> probably be a good idea to invert that relationship.
I suppose you did it for compiling netsurf.
I did it to cheating the zlib, and compiled libpng for ape.
However, both of jpeg and png images are not shown
on the current netsurf.
Kenji
PS: did you check its update will not suffer anything else?
next reply other threads:[~2020-02-12 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 23:19 kokamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 7:16 kokamoto
2020-02-14 1:33 kokamoto
2020-02-14 6:37 ` jamos
2020-02-14 0:29 kokamoto
2020-02-12 20:51 Lucas Francesco
2020-02-12 21:01 ` [9front] " ori
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=3F681F7C3CE15192499C89ECE55776A2@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.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).