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 (ndevos)
COMMIT: http://review.gluster.org/5435 committed in master by Anand Avati (avati) ------ commit 7e6432015afd758ca3fd9e32d3e62b29935b0874 Author: Niels de Vos <ndevos> 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. Bug: 990243 Change-Id: Idcf4d27f45a1a6177105d02a039363702eb8e3b9 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/5435 Reviewed-by: Amar Tumballi <amarts> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user