Date: Sat, 13 May 2023 17:47:21 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 271131] net/asterisk18: utils.c:99:12: error: static declaration of 'gethostbyname_r' follows non-static declaration Message-ID: <bug-271131-7788-SFAGijURW5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271131-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-271131-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271131 --- Comment #9 from O. Hartmann <ohartmann@walstatt.org> --- (In reply to Mina Gali=C4=87 from comment #8) I understand the logic o the check that six arguments includes five argumen= ts, see foryourself. And both checks set to logical 1 "qualifies" for the existence of a reentrant gethostbyname_r(). Well ... I try to focus on a practical solution. My attempt to compile the original = port (asterisk18) with the latest patch for LLVM14 also failed. Either the base framework (Mk) has made changes, or LLVM prior to 15/14 did not check for t= he=20 bailing-out ambigous declaration of gethostbyname_r() and I'm curious wheth= er the compiler has always on FreeBSD picked up the "wrong" function (libc has= the more recent one, according to the head comment of the file main/utils.c in asterisk18, it has been edited last time 2006). In the latter case, the who= le #if statement should be enveloped into=20 #if !defined(__FreeBSD__) #endif This is the way I do the workaround. net/asterisk18 compiles and as for now= , I didn't realise any problems while operating the binary - for now. I can provide the patch here - but I fear I have made myself a fool by discussing "my naive" impressions (I do not active develop ...). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271131-7788-SFAGijURW5>