Date: Thu, 07 Jan 2016 06:20:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205476] x11-toolkits/wxgtk30 Provide backtrace option to configure Message-ID: <bug-205476-13-n8oE51WdFY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205476-13@https.bugs.freebsd.org/bugzilla/> References: <bug-205476-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=3D205476 Kyle Evans <kevans91@ksu.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #164461|0 |1 is obsolete| | Attachment #165200| |maintainer-approval?(portma Flags| |ster@bsdforge.com) --- Comment #7 from Kyle Evans <kevans91@ksu.edu> --- Created attachment 165200 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D165200&action= =3Dedit Amended svn diff for x11-toolkits/wxgtk30 In advance- apologies for being a pain on this. =3D) After thinking about it a little bit more, someone in #bsdports mentioned t= hat USES=3Dlibexec is a thing, and it seems this would allow for what might be = a more elegant solution with no reliance on OSVERSION. This is the patch that I'm attaching right now. This change could also be backported to x11-toolkits/wxgtk28, if any interest in this exists, as that version was t= he first (~7 years ago?) to start searching for backtrace(3) in libexecinfo in addition to libc. As it also turns out, its dependencies can eventually be traced out to devel/libexecinfo anyways, so this ultimately doesn't add much more to the build process. I have tested this on -CURRENT and the option is working as expected. Follo= wing this post, I will also be attaching poudriere logs for 9.3-RELEASE builds w= ith and without BACKTRACE, showing the expected results (--enable-backtrace or --disable-backtrace respectively and successful builds with either). --=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-205476-13-n8oE51WdFY>