my mistake -- it was in there on Apr 18 at least. i guess that's a little old
OpenSSL version 1.1.1b 26 Feb 2019 here
On Thu, Apr 25, 2019 at 6:28 PM Greg A. Woods wrote:
>
> At Thu, 25 Apr 2019 17:18:09 +0200, Martin Husemann
> wrote:
> Subject: Re: SSL_library_init not found in libssl in cu
On Fri, Apr 26, 2019 at 10:54:00AM +0530, Mayuresh wrote:
> Basically the thread has moved on to recognize 1. ssl version upgrade in
> current 2. squid3 being "old" and "not recommended" by upstream and 3.
> wip/squid4 being created and compiling fine with either version of ssl.
Withdraw the last
On Thu, Apr 25, 2019 at 10:05:12PM -0700, Greg A. Woods wrote:
> Not a bad idea to post the actual error messages, and maybe the command
> that failed too, and maybe even the code of the test file that failed! :-)
Basically the thread has moved on to recognize 1. ssl version upgrade in
current 2.
At Fri, 26 Apr 2019 08:38:30 +0530, Mayuresh wrote:
Subject: Re: SSL_library_init not found in libssl in current
>
> On Thu, Apr 25, 2019 at 10:47:15AM -0700, Greg A. Woods wrote:
> > Checking to see if the symbol mentioned in the message is present in the
> > library you think will be used for li
On Fri, Apr 26, 2019 at 07:53:56AM +0530, Mayuresh wrote:
> [Will have to sort out why my ssh keys aren't working. Wonder whether
> those would be deleted if not used for long!]
Everything ok. My keys of 2015 still work!
I have just initialized wip/squid4 and checked compilability on amd64.
Pushe
On Thu, Apr 25, 2019 at 10:47:15AM -0700, Greg A. Woods wrote:
> Checking to see if the symbol mentioned in the message is present in the
> library you think will be used for linking is of course a good idea, but
> you should also always examine the "config.log" file in the build
> directory to see
On Thu, Apr 25, 2019 at 11:28:08AM -0700, Greg A. Woods wrote:
> Of course as mentioned squid-3 is heading on to old and should soon be
> replaced by all users with squid-4, and especially pkgsrc should
> deprecate squid-3 and provide the latest squid-4 by default.
Just a heads up. I created wip/s
At Wed, 24 Apr 2019 09:25:58 +0200, Andreas Krey wrote:
Subject: Re: uniq on open streams
>
> On Tue, 23 Apr 2019 11:50:23 +, Greg A. Woods wrote:
> ...
> >
> > Thinking "Oh, so it should work on FreeBSD too...", I opened a window to
> > my recently installed FreeBSD-12.0 machine, and after re
At Thu, 25 Apr 2019 17:18:09 +0200, Martin Husemann wrote:
Subject: Re: SSL_library_init not found in libssl in current
>
> On Thu, Apr 25, 2019 at 08:34:05PM +0530, Mayuresh wrote:
> > On Thu, Apr 25, 2019 at 04:57:10PM +0200, Martin Husemann wrote:
> > > Note that the issue is the openssl versio
On 2019-04-25 11:08, co...@sdf.org wrote:
On Thu, Apr 25, 2019 at 04:43:24PM +0100, Roy Marples wrote:
On 24/04/2019 23:31, co...@sdf.org wrote:
The default Python version in pkgsrc is now 3.7, in preparation for
the coming end of life date of Python 2.7 (the previous default) at
the end of thi
At Thu, 25 Apr 2019 08:50:26 +0530, Mayuresh wrote:
Subject: SSL_library_init not found in libssl in current
>
> Got this error when trying to build squid:
>
> checking for SSL_library_init in -lssl... no
> configure: error: library 'ssl' is required for OpenSSL
Checking to see if the symbol ment
I have no objections at all. And yes, keeping 3.6 is also a good move; at least
from my little corner of the planet.
On 4/25/19, 12:02 PM, "Adam" wrote:
>> The default Python version in pkgsrc is now 3.7, in preparation for
>> the coming end of life date of Python 2.7 (the previous def
On Thu, Apr 25, 2019 at 04:57:10PM +0200, Martin Husemann wrote:
> Note that the issue is the openssl version, not the architecture (or
> am I missing something?)
I'd think so. Just that mail from JP on this thread says the symbol is
present on current amd64. I personally have only evbarm current
On Thu, 25 Apr 2019, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 04:57:10PM +0200, Martin Husemann wrote:
> > Note that the issue is the openssl version, not the architecture (or
> > am I missing something?)
>
> I'd think so. Just that mail from JP on this thread says the symbol is
> present on cur
On Thu, Apr 25, 2019 at 04:43:24PM +0100, Roy Marples wrote:
> On 24/04/2019 23:31, co...@sdf.org wrote:
> > The default Python version in pkgsrc is now 3.7, in preparation for
> > the coming end of life date of Python 2.7 (the previous default) at
> > the end of this year.
>
> Can we punt 3.4, 3.
On Thu, 25 Apr 2019 16:43:24 +0100, Roy Marples wrote:
> On 24/04/2019 23:31, coypu%sdf.org@localhost wrote:
> > The default Python version in pkgsrc is now 3.7, in preparation for
> > the coming end of life date of Python 2.7 (the previous default) at
> > the end of this year.
> Can we punt 3.
>> The default Python version in pkgsrc is now 3.7, in preparation for
>> the coming end of life date of Python 2.7 (the previous default) at
>> the end of this year.
>
> Can we punt 3.4, 3.5 and 3.6 then?
> 3.4 fails at least to build on netbsd-current due to an openssl conflict by
> the looks o
On 24/04/2019 23:31, co...@sdf.org wrote:
The default Python version in pkgsrc is now 3.7, in preparation for
the coming end of life date of Python 2.7 (the previous default) at
the end of this year.
Can we punt 3.4, 3.5 and 3.6 then?
3.4 fails at least to build on netbsd-current due to an open
On Thu, Apr 25, 2019 at 08:34:05PM +0530, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 04:57:10PM +0200, Martin Husemann wrote:
> > Note that the issue is the openssl version, not the architecture (or
> > am I missing something?)
>
> I'd think so. Just that mail from JP on this thread says the symbol
On Thu, Apr 25, 2019 at 09:52:33AM -0500, John D. Baker wrote:
> This issue is logged in PR pkg/53409, (and again in pkg/54132, closed
> as duplicate) but that's as far as it has gone. The port on which it
> was originally observed is sparc, but do feel free to log the issue seen
> on other ports
Note that the issue is the openssl version, not the architecture (or
am I missing something?)
Martin
On Thu, 25 Apr 2019 08:50:26 +0530, Mayuresh wrote:
> Got this error when trying to build squid:
> checking for SSL_library_init in -lssl... no
> configure: error: library 'ssl' is required for OpenSSL
> on a recently picked current snapshot for RPI2.
This issue is logged in PR pkg/53409, (an
On Thu, Apr 25, 2019 at 01:06:08PM +0530, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 09:28:38AM +0200, Martin Husemann wrote:
> > On Thu, Apr 25, 2019 at 12:54:46PM +0530, Mayuresh wrote:
> > > On Thu, Apr 25, 2019 at 12:50:45PM +0530, Mayuresh wrote:
> > > > # uname -m && nm /usr/lib/libssl.so | gr
On Thu, Apr 25, 2019 at 09:39:57AM +0200, Martin Husemann wrote:
> On Thu, Apr 25, 2019 at 01:06:08PM +0530, Mayuresh wrote:
> > configure scripts (squid3 for one, but may be there are others) look for
> > SSL_library_init. How to deal with that?
>
> They need to be adjusted for newer openssl vers
On Thu, Apr 25, 2019 at 12:54:46PM +0530, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 12:50:45PM +0530, Mayuresh wrote:
> > # uname -m && nm /usr/lib/libssl.so | grep SSL_library_init
> > amd64
> > 00022411 T SSL_library_init
> > #
> >
> >
> > # uname -m && nm /usr/lib/libssl.so | grep SSL_
On Thu, Apr 25, 2019 at 09:28:38AM +0200, Martin Husemann wrote:
> On Thu, Apr 25, 2019 at 12:54:46PM +0530, Mayuresh wrote:
> > On Thu, Apr 25, 2019 at 12:50:45PM +0530, Mayuresh wrote:
> > > # uname -m && nm /usr/lib/libssl.so | grep SSL_library_init
> > > amd64
> > > 00022411 T SSL_libra
On Thu, Apr 25, 2019 at 01:06:08PM +0530, Mayuresh wrote:
> configure scripts (squid3 for one, but may be there are others) look for
> SSL_library_init. How to deal with that?
They need to be adjusted for newer openssl versions.
Martin
On Thu, Apr 25, 2019 at 12:54:46PM +0530, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 12:50:45PM +0530, Mayuresh wrote:
> > # uname -m && nm /usr/lib/libssl.so | grep SSL_library_init
> > amd64
> > 00022411 T SSL_library_init
That is an old symbol, the function has been replaced by OPENSSL_i
On Thu, Apr 25, 2019 at 12:50:45PM +0530, Mayuresh wrote:
> # uname -m && nm /usr/lib/libssl.so | grep SSL_library_init
> amd64
> 00022411 T SSL_library_init
> #
>
>
> # uname -m && nm /usr/lib/libssl.so | grep SSL_library_init
> evbarm
> #
>
> Why this difference?
+port-arm
On Thu, Apr 25, 2019 at 09:03:47AM +0200, tlaro...@polynum.com wrote:
> The problem was that at installation time, the pkg used INSTALL_PROGRAM
> instead of INSTALL_DATA for installing libraries, and INSTALL_PROGRAM is
> set to install with the "-s" that is the stripped flag.
Basically:
# uname -
On Thu, Apr 25, 2019 at 12:21:21PM +0530, Mayuresh wrote:
> On Thu, Apr 25, 2019 at 12:47:15AM +, JP wrote:
> > SSL_library_init is in there on current amd64.
> >
> > "library 'ssl' is required" -- is libssl on there at all?
>
> configure errors can be misleading. The library is there but nm
31 matches
Mail list logo
