On Wed, Mar 20, 2019 at 6:41 PM Andrew Gierth
wrote:
> ... (Though the fact that we prefer gcc to cc in
> configure if both are found is a decision that should probably be
> revisited, given that the reasons for that preference are mostly
> consigned to the graveyard of commercial Unix variants.)
> "Karl" == Karl Denninger writes:
Karl> "cc" on FreeBSD is now (and has been for quite some time) clang:
Karl> If it will compile Postgres now it definitely would not when it
Karl> was first shifted to;
People have been building PG with clang since at least as far back as
clang 3.1, and
On 3/19/2019 21:12, Andrew Gierth wrote:
>> "Karl" == Karl Denninger writes:
> >> That's a configure line that has never worked on FreeBSD:
> >>
> >> % ./configure --with-openssl --with-perl
> >> [...]
> >> configure: error: readline header not found
> >> If you have libedit already ins
> "Karl" == Karl Denninger writes:
>> That's a configure line that has never worked on FreeBSD:
>>
>> % ./configure --with-openssl --with-perl
>> [...]
>> configure: error: readline header not found
>> If you have libedit already installed, see config.log for details on the
>> failure
On 3/19/2019 18:15, Andrew Gierth wrote:
>> "Karl" == Karl Denninger writes:
> Karl> That was on a bare, new grab of the source from your repository and a
> Karl> straight-up run of "./configure --with-openssl --with-perl", then
> "gmake".
>
> That's a configure line that has never worked
> "Karl" == Karl Denninger writes:
Karl> That was on a bare, new grab of the source from your repository and a
Karl> straight-up run of "./configure --with-openssl --with-perl", then
"gmake".
That's a configure line that has never worked on FreeBSD:
% ./configure --with-openssl --with-pe
On Wed, Mar 20, 2019 at 11:33 AM Karl Denninger wrote:
> Digging around I had the openssl-1.0.2r port on the system, which used to be
> necessary for some other stuff back before 12.x. I've removed it and it
> looks like that took care of it; for whatever reason configure was getting
> confuse
On 3/19/2019 17:12, Tom Lane wrote:
> Karl Denninger writes:
>> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
>> of the configure string.
> Hmmm ... I don't have that exact configuration handy to try, but
> we know that PG works against OpenSSL 1.1.1a in principle, and
>
> "Karl" == Karl Denninger writes:
Karl> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is
Karl> part of the configure string.
Nope, they work fine for me, running under 12-stable as of a couple of
weeks ago.
--
Andrew (irc:RhodiumToad)
On Wed, Mar 20, 2019 at 11:13 AM Tom Lane wrote:
> Karl Denninger writes:
> > Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
> > of the configure string.
>
> Hmmm ... I don't have that exact configuration handy to try, but
> we know that PG works against OpenSSL 1.1.1a in
Karl Denninger writes:
> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
> of the configure string.
Hmmm ... I don't have that exact configuration handy to try, but
we know that PG works against OpenSSL 1.1.1a in principle, and
it does work for me with FreeBSD 12.0-RC1 from
Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
of the configure string.
The issue appears to be that FreeBSD updated OpenSSL to OpenSSL
1.1.1a-freebsd 20 Nov 2018 where the 11.x release of FreeBSD (and
previous was on 1.0.x -- e.g. OpenSSL 1.0.2o-freebsd 27 Mar 2018)
The
12 matches
Mail list logo
