From: Mark T. <ma...@di...> - 2013-03-26 20:11:17
|
Hi Demian, Yep, your summary below is correct (same as the official release, but built with an earlier GLIBC). Actually the platform it broke on was Debian stable and Debian testing, so maybe RHEL/CentOS would have been fine anyway... I haven't got a full set up running under Windows, but I was just able to build a plausible-looking browse database under Windows by replacing the SQLite jar with the new one and running the bat file. Likewise under a 32-bit machine here. Thanks, Mark Demian Katz <dem...@vi...> writes: > I swapped in the new .jar on my Ubuntu 12.04 test system and ran the > standard test suite (which includes building and testing a small > AlphaBrowse index to make sure all the key features like authority > cross-references work properly) and everything passed. > > Just to make sure I understand the situation correctly: the official > release is compiled with a version of GLIBC that causes it to break on > platforms with an older GLIBC (CentOS, RHEL). You've just done a > custom compile using an older GLIBC to work around this problem. > > If my understanding is correct, it's probably okay to commit this new > library to the trunk to work around the bugs in the earlier version... > but are there any concerns about 32-bit vs. 64-bit compatibility? Has > anybody tested under Windows yet? I can do some more testing with > Windows and 32-bit VMs if necessary (though it will have to wait until > next week). -- Mark Triggs <ma...@di...> |