[mpich-discuss] mpich-1.4.1p1

[Gus Correa]

Thank you Anthony and Reuti for the insightful comments, as usual.

Yes Reuti, I forgot to mention "+" and "-" characters, which we
also use in file and directory names.

I am still confused about autoconf, locale, and the use of non-ascii
characters [such as accented vowels] in file and directory names
being processed by autoconf and friends.
I'd guess this matters for people in Brazil [Carolina],
Germany [Reuti], etc.
I've always avoided those characters, which is what I suggested
to Carolina.
However, are those characters OK to use or not?
What does LANG=C entail in terms of the admissible characters?

Anyway, maybe I am going astray, way far from MPICH ... :)

Regards,
Gus Correa


Anthony Chan wrote:
> Configure (or any autoconf generated script) assumes C locale, see
> 
> http://www.gnu.org/software/autoconf/manual/autoconf.html#Special-Shell-Variables
> 
> Search for LANG or LC_ALL...
> 
> ----- Original Message -----
>> Hi,
>>
>> Am 21.09.2011 um 21:10 schrieb Gus Correa:
>>
>>> Anthony:
>>>
>>> How about non-ascii characters? e.g. � (A with an accent)
>> about this I wondered too. Also in respect to a linked in RPATH or
>> RUNPATH in the final application which one can check with `readelf -d
>> program`. Does the ability to execute the application then depend on
>> the setting of the locale?
>>
>>
>>> Are they OK in Linux directory and file names?
>>> Do they require some specific locale setting, UTF-8 character set,
>>> or other?
>>> Does autoconf digest them right?
>>>
>>> Carolina:
>>>
>>> I'd stay on the safe side and stick to very conventional
>>> file and directory names made only of:
>>> 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!],
>>> 2) digits [0 to 9],
>>> 3) underscore (_) [e.g. my_file], and
>> 3a) a dash and plus (-+) if it's not the first character. My users in
>> computational chemistry use them quite often without known issues.
>>
>>
>>> 4) period (.) [e.g. my_program.f90]
>>> And use the slash (/) *only* for directory name separator.
>>> No blanks of course [which is a Windows thing].
>> 5) No colon : on a Mac in a terminal. It will show up in the GUI as
>> slash. Despite working it's confusing. Origin is that the colon was
>> (is) the directory separator in HFS (Hierarchical File System) used
>> there and translates from the GUI ":" to a terminal "/" and is
>> rejected because of this in the opposite way.
>>
>> 6) Default on a Mac is not to distinguish between upper and lower
>> case, even in a terminal. Unless you format the partion in a different
>> way to honor it or as Unix FS.
>>
>> --Reuti
>>
>>
>>> My two cents,
>>> Gus Correa
>>>
>>> Anthony Chan wrote:
>>>> Carolina,
>>>> Here are lines that in config.log shows the problem:
>>>> configure:11770: gcc -c -I/home/carol/�rea de
>>>> Trabalho/Mocassin/mpich2-1.4.1p1/src/mpl/include
>>>> -I/home/carol/�rea de
>>>> Trabalho/Mocassin/mpich2-1.4.1p1/src/mpl/include
>>>> -I/home/carol/�rea de
>>>> Trabalho/Mocassin/mpich2-1.4.1p1/src/openpa/src -I/home/carol/�rea
>>>> de Trabalho/Mocassin/mpich2-1.4.1p1/src/openpa/src conftest.c >&5
>>>> gcc: de: No such file or directory
>>>> gcc: Trabalho/Mocassin/mpich2-1.4.1p1/src/mpl/include: No such file
>>>> or directory
>>>> gcc: de: No such file or directory
>>>> gcc: Trabalho/Mocassin/mpich2-1.4.1p1/src/mpl/include: No such file
>>>> or directory
>>>> gcc: de: No such file or directory
>>>> gcc: Trabalho/Mocassin/mpich2-1.4.1p1/src/openpa/src: No such file
>>>> or directory
>>>> gcc: de: No such file or directory
>>>> gcc: Trabalho/Mocassin/mpich2-1.4.1p1/src/openpa/src: No such file
>>>> or directory
>>>> Notice your mpich2 source is located in "/home/carol/�rea de
>>>> Trabalho/Mocassin/mpich2-1.4.1p1/"
>>>> which contains blank character. Many unix tools including autoconf
>>>> cannot handle blanks in
>>>> pathname well, so move mpich2 source tree to a directory whose
>>>> pathname does NOT contain any
>>>> blank or white space characters. The same for the build and install
>>>> directories.
>>>> A.Chan
>>>> ----- Original Message -----
>>>>> Hello,
>>>>>
>>>>> I'm trying to install mpich2-1.4.1p1 in my computer and it's not
>>>>> working.
>>>>> The following message appear:
>>>>>
>>>>> "configure: error: **** Incompatible Fortran and C Object File
>>>>> Types!
>>>>> ****
>>>>> F77 Object File Type produced by "gfortran -O2" is : : ELF 64-bit
>>>>> LSB
>>>>> relocatable, x86-64, version 1 (SYSV), not stripped.
>>>>> C Object File Type produced by "gcc " is : : ERROR: cannot open `'
>>>>> (No
>>>>> such file or directory)."
>>>>>
>>>>> I have gfortran and gcc installed in my computer.
>>>>>
>>>>> I tried to use ./configure --disable-f77, because I don't require
>>>>> support
>>>>> for Fortran 77, just for Fortran 90, but it didn't work either:
>>>>>
>>>>> "Fortran 90 support requires compatible Fortran 77 support.
>>>>> To force the use of the Fortran 90 compiler for Fortran 77,
>>>>> do not use configure option --disable-f77, and set the environment
>>>>> variable F77 to the name of the Fortran 90 compiler, or $FC.
>>>>> If you do not want any Fortran support, use configure options
>>>>> --disable-f77 and --disable-fc."
>>>>>
>>>>> Can you help me? I don't know what to do, and I need this very
>>>>> quickly.
>>>>>
>>>>> Thank you for your attencion,
>>>>>
>>>>> Carolina Moura.
>>>>>
>>>>> _______________________________________________
>>>>> mpich-discuss mailing list mpich-discuss at mcs.anl.gov
>>>>> To manage subscription options or unsubscribe:
>>>>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>>> _______________________________________________
>>>> mpich-discuss mailing list mpich-discuss at mcs.anl.gov
>>>> To manage subscription options or unsubscribe:
>>>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>> _______________________________________________
>>> mpich-discuss mailing list mpich-discuss at mcs.anl.gov
>>> To manage subscription options or unsubscribe:
>>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>>
>> _______________________________________________
>> mpich-discuss mailing list mpich-discuss at mcs.anl.gov
>> To manage subscription options or unsubscribe:
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
> _______________________________________________
> mpich-discuss mailing list     mpich-discuss at mcs.anl.gov
> To manage subscription options or unsubscribe:
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss