Hi Dave, > I built it straight from the tarball (with no configure options) and > bmc-info (for instance) worked.
Great! > I then built the RPM, and got the same failure as with the current > release. That is indeed interesting. My only guess is that perhaps a lingering old freeipmi.tar.gz src file was picked up during the rpm build? But then again, I gave you a new version number, so that's probably not it. Hmmmm. How are you building the rpm? > I'm off now until Wednesday, but I can look at it again sometime next > week. Thanks. PLMK if you figure out something. Al On Thu, 2009-05-21 at 16:28 +0100, Dave Love wrote: > Al Chu <ch...@llnl.gov> writes: > > > Hey Dave, > > > > I think I may have fixed a problem that may be the problem for atleast > > one of the problems you listed below. Could you check out this tar.gz > > and let me know that it works? > > It looks as if you've spotted the problem, but I'm a bit confused... I > built it straight from the tarball (with no configure options) and > bmc-info (for instance) worked. I then built the RPM, and got the same > failure as with the current release. The obvious difference between the > two binaries was that one that worked was statically linked, and the > other dynamically, though I'm not sure why, and I'm pretty sure I was > picking up the new shared library. > > I hadn't realized that it would have worked previously if I removed the > openipmi kernel modules, but we need to be able to run ipmitool as well, > so they will normally be loaded. > > I'm off now until Wednesday, but I can look at it again sometime next > week. -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-users
