| 1 | <div><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex"> |
|---|
| 2 | You can use a 64-bit OS and set the environment variables CC, CXX, F77,<br> F90 to "gcc -m32", "g++ -m32", "gfortran -m32", "gfortran -m32". Then<br> run configure, make clean, make, make install as usual. That will create<br> |
|---|
| 3 | 32-bit binaries on a 64-bit OS. See how that performs compared with<br> regular 64-bit binaries on the 64-bit OS.<br><br> Rajeev<br></blockquote></div><br>I used 64-bit OS and compiled mpich2 like you had described, before installation I set: <br> |
|---|
| 4 | under bash >set gcc -m64 (or g++,gfortran)<br>under tcsh >setenv gcc -m64<br>With -m32 I have done analogously. And no change was considered. Under 32-bit system my processes last quicklier.<br>If I set ">set CC -m64" (CXX, F77, F90), it writes by configuration:<br> |
|---|
| 5 | "checking for gcc... -m64<br>checking for C compiler default output file name... <br>configure: error: C compiler cannot create executables<br>See `config.log' for more details."<br>So it don't want to run qiucklier under 64-bit than under 32-bit OS by any setting of environment variables. It seems me that maybe the reason lies in my Espresso-program (<a href="http://www.pwscf.org">www.pwscf.org</a>), because I didn't try to run any other multiple process through mpich2, only Espresso. Or is there any other ideas?<br> |
|---|
| 6 | <br>Alex<br> |
|---|
