Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] keyval parser: error 1 reading file mpicc-wrapper-data.txt
From: Gus Correa (gus_at_[hidden])
Date: 2011-03-28 19:25:55

Hi Ralph

Thank you for your attention to this again.
More inline.

Ralph Castain wrote:
> I've never seen that problem before,
> and I wasn't able to track down what "keyval parser" is being referenced. :-(

There was a posting in 2006, but somehow it was hijacked and
there is no clear solution, only several suggestions
to do a clean reinstall:

Just in case I did once again a fully clean build.
Downloaded the tarball again, untarred, wiped off the old
build and install directories, everything from ground up.

As before, the error disappeared ... :)
but who knows for how long ... :(

Here is mpicc from both new builds (gnu only, and gnu+intel)
behaving well now:

$ /home/soft/openmpi/1.4.3/gnu/bin/mpicc -o hello_c hello_c.c ; ll
-rwxrwxr-x 1 gus gus 9621 Mar 28 18:24 hello_c
Mon Mar 28 18:24:54 EDT 2011

$ /home/soft/openmpi/1.4.3/gnu-intel/bin/mpicc -o hello_c hello_c.c ; ll
hello_c ; date
-rwxrwxr-x 1 gus gus 9621 Mar 28 18:26 hello_c
Mon Mar 28 18:26:25 EDT 2011

> I have a very simple suggestion, however.
> Just edit the .txt files and remove the comments.

If the error comes back, I will remove the comments,
and see how it goes.
Note that in the 2006 posting above the person seems to have a file
with no comments.

However, it worked with the comments before, it works with the comments
in another cluster.
Why would the parser get confused by the comments then?

Or could it hit something else, and perhaps issue a misleading error
message suggesting that the problem is in the comment line?
I tried to look at the parser code, but it may be beyond my competence.

I wonder if there may be an issue in the file,
perhaps with line terminators or some funny hidden characters,
but I did not edit the file at all.
This is all Linux, nothing was edited or came from a Mac or Windows either.

Once a user here edited his source files on Windows,
copied over to our old cluster,
and the compilers on Linux would go south on those line terminators,
no error message, no nothing.

> If you are getting a workable executable,
> then I would think it must be reading past the error.
> Otherwise, it wouldn't know what linker and CPP flags to
> apply to generate the executable.

Yes, that is reassuring.

> But to be safe, like I said, just remove the comments.

Will do, if the problem comes back.


> On Mar 28, 2011, at 3:18 PM, Gus Correa wrote:
>> Hi Ralph, list
>> Sorry, I spoke too soon.
>> The problem still seems to be there, in all compiler wrappers
>> (I.e. it probably tracks down to the opal_wrapper):
>> $ mpicc -o hello_c hello_c.c
>> [mycomputer.mydomain:09148] keyval parser: error 1 reading file /my/path/to/openmpi/1.4.3/gnu-intel/openmpi/mpicc-wrapper-data.txt at line 1:
>> # There can be multiple blocks of configuration data, chosen by
>> ***
>> Somehow the keyval parser fails to read the first (comment)
>> line of mpicc-wrapper-data.txt.
>> The same thing happens to the other mpi compiler wrappers.
>> However, the compilation proceeds and a working executable is produced.
>> I wonder if the options in mpicc-wrapper-data.txt are being read by mpicc, and likewise for the other compiler wrappers.
>> Any clues on how I can get to the bottom of this issue?
>> Anything in the environment, or in the actual mpicc-wrapper-data.txt file that could cause this?
>> Anything in the parser code?
>> We have Linux CentOS 5.5 x86_62 with gcc 4.1.2.
>> I built OpenMPI both with gfortran and Intel Ifort 12.0.0.
>> Same problem on both builds.
>> Thank you,
>> Gus Correa
>> Ralph Castain wrote:
>>> Good to hear (well, all except that bit about the conspiracy...)!
>>> On Mar 24, 2011, at 12:45 PM, Gus Correa wrote:
>>>> Hi Ralph, list
>>>> Just for the record:
>>>> I configured and built OpenMPI 1.4.3 with gcc/g++/ifort again today.
>>>> The mpicc/opal_wrapper parser error disappeared.
>>>> The whole problem must have been some computer daemon spell.
>>>> Other than my growing feeling that flipping bits and logic gates
>>>> have fun conspiring against my sanity, all is well now.
>>>> Thank you,
>>>> Gus Correa
>>>> Gus Correa wrote:
>>>>> Ralph Castain wrote:
>>>>>> On Mar 23, 2011, at 3:19 PM, Gus Correa wrote:
>>>>>>> Dear OpenMPI Pros
>>>>>>> Why am I getting the parser error below?
>>>>>>> It seems not to recognize comment lines (#).
>>>>>>> This is OpenMPI 1.4.3.
>>>>>>> The same error happens with the other compiler wrappers too.
>>>>>>> However, the wrappers compile and produce an executable.
>>>>>> No idea - I just tested it and didn't get that error. Did you configure this for script wrapper compilers instead of binaries?
>>>>>>> Thank you,
>>>>>>> Gus Correa
>>>>>>> Parser error:
>>>>>>> $ mpicc hello_c.c
>>>>>>> [myhost.mydomain:06489] keyval parser: error 1 reading file /my/path/to/openmpi/share/openmpi/mpicc-wrapper-data.txt at line 1:
>>>>>>> # There can be multiple blocks of configuration data, chosen by
>>>>> Thank you, Ralph.
>>>>> I have two OpenMPI 1.4.3 builds on this cluster.
>>>>> One with gcc/g++/gfortran,
>>>>> the other with gcc/g++ and Intel ifort (12.0.0).
>>>>> The Gnu-only works right, no parser error.
>>>>> The error is restricted to the Gnu-Intel combination.
>>>>> Awkward.
>>>>> Both were configured with these parameters:
>>>>> --prefix=${MYINSTALLDIR} \
>>>>> --with-libnuma=/usr \
>>>>> --with-tm=/opt/torque/2.4.11 \
>>>>> --with-openib=/usr \
>>>>> --enable-static
>>>>> The opal_wrapper is a binary in both cases.
>>>>> To make things more confusing, on another cluster with (older)
>>>>> Intel compiler 10.1.017 the Gnu+Intel build of OpenMPI 1.4.3
>>>>> doesn't have this parser error.
>>>>> Thank you,
>>>>> Gus Correa
>> _______________________________________________
>> users mailing list
>> users_at_[hidden]
> _______________________________________________
> users mailing list
> users_at_[hidden]