Hi there. As indicate in this page: http://gridengine.sunsource.net/howto/lam-integration/lam-integration.html lam-mpi can be tightly integrated with Sun Grid Engine. Althoug SGE is not yet part of the gentoo portage tree, one can install it. I've made the patch for lam-7.0.6 ebuild but the same can be applied on lam-7.0.4 and lam-7.1.1. It is a fact that lam team introduced the same code modification starting from lam-7.1.2 (you can read their comments before the setsid() instruction). I modified the ebuild introducing sge in IUSE variable, even if sge, so that one can choose if patch or not. It is safe to patch anyway, so you can choose to keep the conditional patching out of the ebuild. d # emerge --info Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.14.2-smp i686) ================================================================= System uname: 2.6.14.2-smp i686 Intel(R) Xeon(TM) CPU 3.06GHz Gentoo Base System version 1.6.15 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib/X11/xkb /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X apache2 apm arts avi berkdb bitmap-fonts cli crypt cups dlloader dri eds emboss encode esd foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg kde libg++ libwww mad mikmod motif mp3 mpeg mysql ncurses nls nptl ogg opengl oss pam pcre pdflib perl png pppd python qt qt3 qt4 quicktime readline reflection session spell spl ssl tcpd threads truetype truetype-fonts type1-fonts udev vorbis xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 93111 [details, diff] this is the patch for lam-7.0.6, enables sge tight integration
Created attachment 93112 [details] this is the modified ebuild Note that I added some KEYWORDS that were not into the original ebuild...
Is there a reason to add this, now that there's a working lam-mpi 7.1.2 in the tree?
(In reply to comment #3) > Is there a reason to add this, now that there's a working lam-mpi 7.1.2 in the > tree? > I think this would be a useful minor change for previous lam releases while users wait the 7.1.2 being stable (or at least widely tested) on their architectures. Also, if someone is interested in using SGE without upgrading lam-mpi, he can just re-emerge it (with this patch). Consider also that there are people that don't trust in latest versions... BTW, I've done this some time before lam-7.1.2 included itself, and I started submitting bugs only recently.
We'd have to bump to a new revision for the patch and ~arch it anyway, wouldn't be any faster to get to stable ... If you run into some issues with 7.1.2 that give you a really good reason to not use it, reopen this and we can think about it some more.
(In reply to comment #5) > We'd have to bump to a new revision for the patch and ~arch it anyway, wouldn't > be any faster to get to stable ... > > If you run into some issues with 7.1.2 that give you a really good reason to > not use it, reopen this and we can think about it some more. > I'll test lam-7.1.2 on all archs I can but I would like to add something to this discussion (even if the bug has been resolved). If one doesn't specify USE=sge, the patch won't be applied and there's no need to ~arch the ebuilds. If one specifies USE=sge, well, since sge is not yet part of gentoo portage tree, a einfo message like "Warning, you are going to install lam-mpi coupled with a software that has not been tested by gentoo team, use at your own risk" can be added... I mean, using with sun grid engine installed would be ~arch anyway...
