Hi,

Looks like the current version of top now has a target in the Makefile
to handle the installation.  On Solaris this is necessary since it looks
like it now creates platform specific (ie. sparcv9) subdirs in bin for
the actual top executable.  With the current shtool install method in
the build spec, top doesn't run after the RPM is installed.

Attached is a simple patch for the spec file to use the make install
command (also added the --mandir configure option so the manpage ends up
in the right directory). 

-steve
diff -ruN top.orig/top.spec top/top.spec
--- top.orig/top.spec	2009-06-10 09:59:42.536461000 -0400
+++ top/top.spec	2009-06-10 10:00:18.086690000 -0400
@@ -68,7 +68,8 @@
     CC="%{l_cc}" \
     CFLAGS="%{l_cflags -O}" \
     ./configure \
-        --prefix=%{l_prefix}
+        --prefix=%{l_prefix} \
+	--mandir=%{l_prefix}/man
 
     #   build program
     %{l_make} %{l_mflags}
@@ -77,13 +78,7 @@
     rm -rf $RPM_BUILD_ROOT
 
     #   install program
-    %{l_shtool} mkdir -f -p -m 755 \
-        $RPM_BUILD_ROOT%{l_prefix}/bin \
-        $RPM_BUILD_ROOT%{l_prefix}/man/man1
-    %{l_shtool} install -c -s -m 755 \
-        top $RPM_BUILD_ROOT%{l_prefix}/bin/
-    %{l_shtool} install -c -m 644 \
-        top.1 $RPM_BUILD_ROOT%{l_prefix}/man/man1/
+    %{l_make} %{l_mflags} install DESTDIR=$RPM_BUILD_ROOT
 
     #   determine installation files
     %{l_rpmtool} files -v -ofiles -r$RPM_BUILD_ROOT \

Reply via email to