Hello all, pardon a bit ambiguous and perhaps a bit poetic subject. I've noticed following # ./configure --enable-intf-open --enable-intf-bmc ; doesn't result in what I'd expected. That is enabling interface BMC and OpenIPMI. I've filled bug for the former, because there is a bug in configure.in which disables BMC interface on SPARC platform. Yes, I do dare call it a bug, because that's what it is. The latter, OpenIPMI, should work automagically. That is, if foo.h is not found, then try bar.h, then try something else, and if everything else fails, use "internal" header file. That's what configure output tells you anyway. None the less, you'll end up with ``open: no'' and OpenIPMI interface doesn't get compiled in. Actually, I'm going to fill artifact(why SF.net, why? I mean, omg!) as well.
Now, when I say, execute, # ./configure --enable-intf-bmc --enable-intf-open ; shouldn't I get what I want? And if something is missing, say header files, shouldn't I be told about it with # ./configure; crashing big time, eg. like when no C compiler could be found? I believe this should be the very same case. I haven't investigated this deeply (yet). There are per-os-type defaults which are great. And they should be over-ridable. However, it seems they're not. What do you think; bug or feature? Regards, Z. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
