shadowsocks-client: fix fortify source compatibility
authorJo-Philipp Wich <redacted>
Thu, 25 Jun 2015 15:56:29 +0000 (17:56 +0200)
committerJo-Philipp Wich <redacted>
Thu, 25 Jun 2015 16:02:37 +0000 (18:02 +0200)
commita89c0cadcfa9260cce039772b1a7d0c4744a63c1
tree742b448b31306b72781221144a1a372f72a06c5c
parent07c0677b7b96cc69109b8dda9cebd01e62aa2f26
shadowsocks-client: fix fortify source compatibility

The shadowsocks source uses the name `encrypt` which is already reserved by
the `unistd.h` header. Rename the local `encrypt` and `decrypt` functions to
`crypto_encrypt` and `crypto_decrypt` in order to prevent clashes with the
standard headers.

Fixes the following build error oberserved on the buildbot:

    In file included from client.c:19:0:
    crypto.h:18:5: error: conflicting types for 'encrypt'
     int encrypt(int sockfd, struct link *ln);
         ^
    In file included from .../staging_dir/toolchain-mipsel_mips32_gcc-4.8-linaro_musl-1.1.10/include/fortify/unistd.h:20:0,
                     from client.c:12:
    .../staging_dir/toolchain-mipsel_mips32_gcc-4.8-linaro_musl-1.1.10/include/unistd.h:145:6: note: previous declaration of 'encrypt' was here
     void encrypt(char *, int);
          ^
    make[3]: *** [sslocal] Error 1

Signed-off-by: Jo-Philipp Wich <redacted>
net/shadowsocks-client/patches/100-fortify-source-compat.patch [new file with mode: 0644]
git clone https://git.99rst.org/PROJECT