[mpich-discuss] Compilation of MPCH2-1.2.1 is failing onSunSolaris 10 (Sparc)

Arvind Petaru arvindpetaru at gmail.com
Wed Jan 27 16:07:38 CST 2010


Dave,

   Thanks!!
   Compilation was sucessful.

Cheers,

-Arvind

On Mon, Jan 25, 2010 at 5:25 PM, Dave Goodell <goodell at mcs.anl.gov> wrote:

> I don't think it matters what shell you used to invoke "./configure".  The
> shell that actually interprets the command is determined by the shebang line
> at the top of configure, "#! /bin/sh".  AFAIK, the Solaris "/bin/sh" is
> _not_ bash or zsh, so it will not understand the "export VAL=var"
> convenience syntax.
>
> You can test this by running the following sequence of commands:
>
> -------8<-------
> /bin/sh
> export FOO=" -lpthread"
> -------8<-------
>
> You should get a very similar error message to the one you received when
> running configure.
>
> The reason that you still saw the problem even after modifying configure is
> that you only attempted to re-make.  You need to modify
> /petara1/mpich2/mpich2-1.2.1/src/mpid/ch3/configure as I indicated earlier,
> then run configure, then run make.  Changes to configure after configure has
> been run won't have any effect.
>
> -Dave
>
>
> On Jan 22, 2010, at 10:40 AM, Arvind Petaru wrote:
>
> To add on more.....
>> I was compiling on bash shell.......and i tried below commands on bash
>> shell prompt and it works fine, so I don't think MY_EXPORTED_LIBS is
>> creating problem here:
>>
>> lperf011-root>
>> lperf011-root> VAR=abcd
>> lperf011-root> echo $VAR
>> abcd
>> lperf011-root>
>> lperf011-root> export TMPVAR="$VAR"
>> lperf011-root> echo $TMPVAR
>> abcd
>> lperf011-root>
>> lperf011-root>
>>
>> Also, there was a typo in my earlier mail for point 2, where it should be
>> "--with-device=ch3:sock" instead of "--with-devicech3:sock", missed a "="
>> symbol.....
>>
>> -Arvind
>> On Fri, Jan 22, 2010 at 11:29 AM, Arvind Petaru <arvindpetaru at gmail.com>
>> wrote:
>> Hi Dave,
>>
>>    Thanks for your suggestion.
>>    I tried compiling following your suggestion and I still see the same
>> errors.
>>
>> Steps I followed:
>> ============
>>
>> 1> Removed everything from previous tmp build directory (i.e.,
>> /tmp/petara1/mpich2-1.2.1) and freshly created it again.
>>
>> 2> Configured as below  :-
>>     /petara1/mpich2/mpich2-1.2.1/configure -prefix=/mpich2-install
>> --with-devicech3:sock 2>&1 | tee c.txt
>>
>> 3> As ususal I saw the below error in c.txt file.
>>    /petara1/mpich2/mpich2-1.2.1/src/mpid/ch3/configure: MY_EXPORTED_LIBS=
>> -lpthread: is not an identifier
>>
>> 4> Modified file (
>> /tmp/petara1/mpich2-1.2.1/src/mpid/ch3/configure.lineno, line 7259 ) as
>> suggested by you as:
>>     MY_EXPORTED_LIBS="$LIBS"
>>     export MY_EXPORTED_LIBS
>>
>> 5> Tried compiling again as:
>>     make 2>&1 | tee m.txt
>>
>> 6> Fails with same reason
>>
>> Attaching new c.txt, m.txt and configure.log files.
>>
>> Cheers,
>>
>> -Arvind
>>
>> On Thu, Jan 21, 2010 at 6:06 PM, Dave Goodell <goodell at mcs.anl.gov>
>> wrote:
>> It looks like the CH3 configure step didn't entirely complete, so a bunch
>> of configure-generated files are missing.  Line 454 of your previously
>> attached c.txt is particularly suspect:
>>
>> --------8<--------
>> /petara1/mpich2/mpich2-1.2.1/src/mpid/ch3/configure: MY_EXPORTED_LIBS=
>> -lpthread: is not an identifier
>> --------8<--------
>>
>> Aha! As I'm writing this I think I see the problem.  There's a
>> bash/zsh-ism in src/mpid/ch3/configure.in, line 311:
>>
>> --------8<--------
>> export MY_EXPORTED_LIBS="$LIBS"
>> --------8<--------
>>
>> I don't have the time to do it today, but I can try to build you a release
>> tarball with a fixed version tomorrow.  The fix should be to separate out
>> the assignment from the export:
>>
>> --------8<--------
>> MY_EXPORTED_LIBS="$LIBS"
>> export MY_EXPORTED_LIBS
>> --------8<--------
>>
>> You are welcome to make that change yourself, but you'll need to
>> regenerate the configure from the configure.in by running
>> "./maint/updatefiles" in the source tree, which itself requires particular
>> versions of the autotools and some other utilities.  Alternatively, you can
>> edit "src/mpid/ch3/configure" in the build tree directly, but I can't tell
>> you exactly which line to change.  You'll just have to search for
>> MY_EXPORTED_LIBS and make the change wherever it is.
>>
>> -Dave
>>
>>
>> On Jan 21, 2010, at 3:34 PM, Arvind Petaru wrote:
>>
>> same errors...
>>
>> On Thu, Jan 21, 2010 at 4:34 PM, Rajeev Thakur <thakur at mcs.anl.gov>
>> wrote:
>> Does it give the same error or a different error?
>>
>> Rajeev
>>
>> From: mpich-discuss-bounces at mcs.anl.gov [mailto:
>> mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Arvind Petaru
>> Sent: Thursday, January 21, 2010 3:32 PM
>>
>> To: mpich-discuss at mcs.anl.gov
>> Subject: Re: [mpich-discuss] Compilation of MPCH2-1.2.1 is failing
>> onSunSolaris 10 (Sparc)
>>
>> Forgot to mention earlier....I tried that too(--with-device=ch3:sock) and
>> it fails........
>>
>> -Arvind
>>
>> On Thu, Jan 21, 2010 at 4:27 PM, Rajeev Thakur <thakur at mcs.anl.gov>
>> wrote:
>> Can you try configuring with --with-device=ch3:sock (followed by make and
>> make install) and see if that works?
>>
>> Rajeev
>>
>> From: mpich-discuss-bounces at mcs.anl.gov [mailto:
>> mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Arvind Petaru
>> Sent: Thursday, January 21, 2010 2:19 PM
>> To: mpich-discuss at mcs.anl.gov
>> Subject: [mpich-discuss] Compilation of MPCH2-1.2.1 is failing on
>> SunSolaris 10 (Sparc)
>>
>>
>> Hi,
>>
>>  I'm new to MPI programming.
>>  I installed MPICH2 on my Sun Solaris 10, SPARC version and tried to
>> configure & compile it on this machine.
>>  I was not able to compile it successfully and it throws lot of errors.
>> Not sure what could be the problem (or) if I am missing something.
>>  I'd appreciate if someone can help me in this regards.
>>
>>  Attaching c.txt, m.txt, config.log, config.system and config.status files
>> for your reference.
>>
>>   Let me know if you need any other info.
>>
>> --
>> Cheers,
>>
>> -Arvind
>>
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>>
>>
>>
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>>
>>
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>>
>>
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20100127/4782a625/attachment-0001.htm>


More information about the mpich-discuss mailing list