Re: Debian Sid broke Perl

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de
Subject: Re: Debian Sid broke Perl
Date: 2020-06-07 01:02:59
Message-ID: 1706745.1591491779@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> writes:
> I meant that PostgreSQL's ./configure must get the same answers, and it does
> (should have posted this instead of what I did post):

Ah, that looks good. I suppose that we can generally expect that the
ldflags output will look like "-L/some/path -lperl ...", and whether
or not the libperl in that directory is .so or .a is not going to affect
things at this level. Furthermore, given that this output is specifically
defined to be flags to be used to *embed* libperl, it's the distro's own
fault if they end up with libperl statically linked into other packages;
they should not be putting a .a-style library there.

So I'm content to fix this by removing the check for useshrplib.
Any objections?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-06-07 01:35:41 Re: Debian Sid broke Perl
Previous Message Noah Misch 2020-06-07 00:46:01 Re: Debian Sid broke Perl