On Jan 27, 2014, at 11:44 AM, Sean Farley <[email protected]> wrote:
> > [email protected] writes: > >> I think resolved it by getting rid of some stuff that macports put in maybe > > I just *completely* revamped the mpi ports in macports and would like to > know if these types of problems still exist. Sean, It wasn’t the MPI ports in macports. It was MPICH’s regular configure/make making mistakes because of some libraries in those directories that did not have corresponding .la files. Barry > >> MPICH or libtool assumes certain files are there if other files are there >> (without checking for them) >> >> Barry >> >> On Jan 27, 2014, at 10:36 AM, Satish Balay <[email protected]> wrote: >> >>> On Mon, 27 Jan 2014, Jed Brown wrote: >>> >>>> Mark Adams <[email protected]> writes: >>>> >>>>> It seems to want /opt/local/lib/liblzma.la >>>>> I do have /opt/local/lib/liblzma.a >>>> >>>> There is no explicit reference to liblzma in either PETSc or MPICH. Can >>>> you send PETSC_ARCH/externalpackages/mpich*/config.log? >>> >>> Ah - perhaps its a buggy libtool. Presumably its picked up from >>> /opt/local/bin/libtool - aka macports - and you have a broken macports >>> install. >>> >>> Satish >>> >>> >
