You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Open MPI are you using? (e.g., v1.10.3, v2.1.0, git branch name and hash, etc.)
v2.1.0
Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)
from a release tarball: openmpi-2.1.0.tar.bz2
Please describe the system on which you are running
Operating system/version:
SUSE Linux Enterprise Server 11 SP4
Computer hardware:
SGI ICE X
Network type:
infiniband
Details of the problem
When configuring open MPI to have lustre support, if I use just "--with-lustre" the build
eventually fails with
make[2]: Entering directory `/p/home/tmattox/TIM/src/openmpi-2.1.0/build/ompi/mca/fs/lustre'
CCLD libmca_fs_lustre.la
../../../../libtool: line 7489: cd: yes/lib: No such file or directory
libtool: error: cannot determine absolute directory name of 'yes/lib'
make[2]: *** [libmca_fs_lustre.la] Error 1
make[2]: Leaving directory `/p/home/tmattox/TIM/src/openmpi-2.1.0/build/ompi/mca/fs/lustre'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/p/home/tmattox/TIM/src/openmpi-2.1.0/build/ompi'
make: *** [all-recursive] Error 1
That is because the configure script used the value of "yes" as a path instead of /usr or
something else when it set the path for the lustre library variable: ompi_check_lustre_dir
See the "-Lyes/lib" near the end of the configure:244357 line extracted from the config.log:
configure:244302: result: yes
configure:244326: checking for library containing llapi_file_create
configure:244357: gcc -o conftest -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -pthread -I/app/unsupported/COST/papi/5.4.1/gnu//include -I/app/unsupported/COST/tcltk/8.6.4/gnu//include -I/p/home/tmattox/TIM/src/openmpi-2.1.0/opal/mca/hwloc/hwloc1112/hwloc/include -I/p/home/tmattox/TIM/src/openmpi-2.1.0/build/opal/mca/hwloc/hwloc1112/hwloc/include -I/p/home/tmattox/TIM/src/openmpi-2.1.0/opal/mca/event/libevent2022/libevent -I/p/home/tmattox/TIM/src/openmpi-2.1.0/opal/mca/event/libevent2022/libevent/include -I/p/home/tmattox/TIM/src/openmpi-2.1.0/build/opal/mca/event/libevent2022/libevent/include -Iyes/include -L/app/unsupported/COST/papi/5.4.1/gnu//lib -L/app/unsupported/COST/git/2.4.4/gnu//lib -L/app/unsupported/COST/tcltk/8.6.4/gnu//lib -Lyes/lib conftest.c -lrt -lm -lutil >&5
/p/work2/tmattox/ccaOuL4w.o: In function `main':
conftest.c:(.text.startup+0x7): undefined reference to `llapi_file_create'
collect2: error: ld returned 1 exit status
If I instead use "../configure --with-lustre=/usr" everything works, but "/usr" appears to be the intended default. The output from "../configure --help" indicates that the DIR value is optional for --with-lustre.
The problem seems to be someplace around line 244199 of configure, but I stopped following the rabbit hole...
The text was updated successfully, but these errors were encountered:
timattox
changed the title
"../configure --with-lustre" failes with "yes/lib" error
"../configure --with-lustre" causes build to fail with "yes/lib" error
May 4, 2017
What version of Open MPI are you using? (e.g., v1.10.3, v2.1.0, git branch name and hash, etc.)
v2.1.0
Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)
from a release tarball: openmpi-2.1.0.tar.bz2
Please describe the system on which you are running
Operating system/version:
SUSE Linux Enterprise Server 11 SP4
Computer hardware:
SGI ICE X
Network type:
infiniband
Details of the problem
When configuring open MPI to have lustre support, if I use just "--with-lustre" the build
eventually fails with
That is because the configure script used the value of "yes" as a path instead of /usr or
something else when it set the path for the lustre library variable: ompi_check_lustre_dir
See the "-Lyes/lib" near the end of the configure:244357 line extracted from the config.log:
If I instead use "../configure --with-lustre=/usr" everything works, but "/usr" appears to be the intended default. The output from "../configure --help" indicates that the DIR value is optional for --with-lustre.
The problem seems to be someplace around line 244199 of configure, but I stopped following the rabbit hole...
The text was updated successfully, but these errors were encountered: