Hi Jonathan,
> Thank you, Filipe. That allowed the configure script to complete
> without needing to specify any special parameters. I am not sure why
> the RPM script didn't handle it correctly.
Neither am I, but I've seen this once or twice from Red Hat packages.
> I now run into an issue whe
Thank you, Filipe. That allowed the configure script to complete without
needing to specify any special parameters. I am not sure why the RPM script
didn't handle it correctly.
I now run into an issue when running 'make' also with libconfuse:
"libgmond.c:15:21: error: confuse.h: No such file or d
Hi Jonathan,
I've seen this on Fedora and I think Red Hat. You need to create the
link manually:
# ln -s libconfuse.so.0 /usr/lib64/libconfuse.so
I'd expect the RPM install script to do this.
Filipe
--
Filipe Bonjour
In theory there is no difference between theory and practice.
libconfuse was installed via rpm and is present on my system.
rpm -qa | grep libconfuse
libconfuse-2.7-4.el6.x86_64
rpm -ql libconfuse gives me
/usr/lib64/libconfuse.so.0
/usr/lib64/libconfuse.so.0.0.0
/usr/share/doc/libconfuse-2.7
/usr/share/doc/libconfuse-2.7/AUTHORS
/usr/share/doc/libconfuse
4 matches
Mail list logo