Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Hardcoded Path in Makefile, posted by Martin Killenberg on Tue Feb 20 18:41:31 2007 
    icon2.gif   Re: Hardcoded Path in Makefile, posted by Stefan Ritt on Tue Feb 20 21:10:28 2007 
Message ID: 2144     Entry time: Tue Feb 20 21:10:28 2007     In reply to: 2143
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Comment  OS: Linux  ELOG Version: 2.6.4 
Subject: Re: Hardcoded Path in Makefile 

Martin Killenberg wrote:
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")

I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary.


Ups. The hard-coded /usr/uname somehow sneaked in from some temporary test. I removed it in the current SVN.

Indeed the RPM package I provide is built under Scientific Linux. The Debian port is done by someone else. Unfortunately I don't have ten boxes with all possible distributions laying around, so my possibilities are quite limited and I depend on third party help. If you want to contribute additional RPMs you are welcome.
ELOG V3.1.5-fe60aaf