On Apr 27, 2018, at 2:02 PM, Alastair McKinstry <alastair.mckins...@sceal.ie> wrote: > >> If we're not able to get the CI build product, has anyone been able to >> reproduce the error manually? > No one's caught it manually yet :-(
Computers are hard. > Debian libtool has a bunch of patches applied > (https://sources.debian.org/src/libtool/2.4.6-2.1/debian/patches/) > but nothing has changed in libtool in years. Ok. Could it be a dependent library that is generating (somehow) a faulty .la file? Then the Open MPI libtool would be reading that and somehow getting a blank library name...? (That's a complete guess) > Two notes: (1) We run the build system / make in parallel. Should be ok. We do parallel builds all the time. > (2) When it > fails, its always at this spot. > Whats special about this point in the makefile? It's Fortran...? That's the only thing I can think of. But honestly -- it's a fairly vanilla Automake-ized Makefile.am. https://github.com/open-mpi/ompi/blob/master/ompi/mpi/fortran/use-mpi-ignore-tkr/Makefile.am The only interesting thing in that Makefile.am is that we generate 2 files (mpi-ignore-tkr-sizeof.h and mpi-ignore-tkr-sizeof.f90), but those are clearly delineated as dependencies. Maybe you can put a patch in that Makefile.am that causes libtool to be cat'ed (or even emailed to yourself -- hah!) so that we can potentially run it manually / trace it to see where this blank library name is coming from...? -- Jeff Squyres jsquy...@cisco.com
