devel/google-perftools: Add comment

devel/google-perftools: update 2.15 → 2.16

devel/google-perftools: Broken on arm64

Reported by:	fallout

devel/google-perftools: Fix plist when PROFILE=OFF

PR:		277642
Reported by:	Christos Chatzaras <chris@cretaforce.gr>

devel/google-perftools: Add required test deps and mark TESTING_UNSAFE

devel/google-perftools: update 2.10 → 2.15

devel/google-perftools: Moved man to share/man

Approved by:    portmgr (blanket)

devel/google-perftools: enable libunwind on powerpc

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

compiler: use CHOSEN_COMPILER_TYPE instead of COMPILER_TYPE

CHOSEN_COMPILER_TYPE is the only safe variable to let a port know which
typer of compiler has been elected to be used by the framework

PR: 	199098

devel/google-perftools: Fix build on aarch64

'profiler' option fails to initialize

Reported by:	fallout

devel/google-perftools: Broken on armv7

Reported by:	fallout

devel/google-perftools: Fix typo in options

devel/google-perftools: Fix build on armv6

Build was failing on armv6 with this error:
ld: error: ./.libs/libtcmalloc_debug.so: undefined reference to unw_getcontext

Reported by:	fallout

devel/google-perftools: Broken on riscv64

Reported by:	fallout

devel: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  "Waitman Gobble" <uzimac@da3m0n8t3r.com>
  *  <jkoshy@FreeBSD.org>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron H. K. Diep <ahkdiep@gmail.com>
  *  Aaron Hurt <ahurt@anbcs.com>
  *  Abel Chow <abel_chow@yahoo.com>
  *  Adam McLaurin
  *  Adam Saponara <as@php.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>

devel/google-perftools: Re-enable on aarch64, riscv64

... to see if it builds now.
BROKEN lines were added 2 years ago. The upstream now claims that at
least aarch64 is fully supported.

devel/google-perftools: Add PROFILER options

Option for CPU profiler is mostly to isolate situations when
configure fails to enable it, like on armv6, armv7.

Reference:
https://github.com/gperftools/gperftools/issues/1355#issuecomment-1188455253

devel/google-perftools: Update 2.9.1 -> 2.10

devel/google-perftools: Actually link to libunwind.

This fixes the build on recent CURRENT.

Approved by:	yuri (maintainer, via email)

devel/google-perftools: Add LD_32_PRELOAD to the valgrind detection code

Suggested by:	Paul Floyd <pjfloyd@wanadoo.fr>

devel/google-perftools: Add a more reliable way to detect that the process is
run under Valgrind

devel/google-perftools: enable libunwind on all arches where it's supported

devel/google-perftools: Update 2.8.1 -> 2.9.1

Remove # $FreeBSD$ from Makefiles.

devel/google-perftools: Update 2.8 -> 2.8.1

Mark as BROKEN on riscv64 similar to aarch64.

Approved by:	portmgr (tier-2 blanket)
Obtained from:	lonesome.com build testing

Mark various ports BROKEN on aarch64.

Obtained from:	local run @lonesome.com

devel/google-perftools: Update 2.7.90 -> 2.8

devel/google-perftools: Update 2.7 -> 2.7.90

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

devel/google-perftools: fix build with GCC-based architectures

PR:		235498
Submitted by:	Piotr Kubaj <pkubaj@anongoth.pl>

Conditionalize the dependence of libunwind to x86-only to allow building
these ports on !x86.

libunwind is only available for x86; lang/ruby* already expresses this
correctly.  Some of the rubygems did not: for the ones that already had
USE_RUBY, the dependency was overspecified in the first place.

Tested for no-harm on amd64.

While here, pet portlint where appropriate.

Approved by:	portmgr (tier-2 blanket)

Fix error messages on tier-2 archs.

Approved by:	portmgr (tier-2 blanket)

devel/google-perftools: Update 2.6.3 -> 2.7

Reported by:	repology

devel/google-perftools: Update to 2.6.3

Approved by:	tcberner (mentor)
Differential Revision:	https://reviews.freebsd.org/D13750

Cleanup after removal of libexecinfo from ports.

PR:		220271
Submitted by:	mat (review), Yasuhiro KIMURA (PR)
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D11488

Remove USES=execinfo.

PR:		220271
Submitted by:	mat (review), Yasuhiro KIMURA (PR)
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D11488

Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
   c++14-lang, c++0x, c11, or gcc-c++11-lib.

PR:		219275

devel/google-perftools: Update to 2.6.1

Changes:	https://github.com/gperftools/gperftools/releases/tag/gperftools-2.6.1

PR:		220606
Submitted by:	Yuri Victorovich <yuri@rawbw.com> (maintainer)
Approved by:	garga (mentor, implicit)

* Updated to 2.6
* Added gmake to USES
* New options, PAGE and ALIGN, Default PAGE8k ALIGN16
* Moved LIB_DEPENDS, BROKEN_*(13.1.5) comes before *_DEPENDS(13.1.6)[1]
* Moved USES, comes before USE_*(13.1.7)[1]

Changelog: https://github.com/gperftools/gperftools/releases/tag/gperftools-2.6

[1]
https://www.freebsd.org/doc/en/books/porters-handbook/porting-samplem.html#porting-samplem-order

PR:		220519
Submitted by:	Yuri Victorovich <yuri@rawbw.com> (maintainer)
Reviewed by:	matthew (mentor)
Approved by:	matthew (mentor)
Differential Revision:	https://reviews.freebsd.org/D11524

Begin deorbit burn of ia64.  We have not attempted to build packages for
it for many years.

While here, alphabetize ARCHs, pet portlint, and modernize usages.

Approved by:	portmgr (tier-2 blanket)

Add a fixup-lib-pkgconfig target to move files in lib/pkgconfig into
libdata/pkgconfig.

Fix ports that where installing the file in the wrong place.

PR:		218067
Submitted by:	mat
Exp-run by:	antoine
Reviewed by:	rene, antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D10129

- Switch to new test framework
- Update WWW
- Cosmetic fixes

Approved by:	portmgr blanket

Do not use post-stage.  Use post-install instead.

The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.

PR:		214780
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

many ports: mark broken on powerpc64

Remove ${PORTSDIR}/ from depends. Again.

Sponsored by:	Absolight

- Update to 2.5
- While I'm here:
  - Use = for LIB_DEPENDS
  - Convert to new options target helper

Changes:	https://github.com/gperftools/gperftools/releases
PR:		208582
Submitted by:	Yuri Victorovich <yuri@rawbw.com> (maintainer)

By default libtool replaces -export-symbols <file> with -retain-symbols-file
<file> on ELF systems, but this doesn't really do what -export-symbols is
meant to do.  On GNU ELF systems it converts <file> to a simple version
script first and then uses -version-script instead of -retain-symbols-file.
Let USES=libtool patch libtool scripts to do this on all systems with GNU
ld(1).

Bump PORTREVISION on all ports where the build log contains -export-symbols.

audio/calf: This port builds a module that now exports only one function,
but it also builds a number of executables that link to this module and
expect to see other functions.  Because it's already a bit dodgy to link to
a module (libtool warns about this) let the module continue to export only
one function and instead build an ordinary library from the same source that
the executables can link to.  Fix a number of other issues in the same

MASTER_SITES cleanup.

- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
  of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
  no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.

While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.

Also, replace some EXTRACT_SUFX occurences with USES=tar:*.

Checked by:	make fetch-urlall-list
With hat:	portmgr
Sponsored by:	Absolight

Upgrade to 2.4.

PR:		198467
Submitted by:	maintainer

- Update to version 2.3
- Change maintainer's email

PR:		195874
Submitted by:	maintainer

Cleanup plist

USES=execinfo

Add DOCS to OPTIONS_DEFINE to ports that check for PORT_OPTIONS:MDOCS.

Maintainer update to 2.2.1, obsoleting patch-malloc_hook_mmap_freebsd.h.

PR:		191334
Submitted by:	yuri@rawbw.com (maintainer)

- Switch devel/google-perftools to USES=libtool, drop .la files
- Bump dependent ports as .so version has changed

Approved by:	portmgr blanket

Support LIBS like LDFLAGS.

- Add LIBS="${LIBS}" to MAKE_ENV and CONFIGURE_ENV.
- Add an option helper for LIBS.
- Adjust all ports that already use LIBS.  Also remove references to
  PTHREAD_CFLAGS and PTHREAD_LIBS while here.
- Some ports did not support having a LIBS environment variable and
  required additional patches.

Somewhat simplified a linker command line looks like:

${CC} ${src_LDFLAGS} ${LDFLAGS} ${src_LIBS} ${LIBS}

where src_LDFLAGS and src_LIBS are controlled by upstream and LDFLAGS and
LIBS can be controlled by us.  If possible -L and -l flags need to be

Revert USE_GCC addition, and for clang, set -fno-builtin, and strip the
GCC-specific -fno-builtin-<FUNCTION> arguments.

Now has two failures on 10.0-RC5 and three on 9.2-RELEASE-p3 (both
amd64) with the respective default compiler.

Maintainer upgrade to a new version. Also fixes FreeBSD 10+ build
failures.

Note I have revised the Makefile, and I have also added USE_GCC=any
because we get considerably more "make check" failures with clang.

PR:		ports/185261
PR:		ports/185797
Submitted by:	Yuri <yuri@rawbw.com> (maintainer)

Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 2)

This changes almost all the "gnomehack" only USE_GNOME cases to USES= pathfix.

If a port used other USE_GNOME items it was untouched.
The ports that used other USES were fixed by hand.

PR:		ports/177081
Reviewed by:	bapt
Approved by:	portmgr (miwi)

Update to version 1.8.3

PR:             ports/160493
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)
Approved by:    miwi, wen (mentors implicit)

- Update to 1.7

PR:             154910
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)

- Update to 1.6

PR:             ports/149407
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)
Approved by:    pgj (mentor)

- Fixes the minor issue when shared libraries aren't accounted for in the
profile.

PR:             ports/147930
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)
Feature safe:   yes

Not for powerpc, either.

Hat:            portmgr

- Update to 1.5

PR:             143112
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)

- Update to 1.3

PR:             137376
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)

- Unbreak on amd64

Submitted by:   maintainer via private email

- Use MAN1 instead of pkg-plist.
- Use standard DOCSDIR instead of version-suffix directory.
- Use USE_LDCONFIG to ask ports system to reload.

PR:             134847
Submitted by:   Gea-Suan Lin <gslin@gslin.org>
Approved by:    Yuri <yuri@rawbw.com> (maintainer)

- Update to 1.0

PR:             130354
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)

- Update to 0.98

PR:             127333
Submitted by:   Yuri <yuri@tsoft.com> (maintainer)

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.

To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.

To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.

Changes to Mk/*:
 - Add runtime detection magic in bsd.port.mk

- Update to 0.9.7

PR:             ports/123061
Submitted by:   Yuri <yuri at tsoft.com> (maintainer)

Use ${MASTER_SITE_GOOGLE_CODE} instead of
http://something.googlecode.com/files

PR:             ports/121435 (related)

Upgrade devel/google-perftools from 0.93 to 0.94.

ChangeLog:
http://google-perftools.googlecode.com/svn/tags/perftools-0.94/ChangeLog

Submitted by:   Yuri <yuri@rawbw.com> (maintainer)

Broken on sparc64 as well as amd64.

While here, fix a typo.

Approved by:    portmgr (self)

Add new port devel/google-perftools:

Perf Tools is a collection of a high-performance multi-threaded malloc()
implementation, plus some pretty nifty performance analysis tools.
Perf Tools is the fastest memory allocation library available,
it also often allows applications to have smaller memory
footprint.

WWW: http://code.google.com/p/google-perftools

PR:             ports/113689
Submitted by:   Yuri <yuri@tsoft.com>