Version 3.0.9 has been released

Alan DeKok aland at deployingradius.com
Thu Jul 9 13:43:03 CEST 2015


On Jul 8, 2015, at 8:39 PM, Michael Ströder <michael at stroeder.com> wrote:
> 
> An RPM sanity check on openSUSE build service checks whether run-time linker
> paths point to disallowed locations.

  Hmm... the configure checks are just checks to see if a library exists in that directory.  If the directory doesn't exist, it shouldn't be listed in the make file, and it shouldn't affect run-time linking.

  There are a number of other places where library paths are hard-coded in "configure" scripts.  And they don't cause problems.

  Those paths are hard-coded because of common system breakage.  Libraries are installed in non-standard locations, and the administrator doesn't have a clue.  The configure scripts are supposed to find things in the system... which is what they do.  You can't rely on admins to always pass *all* of the correct library paths.  If you could depend on that, you could depend on sane systems, and the "configure" scripts wouldn't be necessary.

  What's really happening behind the scenes?

  Alan DeKok.




More information about the Freeradius-Users mailing list