Bug#1115168: marked as done (nfsutils: FTBFS: exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result])
Your message dated Sun, 14 Sep 2025 18:12:00 +0200
with message-id <aMbpUP1zuIMcomoK@aurel32.net>
and subject line Re: Bug#1115168: nfsutils: FTBFS: exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
has caused the Debian Bug report #1115168,
regarding nfsutils: FTBFS: exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1115168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115168
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-utils
Version: 1:2.8.3-1
Severity: important
Tags: ftbfs forky sid upstream fixed-upstream
Justification: fails to build from source
User: debian-glibc@lists.debian.org
Usertags: glibc-2.42
Control: forwarded -1 https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9f974046c37b7c28705d5558328759fff708b1cb
Dear maintainer,
During a rebuild of all packages in unstable with glibc 2.42 from
experimental, your package failed to build. Below you will find how the
build ends. If required, the full build log is available here:
https://people.debian.org/~aurel32/glibc-2.42/
The build failure is due to a missing check of the result of the call to
lockf(), so there is no guarantee that the file is correctly locked,
basically making this call useless. Fortunately the issue has already
been fixed upstream with the following patch:
https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9f974046c37b7c28705d5558328759fff708b1cb
About the archive rebuild: The build was made on virtual machines from
AWS, using sbuild, a reduced chroot with only build-essential packages
and glibc 2.42 from experimental.
Regards
Aurelien
--------------------------------------------------------------------------------
[...]
Making all in utils
make[2]: Entering directory '/<<PKGBUILDDIR>>/utils'
Making all in exportfs
make[3]: Entering directory '/<<PKGBUILDDIR>>/utils/exportfs'
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/reexport -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes -Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2 -Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2 -Werror=init-self -Werror=implicit-function-declaration -Werror=return-type -Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return -Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2 -Werror=int-conversion -Werror=incompatible-pointer-types -Werror=misleading-indentation -Wno-cast-function-type -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o exportfs-exportfs.o `test -f 'exportfs.c' || echo './'`exportfs.c
exportfs.c: In function ‘release_lockfile’:
exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
83 | lockf(_lockfd, F_ULOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
exportfs.c: In function ‘grab_lockfile’:
exportfs.c:77:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
77 | lockf(_lockfd, F_LOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [Makefile:573: exportfs-exportfs.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/utils/exportfs'
make[2]: *** [Makefile:480: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/utils'
make[1]: *** [Makefile:504: all-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j2 returned exit code 2
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Version: 2.8.4-1
On 2025-09-13 23:20, Aurelien Jarno wrote:
> Source: nfs-utils
> Version: 1:2.8.3-1
> Severity: important
> Tags: ftbfs forky sid upstream fixed-upstream
> Justification: fails to build from source
> User: debian-glibc@lists.debian.org
> Usertags: glibc-2.42
> Control: forwarded -1 https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9f974046c37b7c28705d5558328759fff708b1cb
>
> Dear maintainer,
>
> During a rebuild of all packages in unstable with glibc 2.42 from
> experimental, your package failed to build. Below you will find how the
> build ends. If required, the full build log is available here:
>
> https://people.debian.org/~aurel32/glibc-2.42/
>
> The build failure is due to a missing check of the result of the call to
> lockf(), so there is no guarantee that the file is correctly locked,
> basically making this call useless. Fortunately the issue has already
> been fixed upstream with the following patch:
>
> https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9f974046c37b7c28705d5558328759fff708b1cb
>
Thanks for the upload of the new upstream version, I confirm that the
bug is now fixed. Closing it accordingly.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
--- End Message ---
Reply to: