[email protected] writes: > On Tue, 28 Jan 2014, Sean Farley wrote: > >> The gmake issue could be a lot of things: >> >> - something weird with mpich's autoconf >> - libtool problems >> - gmake itself >> - path issues > > The issue is with 'gmake - j 7 all' with mpich build [and similarly > petsc build] after configure [of the corresponding package] is > completed.
So I see. I still can't reproduce but it seems that other gmake users have this issue on case-insensitive filesystems (which I don't have). Can you reproduce this on a vm easily? It'd be great to nail this down. >> I'll try to reproduce this again to see if it happens on my machine. >> >> Maybe I should just advise not to use --download-*mpi*. Wrapping >> compilers is tricky. For example, Mark seems to have upgraded to >> Mavericks, yet in his script he is specifying gcc/g++ which is no longer >> distributed with Xcode. > > Apple [Xcode5] provides a binary called /usr/bin/gcc - which is > 'clang'. [Yeah naming 'clang' as 'gcc' is funky - but I think apple > does that to not break user makefiles that have 'gcc' hardcoded] Ah, right, I forgot. Confusing, nonetheless.
