May 2022 - discuss - mailman3.cels.anl.gov

libfabric failure during mpich install
by Marshall Tabetah 06 May '22

06 May '22

Hello, Team As I attempted to configure mpich-4.0.2 in my cygwin terminal, everything went on well until it failed to configure libfabric. The following error message was thus released upon termination. error: libfabric only builds on Linux, OS X, and FreeBSD. When I find out more information about libfabric, it seems it has support for Windows, so I do not surely know where the error comes from. Anyway, I hereby attach the files that communicate the status of the attempted configuration. Files that are not attached are those that were not produced. I appreciate further discussion/orientation. Cheers, Marshall

1 0

Re: [mpich-discuss] [EXTERNAL] Re: error building cuda from yaksa
by Allen McIntosh 02 May '22

02 May '22

Installing the libtool-bin package also made the problem go away. (This was an Ubuntu system. The package name may be different on another distribution.) On 5/2/22 2:02 PM, Allen McIntosh wrote: > That was what I thought also. Unfortunately this doesn't work. The > purpose of setting $LIBTOOL_VERSION is to embed the version in the .lo > file $LO_FILEPATH that is created in the next statement. Although the > version is placed in something that appears to be a comment, it is > required later by something else called 'libtool', and it is > considered to be an error if the version is missing: > > libtool: error: 'src/backend/cuda/pup/yaksuri_cudai_pup__Bool.lo' is > not a valid libtool object > > The file contains the line > # Generated by > > This is a rather cryptic error message, but it goes away if the > libtool invocation on line 44 is changed to './libtool'. That is > marginally OK if cudalt.sh is only invoked in that directory (which > seems to be true just now) but it's not a permanent solution IMHO. > > I have attached the build log for whatever that's worth. Let me know > if you want any config logs. > > On 5/2/22 11:01 AM, Zhou, Hui wrote: >> Hi Allen, >> >> The line was just getting a libtool version to be included in a >> comment. I suspect simply deleting the line would work fine. Could >> you try that? >> >> Posting yaksa related questions here is fine. Don't worry about >> reposting to yaksa-users. >> >> -- >> Hui >> ------------------------------------------------------------------------ >> *From:* Allen McIntosh via discuss <discuss(a)mpich.org> >> *Sent:* Monday, May 2, 2022 9:22 AM >> *To:* discuss(a)mpich.org <discuss(a)mpich.org> >> *Cc:* Allen McIntosh <aamcintosh(a)peratonlabs.com> >> *Subject:* [mpich-discuss] error building cuda from yaksa >> >> Mpich version: 4.0.2 >> OS: Ubuntu 20.04 (but likely irrelevant) >> >> Line 45 (approximately) of >> mpich-4.0.2/modules/yaksa/src/backend/cuda/cudalt.sh invokes libtool >> without providing its own version. This results in an error if there is >> no system version of libtool. I got around this by changing the >> invocation to "./libtool", but that is pretty ugly. I have asked to >> have libtool-bin installed on the build system. I can post with any >> results. >> >> [I see that I really should have posted this to yaksa-users. I will >> subscribe and post there.] >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >

1 0

Re: [mpich-discuss] [EXTERNAL] Re: error building cuda from yaksa
by Allen McIntosh 02 May '22

02 May '22

That was what I thought also. Unfortunately this doesn't work. The purpose of setting $LIBTOOL_VERSION is to embed the version in the .lo file $LO_FILEPATH that is created in the next statement. Although the version is placed in something that appears to be a comment, it is required later by something else called 'libtool', and it is considered to be an error if the version is missing: libtool: error: 'src/backend/cuda/pup/yaksuri_cudai_pup__Bool.lo' is not a valid libtool object The file contains the line # Generated by This is a rather cryptic error message, but it goes away if the libtool invocation on line 44 is changed to './libtool'. That is marginally OK if cudalt.sh is only invoked in that directory (which seems to be true just now) but it's not a permanent solution IMHO. I have attached the build log for whatever that's worth. Let me know if you want any config logs. On 5/2/22 11:01 AM, Zhou, Hui wrote: > Hi Allen, > > The line was just getting a libtool version to be included in a > comment. I suspect simply deleting the line would work fine. Could you > try that? > > Posting yaksa related questions here is fine. Don't worry about > reposting to yaksa-users. > > -- > Hui > ------------------------------------------------------------------------ > *From:* Allen McIntosh via discuss <discuss(a)mpich.org> > *Sent:* Monday, May 2, 2022 9:22 AM > *To:* discuss(a)mpich.org <discuss(a)mpich.org> > *Cc:* Allen McIntosh <aamcintosh(a)peratonlabs.com> > *Subject:* [mpich-discuss] error building cuda from yaksa > > Mpich version: 4.0.2 > OS: Ubuntu 20.04 (but likely irrelevant) > > Line 45 (approximately) of > mpich-4.0.2/modules/yaksa/src/backend/cuda/cudalt.sh invokes libtool > without providing its own version. This results in an error if there is > no system version of libtool. I got around this by changing the > invocation to "./libtool", but that is pretty ugly. I have asked to > have libtool-bin installed on the build system. I can post with any > results. > > [I see that I really should have posted this to yaksa-users. I will > subscribe and post there.] > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] error building cuda from yaksa
by Zhou, Hui 02 May '22

02 May '22

Hi Allen, The line was just getting a libtool version to be included in a comment. I suspect simply deleting the line would work fine. Could you try that? Posting yaksa related questions here is fine. Don't worry about reposting to yaksa-users. -- Hui ________________________________ From: Allen McIntosh via discuss <discuss(a)mpich.org> Sent: Monday, May 2, 2022 9:22 AM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: Allen McIntosh <aamcintosh(a)peratonlabs.com> Subject: [mpich-discuss] error building cuda from yaksa Mpich version: 4.0.2 OS: Ubuntu 20.04 (but likely irrelevant) Line 45 (approximately) of mpich-4.0.2/modules/yaksa/src/backend/cuda/cudalt.sh invokes libtool without providing its own version. This results in an error if there is no system version of libtool. I got around this by changing the invocation to "./libtool", but that is pretty ugly. I have asked to have libtool-bin installed on the build system. I can post with any results. [I see that I really should have posted this to yaksa-users. I will subscribe and post there.] _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

error building cuda from yaksa
by Allen McIntosh 02 May '22

02 May '22

Mpich version: 4.0.2 OS: Ubuntu 20.04 (but likely irrelevant) Line 45 (approximately) of mpich-4.0.2/modules/yaksa/src/backend/cuda/cudalt.sh invokes libtool without providing its own version. This results in an error if there is no system version of libtool. I got around this by changing the invocation to "./libtool", but that is pretty ugly. I have asked to have libtool-bin installed on the build system. I can post with any results. [I see that I really should have posted this to yaksa-users. I will subscribe and post there.]

1 0