Date: Sun, 10 Apr 2016 13:54:34 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207964] /usr/src/lib/libc/gen/signal.c:(.text+0x0): multiple definition of `signal' Message-ID: <bug-207964-8-1IxBuWbkQp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207964-8@https.bugs.freebsd.org/bugzilla/> References: <bug-207964-8@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=3D207964 Jilles Tjoelker <jilles@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jilles@FreeBSD.org --- Comment #1 from Jilles Tjoelker <jilles@FreeBSD.org> --- Apparently, libc and libroken can't be both linked statically. I recommend linking at least libc (and libthr and librt if you use them) dynamically. Another reason for this is that external NSS modules only work with dynamic linking of libc. If you can modify the application's source code, changing it to use sigacti= on() instead of signal() may help. Note that libroken's signal enables SA_RESTART for all signals except SIGALRM. Libc could avoid this problem by moving the definition of the _sigintr vari= able to its own file. --=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-207964-8-1IxBuWbkQp>