I'm trying to install sarg on a box without root access.
I can't make it. I think you should really recheck your
configure script and sources and check whether you are
not hardcoding anything.
The thing is,
normally you specify --prefix, and everything goes
there, but your script ignores --prefix for some things
and needs stuff like --enable-bindir separately.
Why not using standard configure stuff:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables
--libexecdir=DIR program executables
architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data
architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data
--libdir=DIR object code libraries
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]
The advantage is that configure handles
cross-dependency between --prefix and any other
directive automatically, and besides it's
standard-compliant, why reinventing the wheel?
Even after I've managed to install it somehow, when
SARG: setrlimit error - Operation not permitted
SARG: File not found: /usr/local/squid/var/logs/access.log
What does the first line mean?
But the worse thing is - after running sarg the entire
contents of the sarg installation folder gets ERASED!!!
What the heck is going on??? :-)
btw, I used --prefix and all 4 custom options:
make install worked, but it's still asking for
Log in to post a comment.