Re: Conflicting declarations for b64_encode etc. on Solaris 11.4 Beta
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres bugs <pgsql-bugs@postgresql.org>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: 2018-02-28T23:37:27Z
Lists: pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes: > Attached is an updated patch which does a bit more consistency work. I > have renamed the base64 functions with pg_base64_ as prefix in encode.c, > to avoid any conflicts in encode.c. pgp-armor.c also gets the same > treatment. There is no real point in renaming the other functions is > not necessary, and hex_encode/hex_decode are publicly available, so > renaming them would cause breakage for any callers of them in plugins. Pushed. > It is a bit sad that both pgcrypto and encode.c hold copies of base64 > functions. 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. regards, tom lane
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