On Sep 6, 2018, at 2:19 PM, Adrian Bunk <b...@debian.org> wrote:
>
> With thanks to Santiago Vila we finally figured out how to reproduce it.
>
> From a failed build log:
> I: NOTICE: Log filtering will replace 'build/openmpi-LjweZK/openmpi-3.0.1'
> with '<<PKGBUILDDIR>>'
> I: NOTICE: Log filtering will replace 'build/openmpi-LjweZK' with
> '<<BUILDDIR>>'
>
> Note the -L in the random string.
Oh wow, so your tmpdir just happens to contain "-L" and that causes the problem?
...unfortunately, I'm unable to replicate this issue. :-\
Are you able to cause this problem running by hand?
Here's what I tried:
-----
$ cd /home/jsquyres/openmpi-releases
$ mkdir -p build/openmpi-LjweZK
$ cd build/openmpi-LjweZK
$ tar xf ../../openmpi-3.0.1.tar.bz2
$ cd openmpi-3.0.1
$ ./configure --prefix=$HOME/bogus |& tee config.out
$ make -j 32 |& tee make.out
-----
I also tried with a VPATH build (same general recipe as above, but in a vpath
subdir)
Neither of these resulted in the problem.
What's different / why can't I reproduce?
I am using:
Autoconf 2.69
Automake 1.15 (*** you are using 1.15.1 -- do we think that makes a difference?)
Libtool 2.4.6
I am also using gcc 7.3.0.
Here's the directory I built in:
/home/jsquyres/openmpi-releases/build/openmpi-LjweZK/openmpi-3.0.1
I'm *not* running on Debian -- I'm running on an RHEL machine -- but this seems
like a path issue, not a distro issue, so I'm kinda hoping that that doesn't
matter...
Any thoughts?
--
Jeff Squyres
jsquy...@cisco.com
