History log of /dragonfly/lib/libexecinfo/Makefile (Results 1 – 3 of 3)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3
# 77bd33e1 20-Dec-2019 zrj <rimvydas.jasinskas@gmail.com>

libexecinfo(3): Internalize libelf in symtab.c.

Previous variant had symbol conflicts against ports libelf library.
Use custom, cut down variant that provides basic set needed for
libexecinfo sym

libexecinfo(3): Internalize libelf in symtab.c.

Previous variant had symbol conflicts against ports libelf library.
Use custom, cut down variant that provides basic set needed for
libexecinfo symtab.c, ensure symbols are static and mangled.
The libelf (as provided in contrib) is not very suitable for generic
implementation of backtrace(3) function family.

This is a temporary workaround to unbreak specific ports that are link
against libelf and libexecinfo (including static compilations).

Reported-by: Romick@users

show more ...


Revision tags: v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1
# dba3e8e9 02-Jul-2017 zrj <rimvydas.jasinskas@gmail.com>

lib/libexecinfo: Fix static and profiled archives.

Previously archives were embedded within archives.

Reported-by: tuxillo


Revision tags: v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc
# 999f82af 03-Nov-2015 John Marino <draco@marino.st>

Add libexecinfo to lib directory, but leave it unhooked

The execinfo library is used to fill in the backtrace of the currently
executing thread. It originated in Linux and has found its way into a

Add libexecinfo to lib directory, but leave it unhooked

The execinfo library is used to fill in the backtrace of the currently
executing thread. It originated in Linux and has found its way into a
lot of vendor software. NetBSD created a BSD-licensed implementation
which FreeBSD imported a while back.

The execinfo library has been in FreeBSD since Release 10. FreeBSD 9
is the only release that needs libexecinfo from ports and when that
release hits EOL, DragonFly could be left unsupported if ports
maintainers assumes libexecinfo is always available and removes USES
support for it.

To avoid this situation, bring libexecinfo into DragonFly's base for
the purpose of supporting ports. It requires libelf which has also
been brought in as an internal library.

show more ...