Andriy, I would suggest looking at the 2.3 version of this code. The select/bgq plugin doesn't exist anymore (it doesn't do anything in 2.2 as you have noticed) but the select/bluegene plugin requires a c++ compiler to be built. The c++ is only for the bgq side of things. All the select plugins are built to allow multi-cluster operation, so if you aren't using the slurmdbd then it isn't that big of a deal, you can make it so you just don't build the bluegene plugin (unless of course you need it for a bluegene cluster).
So this patch will allow you to avoid c++ for now, but in 2.3 the problem is not this easy to avoid. There are a couple of options. One being just don't build the bluegene plugin if a c++ compiler doesn't exist, and if that is the case how should things fail? I would expect at configure time. >From my understanding we need a c++ compiler to link things correctly when >linking to other c++ .o files, which are now created in the bluegene plugin on >bgq systems. When you have anything setup to compile with c++ it appears the >automake tools always make the linker c++ even if you aren't linking to any >c++. If you have any ideas on the matter let us know. Danny > -----Original Message----- > From: [email protected] [mailto:owner-slurm- > [email protected]] On Behalf Of Andrej N. Gritsenko > Sent: Thursday, April 07, 2011 3:48 AM > To: [email protected] > Subject: [slurm-dev] patch to avoid c++ compiler requirement. > > Hello there! > > Compiling source of SLURM 2.2.3 requires c++ compiler but really it > isn't required because file src/plugins/select/bgq/select_bgq.cc isn't > C++ source file but plain C instead so to get rid of that requirement is > simple: > 1) rename src/plugins/select/bgq/select_bgq.cc into select_bgq.c; > 2) adapt Makefile.am and bgq.h in src/plugins/select/bgq/ directory to > that change. > Patch attached. Thank you. > > Andriy.
