Red Hat Bugzilla – Bug 990243
Building glusterfs should fail when functions are implicitly declared
Last modified: 2014-04-17 07:44:35 EDT
It seems that calling undeclared functions do not cause the build to fail. However, the missing function will likely cause issues when the compiled binaries are run.
gcc supports a -Werror=implicit-function-declaration option that could be used for this.
REVIEW: http://review.gluster.org/5435 (build: use -Werror=implicit-function-declaration to detect build issues) posted (#1) for review on master by Niels de Vos (email@example.com)
COMMIT: http://review.gluster.org/5435 committed in master by Anand Avati (firstname.lastname@example.org)
Author: Niels de Vos <email@example.com>
Date: Tue Jul 30 18:22:48 2013 +0200
build: use -Werror=implicit-function-declaration to detect build issues
There have been review requests that include a call to a non-existent
function. These problems should be detected as early as possible,
preferably before (automated) regression tests.
Signed-off-by: Niels de Vos <firstname.lastname@example.org>
Reviewed-by: Amar Tumballi <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Anand Avati <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.