compile error with Ruby
hi, just a quick heads up. noted the following issue with freeradius 2.1.6 when compiling. no Ruby installed - configure script WARNs and doesnt try including Ruby support only Ruby tools installed - configure thinks all is okay - make then fails because ruby.h is not present Ruby development package installed - configure says all is okay and make works (ie ruby-devel must be installed (as expected!) but if the system has only the Ruby binary installed then configure stage thinks its okay to build in Ruby support. not a show stopper because development has to be flagged on the congigure line (?) but a little quirky - i cant recall any other modules that think its all okay if just the runtime binary is present (eg openssl) alan
A.L.M.Buxey@lboro.ac.uk wrote:
(ie ruby-devel must be installed (as expected!) but if the system has only the Ruby binary installed then configure stage thinks its okay to build in Ruby support.
Ugh.
not a show stopper because development has to be flagged on the congigure line (?) but a little quirky - i cant recall any other modules that think its all okay if just the runtime binary is present (eg openssl)
The perl module does something similar. The configure script asks Perl: What command-line options do I use to build with perl? It responds: -lperl. Q: Is libperl.so installed on the system? A: No, why would it be? What's wrong with you? I've had arguments with the Debian people about this. They don't see a problem with Perl lying to you: D: But all you need to do is to install the perl-dev package! Me: Yes... but why is Perl lying to me? D: <mutters incoherently> Install perl-dev! That's it! Me: are you pretending to be dumb, or did you have to work at it? Alan DeKok.
--On Tuesday, May 26, 2009 10:37:36 AM +0200 Alan DeKok <aland@deployingradius.com> wrote:
The perl module does something similar. The configure script asks Perl: What command-line options do I use to build with perl? It responds: -lperl.
Q: Is libperl.so installed on the system? A: No, why would it be? What's wrong with you?
I've had arguments with the Debian people about this. They don't see a problem with Perl lying to you:
D: But all you need to do is to install the perl-dev package! Me: Yes... but why is Perl lying to me? D: <mutters incoherently> Install perl-dev! That's it! Me: are you pretending to be dumb, or did you have to work at it?
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. 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. 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.
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.
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Jeffrey Hutzelman