Bug 24984 - chemtool 1.6 doesn't install binaries via the make install command
Bug#: 24984 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: major Priority: P2
Resolution: FIXED Assigned To: phosphan@gentoo.org Reported By: PositronMan@hotmail.com
Component: Applications
URL:  http://pals.cwru.edu/~bgo/chemtool-bug.html
Summary: chemtool 1.6 doesn't install binaries via the make install command
Keywords:  
Status Whiteboard: 
Opened: 2003-07-21 11:40 0000
Description:   Opened: 2003-07-21 11:40 0000 
When I try to emerge chemtool-1.6, the files that should be installed with the
'
make DESTDIR="${D}" install || die "make install failed"' line, do not get
installed. I get no errors, and in fact, from the output of make install, it
looks like the process actually works! If I do 'make install' by hand, the
files
do get installed correctly. This is very strange, and I have absolutly no idea
what is going wrong. A copy of my emerge can be found at 
http://pals.cwru.edu/~bgo/chemtool-bug.html . I added a '-v' to /bin/install in
the makefile in hopes of getting more useful information.

Reproducible: Always
Steps to Reproduce:

------- Comment #1 From Patrick Kursawe 2003-08-05 00:19:57 0000 ------- 
I am not able to reproduce your bug. Please try executing the steps seperately
ebuild /path/to/ebuild compile
ebuild /path/to/ebuild install
and then check the contents of the portage temp directory.
I wonder if those files are not copied there or if they are not found there when merging...

------- Comment #2 From Brian 2003-08-05 10:43:19 0000 ------- 
Okay, I've just looked at this again and found the problem. The ebuild is buggy
for people who don't use kde. In src_install() there are the following lines:

   if ! use kde; then
       rm -rf ${D}/${KDEDIR}
   fi

Since I don't have kde, ${KDEDIR} is undefined. Therefore the above line
amounts to rm -rf ${D}/ , which deletes everything that 'make install' just put
in there. I think that a check for $KDEDIR, like

   if [ -z "${KDEDIR}" ]; then
       KDEDIR=boguskde;
   fi

at the beginning of the ebuild would fix the problem.

Hmmm, I just looked at environment.bz2 in the build-info directory, and I see a
KDEDIRS=/usr, should there maybe be an S on the end of KDEDIR, or is there
something wrong with my environment?

------- Comment #3 From Patrick Kursawe 2003-08-05 23:52:45 0000 ------- 
Ouch. Bad mistake by me. Just saying "I want KDE support" doesn't mean "I have
KDE"... No, KDEDIR was just fine for people who are using KDE, both variables
are set for them (KDEDIR=current version, KDEDIRS=other places to look for
stuff) - please retry after next sync if it works for you.

------- Comment #4 From Brian 2003-08-07 11:50:59 0000 ------- 
Works for me now, Thanks.