You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

83 lines
2.8 KiB

##
## strace.spec -- OpenPKG RPM Package Specification
## Copyright (c) 2000-2022 OpenPKG Project <http://openpkg.org/>
##
## Permission to use, copy, modify, and distribute this software for
## any purpose with or without fee is hereby granted, provided that
## the above copyright notice and this permission notice appear in all
## copies.
##
## THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
## WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
## MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
## IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR
## CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
## SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
## LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
## USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
## ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
## OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
## OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
## SUCH DAMAGE.
##
# package information
Name: strace
Summary: System Call Tracing
URL: http://www.liacs.nl/~wichert/strace/
Vendor: Rick Sladkey
Packager: OpenPKG Project
Distribution: OpenPKG Community
Class: EVAL
Group: Debugging
License: GPL
Version: 4.5.19
Release: 20091022
# list of sources
Source0: http://download.sourceforge.net/strace/strace-%{version}.tar.bz2
Patch0: strace.patch
# build information
BuildPreReq: OpenPKG, openpkg >= 20160101
PreReq: OpenPKG, openpkg >= 20160101
%description
Strace is a system call trace, i.e. a debugging tool which
prints out a trace of all the system calls made by a another
process/program. The program to be traced need not be recompiled for
this, so you can use it on binaries for which you don't have source.
System calls and signals are events that happen at the user/kernel
interface. A close examination of this boundary is very useful
for bug isolation, sanity checking and attempting to capture race
conditions
%track
prog strace = {
version = %{version}
url = http://sourceforge.net/projects/strace/files/
regex = strace-(__VER__)\.tar\.bz2
}
%prep
%setup -q
%patch -p0
%build
CC="%{l_cc}" \
CFLAGS="%{l_cflags -O}" \
./configure \
--prefix=%{l_prefix} \
--mandir=%{l_prefix}/man \
--disable-nls
%{l_make} %{l_mflags -O}
%install
%{l_make} %{l_mflags} install DESTDIR=$RPM_BUILD_ROOT
strip $RPM_BUILD_ROOT%{l_prefix}/bin/* >/dev/null 2>&1 || true
%{l_rpmtool} files -v -ofiles -r$RPM_BUILD_ROOT %{l_files_std}
%files -f files
%clean