From: | Jacob Champion <pchampion(at)vmware(dot)com> |
---|---|
To: | "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "m(dot)kulagin(at)postgrespro(dot)ru" <m(dot)kulagin(at)postgrespro(dot)ru> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Pull general SASL framework out of SCRAM |
Date: | 2021-07-13 22:41:01 |
Message-ID: | bf4c861d6331af782af1ec1639aaa00f18703504.camel@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2021-07-13 at 19:31 +0900, Michael Paquier wrote:
> On Tue, Jul 13, 2021 at 12:41:27PM +0300, Mikhail Kulagin wrote:
> > I got an error while building one of the extensions.
> > /home/mkulagin/pg-install/postgresql-master/include/internal/libpq-int.h:44:10: fatal error: fe-auth-sasl.h: No such file or directory
> > #include "fe-auth-sasl.h"
> > ^~~~~~~~~~~~~~~~
>
> Right. I overlooked the fact that libpq-int.h is installed.
Thanks for catching that Mikhail.
> > I think the new fe-auth-sasl.h file should be installed too.
> > Correction proposal in the attached file (but I'm not sure that fix
> > of Install.pm is correct).
>
> That looks correct to me. I'll check that tomorrow.
Looks right to me too. I'm currently rebuilding my Windows dev
environment so I haven't been able to double-check that piece of it.
Just to make sure -- do we want to export the fe-auth-sasl.h header as
opposed to forward-declaring the pg_fe_sasl_mech struct? Is the use
case for libpq-int.h just "here, have at the internals, and if you
break it then it's on you"?
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-07-13 23:00:38 | Re: proposal: possibility to read dumped table's name from file |
Previous Message | Stephen Frost | 2021-07-13 22:32:17 | Re: proposal: possibility to read dumped table's name from file |