Hi Gus,<br><br>Thanks for the clue. I'll do that now.<br><br>Carolina.<br><br><div class="gmail_quote">2011/9/21 Gus Correa <span dir="ltr"><<a href="mailto:gus@ldeo.columbia.edu">gus@ldeo.columbia.edu</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Anthony, Carolina<br>
<br>
Anthony:<br>
<br>
How about non-ascii characters? e.g. Ã (A with an accent)<br>
Are they OK in Linux directory and file names?<br>
Do they require some specific locale setting, UTF-8 character set,<br>
or other?<br>
Does autoconf digest them right?<br>
<br>
Carolina:<br>
<br>
I'd stay on the safe side and stick to very conventional<br>
file and directory names made only of:<br>
1) upper and lower case letters [a to z, and A to Z, without any accents, be careful with your Brazilian ABNT/ABNT-2 keyboard!],<br>
2) digits [0 to 9],<br>
3) underscore (_) [e.g. my_file], and<br>
4) period (.) [e.g. my_program.f90]<br>
And use the slash (/) *only* for directory name separator.<br>
No blanks of course [which is a Windows thing].<br>
<br>
My two cents,<br><font color="#888888">
Gus Correa</font><div><div></div><div class="h5"><br>
<br>
Anthony Chan wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Carolina,<br>
<br>
Here are lines that in config.log shows the problem:<br>
<br>
configure:11770: gcc -c -I/home/carol/Ã rea de Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/mpl/include -I/home/carol/Ã rea de Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/mpl/include -I/home/carol/Ã rea de Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/openpa/src -I/home/carol/Ã rea de Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/openpa/src conftest.c >&5<br>
gcc: de: No such file or directory<br>
gcc: Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/mpl/include: No such file or directory<br>
gcc: de: No such file or directory<br>
gcc: Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/mpl/include: No such file or directory<br>
gcc: de: No such file or directory<br>
gcc: Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/openpa/src: No such file or directory<br>
gcc: de: No such file or directory<br>
gcc: Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/src/openpa/src: No such file or directory<br>
<br>
Notice your mpich2 source is located in "/home/carol/Ã rea de Trabalho/Mocassin/mpich2-1.4.<u></u>1p1/"<br>
which contains blank character. Many unix tools including autoconf cannot handle blanks in<br>
pathname well, so move mpich2 source tree to a directory whose pathname does NOT contain any<br>
blank or white space characters. The same for the build and install directories.<br>
<br>
A.Chan<br>
<br>
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br>
<br>
I'm trying to install mpich2-1.4.1p1 in my computer and it's not<br>
working.<br>
The following message appear:<br>
<br>
"configure: error: **** Incompatible Fortran and C Object File Types!<br>
****<br>
F77 Object File Type produced by "gfortran -O2" is : : ELF 64-bit LSB<br>
relocatable, x86-64, version 1 (SYSV), not stripped.<br>
C Object File Type produced by "gcc " is : : ERROR: cannot open `' (No<br>
such file or directory)."<br>
<br>
I have gfortran and gcc installed in my computer.<br>
<br>
I tried to use ./configure --disable-f77, because I don't require<br>
support<br>
for Fortran 77, just for Fortran 90, but it didn't work either:<br>
<br>
"Fortran 90 support requires compatible Fortran 77 support.<br>
To force the use of the Fortran 90 compiler for Fortran 77,<br>
do not use configure option --disable-f77, and set the environment<br>
variable F77 to the name of the Fortran 90 compiler, or $FC.<br>
If you do not want any Fortran support, use configure options<br>
--disable-f77 and --disable-fc."<br>
<br>
Can you help me? I don't know what to do, and I need this very<br>
quickly.<br>
<br>
Thank you for your attencion,<br>
<br>
Carolina Moura.<br>
<br>
______________________________<u></u>_________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><br>
</blockquote>
______________________________<u></u>_________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><br>
</div></div></blockquote></div><br>