Skip to content
This repository has been archived by the owner on Apr 21, 2019. It is now read-only.

Errors while installing #8

Open
manjush3v opened this issue Feb 3, 2015 · 1 comment
Open

Errors while installing #8

manjush3v opened this issue Feb 3, 2015 · 1 comment

Comments

@manjush3v
Copy link

The following errors are generated while installing in mac 10.10.1 OS X
In file included from seccure/libseccure.c:32:
seccure/libseccure.h:20:9: error: 'LIBSECFURE_H' is used as a header guard
here, followed by #define of a different macro [-Werror,-Wheader-guard]

ifndef LIBSECFURE_H

    ^~~~~~~~~~~~~~

seccure/libseccure.h:21:9: note: 'LIBSECCURE_H' is defined here; did you mean
'LIBSECFURE_H'?

define LIBSECCURE_H

    ^~~~~~~~~~~~~~
    _LIBSECFURE_H_

seccure/libseccure.c:60:22: error: equality comparison with extraneous
parentheses [-Werror,-Wparentheses-equality]
if ( (keypair->pub == NULL) )
~~~~~~~~~~~~~^~~~~~~
seccure/libseccure.c:60:22: note: remove extraneous parentheses around the
comparison to silence this warning
if ( (keypair->pub == NULL) )
~ ^ ~
seccure/libseccure.c:60:22: note: use '=' to turn this equality comparison into
an assignment
if ( (keypair->pub == NULL) )
^~
=
seccure/libseccure.c:474:13: error: equality comparison with extraneous
parentheses [-Werror,-Wparentheses-equality]
if ( (data == NULL) ) {
~~~~~^~~~~~~
seccure/libseccure.c:474:13: note: remove extraneous parentheses around the
comparison to silence this warning
if ( (data == NULL) ) {
~ ^ ~
seccure/libseccure.c:474:13: note: use '=' to turn this equality comparison into
an assignment
if ( (data == NULL) ) {
^~
=
seccure/libseccure.c:682:13: error: equality comparison with extraneous
parentheses [-Werror,-Wparentheses-equality]
if ( (data == NULL) ) {
~~~~~^~~~~~~
seccure/libseccure.c:682:13: note: remove extraneous parentheses around the
comparison to silence this warning
if ( (data == NULL) ) {
~ ^ ~
seccure/libseccure.c:682:13: note: use '=' to turn this equality comparison into
an assignment
if ( (data == NULL) ) {
^~
=
4 errors generated.
error: command 'clang' failed with exit status 1

@manjush3v
Copy link
Author

I am not sure if silencing clang warnings is considered best practice. I even found that open source projects don't consider these warnings as valid ones. #9 is a solution for clang warnings.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant