compile error with Ruby
Alan DeKok
aland at deployingradius.com
Wed May 27 08:55:37 CEST 2009
Jeffrey Hutzelman wrote:
> Clearly, the tool that tells you what libraries to use should be part of
> the -dev package, so it's not present when the libraries aren't.
Yeah, well...
> Unfortunately, in the case of perl that's difficult because the tool in
> question is perl itself, combined with a core module (Config) which must
> be present in order for perl to function. Perl is a little too
> integrated with its own build system, and can't really fathom the idea
> that you'd build libperl but install perl without it.
Yes. That needs fixing upstream, I think.
> However, that should be the exception rather than the rule. So, the
> equivalent problem with Ruby may in fact be a minor packaging problem,
> rather than the can of worms that it is with Perl.
I've added some additional checks that *should* help work around this
issue. See the recent git log for polite comments. :)
Alan DeKok.
More information about the Freeradius-Devel
mailing list