Re: [blfs-dev] w3m and openssl

2018-02-20 Thread Pierre Labastie
On 20/02/2018 12:14, Richard Melville wrote: > On 20 February 2018 at 07:41, Pierre Labastie > wrote: > > > A more radical step away: archive w3m. Do we really need 3 text browsers > in > this book nowadays? > > I use w3m, but

Re: [blfs-dev] w3m and openssl

2018-02-20 Thread Richard Melville
On 20 February 2018 at 07:41, Pierre Labastie wrote: > > A more radical step away: archive w3m. Do we really need 3 text browsers in > this book nowadays? > > I use w3m, but I use libressl instead of openssl. This issue was flagged back in 2014 by the freebsd community,

Re: [blfs-dev] w3m and openssl

2018-02-19 Thread Pierre Labastie
On 20/02/2018 00:15, Ken Moffat wrote: > On Mon, Feb 19, 2018 at 11:39:09PM +0100, Pierre Labastie wrote: >> I usually do not build w3m, but since we are at tagging, and jhalfs included >> it as a dependency of something, I thought I would give it a try. Problem, I >> get the following

[blfs-dev] w3m and openssl

2018-02-19 Thread Pierre Labastie
I usually do not build w3m, but since we are at tagging, and jhalfs included it as a dependency of something, I thought I would give it a try. Problem, I get the following warning+error: - gcc -I. -I. -g -O2 -I./libwc -DHAVE_CONFIG_H -DAUXBIN_DIR=\"/usr/libexec/w3m\ "