pgsql: Re-defines SHA2 symbols so that they would not conflict with

From: momjian(at)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Re-defines SHA2 symbols so that they would not conflict with
Date: 2006-05-30 12:56:45
Message-ID: 20060530125645.D0B2D9FA5FB@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Re-defines SHA2 symbols so that they would not conflict with certain
versions of OpenSSL. If your OpenSSL does not contain SHA2, then there
should be no conflict. But ofcourse, if someone upgrades OpenSSL,
server starts crashing.

Backpatched to 8.1.X.

Marko Kreen

Modified Files:
--------------
pgsql/contrib/pgcrypto:
sha2.c (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sha2.c.diff?r1=1.5&r2=1.6)
sha2.h (r1.2 -> r1.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/sha2.h.diff?r1=1.2&r2=1.3)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-05-30 12:56:56 pgsql: Re-defines SHA2 symbols so that they would not conflict with
Previous Message Bruce Momjian 2006-05-30 12:43:33 pgsql: Add "inline" compile fix for MSVC/BCC: #define inline __inline