Bug 20080 - tcltk.spec installs some Itcl files in %{_prefix} instead of RPM_BUILD_ROOT%{_prefix}
tcltk.spec installs some Itcl files in %{_prefix} instead of RPM_BUILD_ROOT%{...
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: tcltk (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-30 22:16 EST by jens.koerber
Modified: 2007-04-18 12:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-11-15 08:31:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jens.koerber 2000-10-30 22:16:05 EST
Fix:

#------------------------------------------
# Itcl
#
make INSTALL_ROOT=${RPM_BUILD_ROOT} INSTALL="install -c" \
      exec_prefix=%{_prefix} \
           bindir=$RPM_BUILD_ROOT%{_bindir} \
           libdir=$RPM_BUILD_ROOT%{_libdir} \
           mandir=$RPM_BUILD_ROOT%{_mandir} \
          infodir=$RPM_BUILD_ROOT%{_infodir} \
       includedir=$RPM_BUILD_ROOT%{_prefix}/include \
    MKINSTALLDIRS="mkdir -p" install -C itcl%{itclvers}
Comment 1 Jeff Johnson 2000-11-02 11:32:29 EST
There are two empty directories not installed correctly:
	/usr/lib/itcl3.2
	/usr/lib/itk3.2
Fixed in tcltk-8.3.2-48.
Comment 2 jens.koerber 2000-11-15 08:31:36 EST
hmmm, another one (sorry... forgot that) .. it's itk/itcl version 3.2 NOT
3.1 in

ln -sf libitk3.1.so ${RPM_BUILD_ROOT}%{_libdir}/libitk.so
ln -sf libitcl3.1.so ${RPM_BUILD_ROOT}%{_libdir}/libitcl.so

fix

ln -sf libitk%{itclvers}.so ${RPM_BUILD_ROOT}%{_libdir}/libitk.so
ln -sf libitcl%{itclvers}.so ${RPM_BUILD_ROOT}%{_libdir}/libitcl.so
Comment 3 Jeff Johnson 2001-01-06 06:44:08 EST
Yup, itcl/itk libraries were not installed correctly. Fixed (again) in
tcltk-8.3.2-50. Thanks
for reopening the bug.

Note You need to log in before you can comment on or make changes to this bug.