Date: Fri, 25 Mar 2016 10:34:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 208201] [maintainer update][patch] devel/dyncall: build with -fPIC Message-ID: <bug-208201-13-GbRPh2lWvq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208201-13@https.bugs.freebsd.org/bugzilla/> References: <bug-208201-13@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=3D208201 --- Comment #2 from Tassilo Philipp <tphilipp@potion-studios.com> --- dyncall is often used in scripting language extensions, which are shared libraries. Without fPIC, building those would fail. dyncall's configure step actually adds -fPIC for all FreeBSD builds, *if* CFLAGS isn't already set by the user. Since the ports tree sets it, the res= ult is that fPIC isn't used. This simply adds it back for FreeBSD builds. I *think* this would be required for all the platforms, as dyncall itself w= ould set it for all FreeBSD builds, I wouldn't see why dynamic linking logic wou= ld work on arm differently than x86? Maybe I'm missing something? --=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-208201-13-GbRPh2lWvq>