Number of commits found: 53

Backport two revisions from Valgrind svn to fix crash when debugging
binaries built with GCC 4.6+:

  r11856 | tom | 2011-07-05 02:22:32 -0700 (Tue, 05 Jul 2011) | 2 lines

  Implement some extra DWARF ops that gcc 4.6.1 seems to use. Fixes #275284.

  r11904 | tom | 2011-07-21 08:07:26 -0700 (Thu, 21 Jul 2011) | 2 lines

  DWARF comparisons should be signed. Patch from Jakub Jelinek.

Submitted by:   Tom Russo <tvrusso sandia.gov>
PR:             ports/166341

-The base __aligned attribute no longer exists in gcc46+
-patch uses __attribute__ which is upward compatible with gcc42+

PR:             ports/156881
Submitted by:   Zhihao Yuan <lichray@gmail.com>
Approved by:    maintainer(timeout), gaboe(mentor)
Feature safe:   yes

- Return my ports back to the pool.  I was unable to make any fixes to
  my ports in the past 3 weeks while ports were broken on any 10.x
  machines, which means I'm unable to maintain them.  So let people know
  that there's no available support for them until things are back to
  normal (which also means that anyone with spare time will be able
  to fix them without getting approval).

- Update to revision 2.  This update includes fixes for setcontext/getcontext
  routines.

- Udpdate to a new 3.6.1 snapshot.
  Changes:
  - Implement shm_unlink wrapper.
  - Add support for SHM_ANON shm_open(2) path.
  - Fix sycalls 0 and 198 (__syscall) handling.

- Update valgrind to 3.6.1.
  This is a bugfix release.

Chase the upgrade of MPICH2.

- Update to revision 2:
  - getfsstat syscall handling
  - merge in forgotten changes from p4 (shmctl handling).

- Update to revision 1.

Changelog:
  - Add shm_open syscall handler implementation.
  Submitted by: Jerry Toung <jrytoung@gmail.com>

- Update to 3.6.0.

- Fix shmat syscall wrapper [1].
- Implement shmctl syscall wrapper.

PR:             ports/149621 [1]
Submitted by:   Stephen Sanders <ssanders@opnet.com> [1]

- Update to revision 3.
  - Add support for syscall 510 (new _semctl).

Submitted by:   Brian Fundakowski Feldman <bfeldman@hammers.com>

- Update to 3.5.0-2:
  - Fix build of MPI wrappers [1]
  - Fix LDT handling in i386 case.
  - Fix socketpair(2) syscall wrapper.

PR:             ports/144067 [1]
Reported by:    "O. Hartmann" <ohartman@zedat.fu-berlin.de> [1]

- Update to newer snapshot fro P4.

- Bump PORTREVISION as the revision numbering scheme has changed.
- Reformat pkg-descr for lines to not exceed 80 characters.

Pointed out by: bsam
Feature safe:   yes

- Remove the bogus PKGNAMESUFFIX that erroneously went in.

Pointy hat to:  me
Feature safe:   yes

- Do not try to build 32-bit support on amd64 if 32-bit libraries are not
  available.

Suggested by:   koitsu
Feature safe:   yes

- Update to version 3.5.0.

Feature safe:   yes

- Take maintainership.

- Fix build with NOPORTDOCS

Approved by:    miwi (mentor, implicit)

Reset barner@FreeBSD.org due to several months of inactivity.

Hat:            portmgr

- Remove conditional checks for FreeBSD 5.x and older

- Fix build from within jails

PR:             ports/127015
Submitted by:   Alexander Churanov
Approved by:    portmgr (erwin)

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

(Only the first 15 lines of the commit message are shown above )

Conversion from (now defunct) autoconf-2.61 to autoconf-2.62

Tested by:      exp build run (erwin)

Fix build on FreeBSD 7.

Requested by:   many
PR:             ports/116513 [1],
                ports/123711 [2]
Submitted by:   Bruce Cran <bruce@cran.org.uk> [1],
                delphij [2]

- Mark BROKEN on 7.x

Reported by:    pointyhat

Mark IGNORE on 8.0: unsupported.

Remove always true/always false OSVERSION conditions.

Remove always-false/true conditions based on OSVERSION 500000

Switch autoconf dependencies from 2.53 or 2.59 to 2.61.

PR:             ports/116639
Submitted by:   aDe

Welcome bsd.perl.mk.  Add support for constructs such as USE_PERL5=5.8.0+.
Drop support for antique perl.

Work done by:   gabor
Sponsored by:   Google Summer of Code 2007
Hat:            portmgr

Remove USE_REINPLACE from all categories starting with D

- SHM fix: Silence erroneous warnings on X server initialization
- Bump PORTREVISION

Submitted by: anholt

- Add support for uuidgen(2) system call
- Bump PORTREVISION

Submitted by:   rodrigc
PR:             ports/87697

- Fix on FreeBSD 6 and above: [1] [2]

  Valgrind did not handle the following sysarch calls, and thus crashed
  immediately
    o get_fsbase
    o set_fsbase
    o get_gsbase
    o set_fsbase

- Valgrind no longer dumps core when its client application does. [2]

  Valgrind-snapshot does contain for safing the client's core dump,
  but it does not work (it resulted in a crash) and has therefore been
  disabled.

(Only the first 15 lines of the commit message are shown above )

- Mark valgrind ports IGNORE when /proc is not mounted, previously, only
  a warning was printed.

  A mounted procfs is a runtime dependency of valgrind, but since the
  implementation of automatic suppression file generation the valgrind
  binary is run in the post-install stage.

- An exception needs to be made for the ports cluster: The machine compiling
  the list of IGNOREd ports does not have a mounted /proc, so the check (and
  the generation of supression files is disabled there).

  Users who want to suppress false positives in valgrinds output should build
  the port instead of installing the package (so the rules can be customized to
  their specific installation).

Reported by:    Paul Ledbetter III <aeacides@gmail.com>
Approved by:    portmgr (kris)

Fix generation of suppression files: Valgrind puts parts of its output
on stderr, so the redirection into a file did not work.

Submitted by:   Eugene Kilachkoff <zeus@samaramail.ru>
PR:             ports/81249

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

Change email address in ports maintained by me to barner@FreeBSD.org

Approved by:    arved (mentor)

- Add some suppression files & fix packaging[1]
   (bump PORTREV)
- Warn if USER_LDT is not present in 4.x-kernel [2]

PR:             ports/71832 [1]; ports/75436 [2]
Submitted by:   Frerich Raabe;   maintainer

- Starting from some point after FreeBSD 5.2.1, valgrind did not terminate
  correctly, but got stuck in state ``umtx''. This was mentioned on the lists
  and in kern/68992 [closed], but I was never able to fix the problem.

  On FreeBSD >= 502120, the kernel's and valgrind's definition of
  UMTX_CONTESTED flag were out of sync, which is why valgrind did not terminate
  on these systems.

PR:             ports/74903
Submitted by:   Simon Barner <barner@gmx.de> (maintainer)

- Take care of leftover pkgconfig directory

PR:             ports/74818
Submitted by:   Simon Barner <barner@gmx.de> (maintainer)

Remove junk from Makefile.

Reported by: Amir Shalem <amir(at)boom.org.il>

Rename devel/calltree to callgrind.
Update it to 0.9.8.
Update related ports.

PR:             ports/70936
Submitted by:   maintainer

Correct CONFLICTS. valgrind-snapshot conflicts with every version of
valgrind, not just 352.

Instead of just checking for PACKAGE_BUILDING, don't let the check for
procfs stop the portbuild at all. Displaying a warning is fine, breaking
the build over a runtime requirement that does not break building the port
is not.

valgrind installs different files on RELENG_4 & RELENG_5, add some
PLIST_SUB to deal with that.

Disable procfs check on package builders.

- Use canonical way to request new Perl

- Update to 352

PR:             ports/69553
Submitted by:   Simon Barner <barner@in.tum.de> (maintainer)

Valgrind is a system for debugging and profiling un*x programs.
With the tools that come with Valgrind, you can automatically
detect many memory management and threading bugs, avoiding
hours of frustrating bug-hunting, making your programs more
stable. You can also perform detailed profiling, to speed up
and reduce memory use of your programs.

The Valgrind distribution includes five tools: two memory error
detectors, a thread error detector, a cache profiler and a heap
profiler.  Several other tools have been built with Valgrind.

Valgrind was ported to FreeBSD by Doug Rabson (http://www.rabson.org/).

Submitted by:   Doug Rabson <dfr@FreeBSD.org> and Simon Barner
<barner@in.tum.de>

Number of commits found: 53

12 vulnerabilities affecting 17 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities