| 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 did all wrong. You forgot your CC/CXX/F77/F90 variable in<br> your command. Do<br><br> bash: export CC="gcc -m32"<br> tcsh: setenv CC "gcc -m32"<br><br> for all CC/CXX/F77/F90 before configure. Or you can set these<br> |
|---|
| 3 | variables as part of your configure command,<br> e.g. configure CC="gcc -m32" CXX="g++ -m32" ..... --prefix=...<br> Make sure your 64bit OS has 32-bit libraries installed, check<br> with your system admin.<br> |
|---|
| 4 | <br> A.Chan<br></blockquote></div><br>Thank you for your detailed letter. I did everything like you had recommended. If I set under 64-bit OS >export CC="gcc -m64" (the same for CXX/F77/F90) it configured without any problems. But if I set >export CC="gcc -m32" it wrote by configuration:<br> |
|---|
| 5 | "checking for gcc... -m32<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 didn't create 32-bit binaries on a 64-bit OS. <br> |
|---|
| 6 | Under 32-bit OS it was quite the contrary: if I set -m32 it was OK; if I set -m64 - configure error.<br>By such compilation the velosity of my multiprocess calculations with mpich2 was as usual quicklier under 32-bit OS than under 64-bit one. The same process needs 11 min under 32-bit and 12 min under 64-bit OS. So, I think, the reason doesn't lie in the procedure of configuration before installation of mpich2. Without set of -m32 or -m64 the results of installation of mpich2 were the same.<br> |
|---|
| 7 | <br>Alex Mazheika<br> |
|---|
