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

From momjian@postgresql.org (Bruce Momjian)
Subject pgsql: Re-defines SHA2 symbols so that they would not conflict with
Date
Msg-id 20060530125645.D0B2D9FA5FB@postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add "inline" compile fix for MSVC/BCC: #define inline __inline
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Re-defines SHA2 symbols so that they would not conflict with