Build issues - library paths, and debian pkg format
aland at deployingradius.com
Fri Dec 5 20:37:30 CET 2014
On Dec 5, 2014, at 1:08 PM, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> First, the libraries are getting the wrong paths again. I've
> been building over the last few days and have to run from within
> the build directory (even after --enable-developer=no and make
> install) otherwise I get something like
Hmm… I don’t think anything changed in the build system. And it works find for my systems.
> /etc/freeradius/mods-enabled/cache_eap: Failed to link to module 'rlm_cache': build/lib/.libs/rlm_cache_rbtree.so: cannot open shared object file: No such file or directory
Is it *only* that file, or is it other modules, too?
If it’s only that file, then the issue is the build for that file. If it’s other modules, then the entire build system needs fixing.
> I've just build a debian package, and get the same thing trying to
> run the installed binary, so something's not building right. I
> seem to remember it coming up before, but can't find what the
> solution was at the time.
> Have I missed something obvious, or is something broken?
The *installed* modules should be the ones which link to the installed modules...
> Second, debian/source/format contains "3.0 (quilt)" which means
> that the debian build wants to find a tarball to create a diff. It
> can't find a tarball, so crashes out.
> Any reason not to set this to "3.0 (native)”?
The file was added recently. Is it needed, or can we just delete it?
> (I believe that's generally frowned upon for official Debian
> packages as they want an upstream tarball to diff against, but for
> the upstream distribution it doesn't make much sense...)
More information about the Freeradius-Devel