[torqueusers] TORQUE 4.0 and hwloc

Gabe Turner gabe at msi.umn.edu
Wed Apr 4 11:09:47 MDT 2012


On Wed, Apr 04, 2012 at 05:02:19PM +0000, DuChene, StevenX A wrote:
[snip]
> And on the line that actually calls configure from within the spec file I see:
> 
> %configure --includedir=%{_includedir}/%{name} --with-default-server=%{torque_server} \
>     --with-server-home=%{torque_home} --with-sendmail=%{sendmail_path} \
>     --disable-dependency-tracking %{ac_with_gui} %{ac_with_scp} %{ac_with_syslog} \
>     --disable-gcc-warnings %{ac_with_munge} %{ac_with_pam} %{ac_with_drmaa} \
>     --disable-qsub-keep-override %{ac_with_blcr} %{ac_with_cpuset} %{ac_with_spool} %{?acflags}
> 
> So is "%bcond_with    cpuset" supposed to turn it off or on? If it is
> supposed to turn it on then as I said before it is not working.
> 
> Now I know I can just alter the spec file to hard code turn it on with
> "-enable-cpuset" or "-enable-libcpuset" or possibly
> "--enable-geometry-requests" but I am trying to understand the logic of
> what I see someone cleverly added into the torque spec file as
> distributed with the torque-4.0 sources.

It looks to me like the spec file is supporting the --with option to
rpmbuild. So cpuset will be enabled as a configure option if you pass
'--with cpuset' to rpmbuild. Is that what you are already trying?


-- 
Gabe Turner                                             gabe at msi.umn.edu
HPC Systems Administrator,
University of Minnesota
Supercomputing Institute                          http://www.msi.umn.edu


More information about the torqueusers mailing list