[Bug 205476] x11-toolkits/wxgtk30 Provide backtrace option to configure
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jan 7 06:20:12 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205476
Kyle Evans <kevans91 at ksu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #164461|0 |1
is obsolete| |
Attachment #165200| |maintainer-approval?(portma
Flags| |ster at bsdforge.com)
--- Comment #7 from Kyle Evans <kevans91 at ksu.edu> ---
Created attachment 165200
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165200&action=edit
Amended svn diff for x11-toolkits/wxgtk30
In advance- apologies for being a pain on this. =)
After thinking about it a little bit more, someone in #bsdports mentioned that
USES=libexec 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 the
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. Following
this post, I will also be attaching poudriere logs for 9.3-RELEASE builds with
and without BACKTRACE, showing the expected results (--enable-backtrace or
--disable-backtrace respectively and successful builds with either).
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list