- update to 3.6.0:
3.6.0 is a feature release with many significant improvements and the usual collection of bug fixes. See the NEWS file for details. - apparently gcc-32bit does not exist on old code streams, but it seems to work without it as well - disable building docs until I find a way to build them without network access OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=20
This commit is contained in:
Git OBS Bridge
parent
3c504fac06
commit
ed1ef981db
File diff suppressed because it is too large
Load Diff
@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:457913240401bf61b8b72d5b4d7573d589553dec43a5d5724bc012a95282c736
|
||||
size 5187901
|
||||
3
valgrind-3.6.0.tar.bz2
Normal file
3
valgrind-3.6.0.tar.bz2
Normal file
@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bc0f0153b5a47b986f1d8efa2c488e0aea85a1cf2c4b11c52be127903080285f
|
||||
size 5962204
|
||||
@ -1,3 +1,22 @@
|
||||
-------------------------------------------------------------------
|
||||
Fri Oct 22 09:59:53 CEST 2010 - dmueller@suse.de
|
||||
|
||||
- update to 3.6.0:
|
||||
3.6.0 is a feature release with many significant improvements and the
|
||||
usual collection of bug fixes. See the NEWS file for details.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Thu Oct 21 13:17:43 CEST 2010 - dmueller@suse.de
|
||||
|
||||
- apparently gcc-32bit does not exist on old code streams, but
|
||||
it seems to work without it as well
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Wed Oct 20 19:38:57 CEST 2010 - dmueller@suse.de
|
||||
|
||||
- disable building docs until I find a way to build them without
|
||||
network access
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Wed Oct 13 13:42:05 CEST 2010 - dmueller@suse.de
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
#
|
||||
# spec file for package valgrind (Version 3.5.0)
|
||||
# spec file for package valgrind (Version 3.5.90.svn11414)
|
||||
#
|
||||
# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
|
||||
#
|
||||
@ -18,17 +18,17 @@
|
||||
|
||||
|
||||
Name: valgrind
|
||||
BuildRequires: gcc-c++ glibc-devel-32bit xorg-x11-devel docbook-xsl-stylesheets docbook_4 libxslt
|
||||
BuildRequires: docbook-xsl-stylesheets docbook_4 gcc-c++ glibc-devel-32bit libxslt xorg-x11-devel
|
||||
%ifarch x86_64 ppc64
|
||||
BuildRequires: gcc-32bit
|
||||
BuildRequires: glibc-devel-32bit
|
||||
%endif
|
||||
Url: http://valgrind.org/
|
||||
License: GPLv2
|
||||
License: GPL v2 or later
|
||||
Group: Development/Tools/Debuggers
|
||||
Summary: Valgrind Suite of Tools for Debugging and Profiling
|
||||
Summary: Memory Management Debugger
|
||||
BuildRoot: %{_tmppath}/%{name}-%{version}-build
|
||||
Version: 3.5.90.svn11414
|
||||
Release: 1
|
||||
Version: 3.6.0
|
||||
Release: 0.<RELEASE6>
|
||||
Source0: %{name}-%{version}.tar.bz2
|
||||
# svn di svn://svn.valgrind.org/valgrind/tags/VALGRIND_3_5_0 svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH > 3_5_BRANCH.diff
|
||||
# svn di svn://svn.valgrind.org/vex/tags/VEX_3_5_0 svn://svn.valgrind.org/vex/branches/VEX_3_5_BRANCH > VEX_3_5_BRANCH.diff
|
||||
@ -41,27 +41,31 @@ Provides: valgrind-devel = %version
|
||||
Provides: callgrind = %version
|
||||
Obsoletes: callgrind < %version
|
||||
ExclusiveArch: %ix86 x86_64 ppc ppc64 s390x
|
||||
%if %suse_version > 1100
|
||||
%define building_docs 1
|
||||
%else
|
||||
%define building_docs 0
|
||||
%endif
|
||||
|
||||
%description
|
||||
Valgrind checks all memory operations in an application, like read,
|
||||
write, malloc, new, free, and delete. Valgrind can find uses of
|
||||
uninitialized memory, access to already freed memory, overflows,
|
||||
illegal heap operations, memory leaks, and any illegal
|
||||
illegal stack operations, memory leaks, and any illegal
|
||||
new/malloc/free/delete commands. Another program in the package is
|
||||
"cachegrind," a profiler based on the valgrind engine. It is plugin
|
||||
based and many different tools are available.
|
||||
"cachegrind," a profiler based on the valgrind engine.
|
||||
|
||||
To use valgrind you should launch the application like normal with
|
||||
debuginfo packages installed, for example:
|
||||
|
||||
|
||||
_memcheck --leak-check_
|
||||
To use valgrind you should compile your application with "-g -O0"
|
||||
compiler options. Afterwards you can use it with:
|
||||
|
||||
valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes
|
||||
--db-attach=yes my_application, for example.
|
||||
|
||||
More valgrind options can be listed via "valgrind --help". There is
|
||||
also complete documentation in the /usr/share/doc/packages/valgrind/
|
||||
directory. A debugged application runs slower and needs much more
|
||||
memory, but is usually still usable.
|
||||
memory, but is usually still usable. Valgrind is still in development,
|
||||
but it has been successfully used to optimize several KDE applications.
|
||||
|
||||
|
||||
|
||||
@ -77,9 +81,10 @@ Authors:
|
||||
Robert Walsh
|
||||
|
||||
%if %suse_version > 1100
|
||||
|
||||
%package devel
|
||||
License: GPLv2+
|
||||
Summary: Valgrind Suite of Tools for Debugging and Profiling
|
||||
License: GPL v2 or later
|
||||
Summary: Memory Management Debugger
|
||||
Group: Development/Tools/Debuggers
|
||||
Requires: %name = %version
|
||||
|
||||
@ -87,22 +92,21 @@ Requires: %name = %version
|
||||
Valgrind checks all memory operations in an application, like read,
|
||||
write, malloc, new, free, and delete. Valgrind can find uses of
|
||||
uninitialized memory, access to already freed memory, overflows,
|
||||
illegal heap operations, memory leaks, and any illegal
|
||||
illegal stack operations, memory leaks, and any illegal
|
||||
new/malloc/free/delete commands. Another program in the package is
|
||||
"cachegrind," a profiler based on the valgrind engine. It is plugin
|
||||
based and many different tools are available.
|
||||
"cachegrind," a profiler based on the valgrind engine.
|
||||
|
||||
To use valgrind you should launch the application like normal with
|
||||
debuginfo packages installed, for example:
|
||||
|
||||
|
||||
_memcheck --leak-check_
|
||||
To use valgrind you should compile your application with "-g -O0"
|
||||
compiler options. Afterwards you can use it with:
|
||||
|
||||
valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes
|
||||
--db-attach=yes my_application, for example.
|
||||
|
||||
More valgrind options can be listed via "valgrind --help". There is
|
||||
also complete documentation in the /usr/share/doc/packages/valgrind/
|
||||
directory. A debugged application runs slower and needs much more
|
||||
memory, but is usually still usable.
|
||||
memory, but is usually still usable. Valgrind is still in development,
|
||||
but it has been successfully used to optimize several KDE applications.
|
||||
|
||||
|
||||
|
||||
@ -116,6 +120,7 @@ Authors:
|
||||
Paul Mackerras
|
||||
Dirk Mueller
|
||||
Robert Walsh
|
||||
|
||||
%endif
|
||||
|
||||
%prep
|
||||
@ -136,25 +141,33 @@ autoreconf -fi
|
||||
export GDB=/usr/bin/gdb
|
||||
%configure
|
||||
make %{?jobs:-j%jobs}
|
||||
%if %building_docs
|
||||
pushd docs
|
||||
#make all-docs
|
||||
# building the docs needs network access at the moment :-(
|
||||
make FAQ.txt man-pages html-docs
|
||||
popd
|
||||
%endif
|
||||
|
||||
|
||||
%install
|
||||
make DESTDIR=$RPM_BUILD_ROOT install
|
||||
mkdir -p $RPM_BUILD_ROOT/usr/share/doc/packages
|
||||
%if %building_docs
|
||||
mv $RPM_BUILD_ROOT/usr/share/doc/valgrind $RPM_BUILD_ROOT/usr/share/doc/packages
|
||||
%endif
|
||||
|
||||
%files
|
||||
%defattr(-,root,root)
|
||||
%doc README* NEWS AUTHORS COPYING COPYING.DOCS
|
||||
/usr/bin/*
|
||||
%_libdir/valgrind
|
||||
%doc %_mandir/*/*
|
||||
|
||||
%if %building_docs
|
||||
%doc %_mandir/*/*
|
||||
%endif
|
||||
|
||||
%if %suse_version > 1100
|
||||
|
||||
%files devel
|
||||
%defattr(-,root,root)
|
||||
%endif
|
||||
|
||||
Loading…
Reference in New Issue
Block a user