Re: Conflicting declarations for b64_encode etc. on Solaris 11.4 Beta
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Postgres bugs <pgsql-bugs@postgresql.org>, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: 2018-03-01T00:55:10Z
Lists: pgsql-bugs
On Wed, Feb 28, 2018 at 06:37:27PM -0500, Tom Lane wrote: > And on top of that, there's src/common/base64.c with again almost the > same functionality. But refactoring to fix that would be a bit invasive > and not something to back-patch. I think what you did here is appropriate > as a minimal portability fix. Maybe later somebody will look into > removing the duplication, as a HEAD-only improvement. Thanks for pushing the patch. base64.c ignores some whitespace handling, which is in line with what the RFCs of SCRAM expect when doing conversion of the data exchanged in the protocol so that's a bit more different than the other implementations. Maybe that's worth refactoring, still I am not completely convinced that we have much to gain from such a move either. -- Michael
Commits
-
Rename base64 routines to avoid conflict with Solaris built-in functions.
- d07f79a9cc7b 9.4.18 landed
- aac6286d8fd1 10.4 landed
- 679df2b8d8a5 9.5.13 landed
- 43e949086638 11.0 landed
- 11e7700e584e 9.6.9 landed
- 10102c91ea13 9.3.23 landed