Thanks Chris for posting this - I've never tried to build OGS outside of our machines or EC2 images.
And we needed to use "BerkeleyDB version 4.4.20" because the on-disk data structure is not compatible across different releases of Berkeley DB - it's not Oracle's fault, but it's just that it is not engineered that way. And in order to read back configuration & jobs from an existing SGE installation, we need BDB 4.4.x -- we think compatibility with older SGE versions is more important and thus we try not to break it if possible. For a fresh install, on-disk data is not an issue, and one can safely use newer releases of Berkeley DB. I modified OGS to use newer releases of Berkeley (including Berkeley DB 11g R2), but the change and other changes were not included in GE 2011.11 because we needed to release "something" for SC11 and thus non critical features were all skipped - I am going to integrate some of the changes back into trunk soon. Rayson On Thu, Jan 12, 2012 at 5:45 PM, Chris Dagdigian <d...@sonsorol.org> wrote: > > Tried to reverse engineer my crusty old build environment into something > that I (or even others) can actually replicate or follow. > > Going to try similar for 32bit binaries as well as document the process for > RHEL/CentOS 5.x based systems in the near future... > > Short link: > http://biote.am/6y > > Long link: > http://bioteam.net/2012/01/building-open-grid-scheduler-on-centos-rhel-6-2/ > > Feedback welcome. > > -dag > > > > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
