https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-mail/fdm-2.2-r1 has implicit function declarations in configure logs (MUSL-SYSTEM). Discovered on: amd64 (internal ref: tinderbox_musl) NOTE: (MUSL-SYSTEM) in the summary means that bug was found on a machine that runs MUSL libc but this bug MAY or MAY NOT BE related to musl. See also: https://bugs.gentoo.org/898488#c4.
Created attachment 863217 [details] build.log build log and emerge --info
Found the following implicit function declarations in configure logs: config.log:743 - b64_ntop config.log:792 - b64_ntop
tinderbox_musl has reproduced this issue with version 2.2-r2 - Updating summary.
tinderbox_musl has reproduced this issue with version 2.2-r3 - Updating summary.
The issue here is that the musl does not provide b64_ntop function at all, that is why the implicit function declaration is triggered. The configuration test fails later, because the program cannot be linked anyway. > checking for b64_ntop... no > checking for b64_ntop with -lresolv... no What is the proper fix for this issue? Should the test function redeclare the function prototype to silent the implicit function declaration warning?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40934b99ce963b13e33514aa345a4cca68d278a2 commit 40934b99ce963b13e33514aa345a4cca68d278a2 Author: Petr Vaněk <arkamar@gentoo.org> AuthorDate: 2025-01-10 13:15:41 +0000 Commit: Petr Vaněk <arkamar@gentoo.org> CommitDate: 2025-01-10 13:26:27 +0000 net-mail/fdm: skip qa check for b64_ntop Musl does no provide b64_ntop function, therefore the implicit function declaration message is rather false positive. fdm fallbacks to compat implementation based on this configuration check. Closes: https://bugs.gentoo.org/907833 Signed-off-by: Petr Vaněk <arkamar@gentoo.org> net-mail/fdm/fdm-2.2-r3.ebuild | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
