[petsc-dev] configure failed after update of OSX

[Mark Adams]

On Tue, Jan 28, 2014 at 1:26 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> I'll have to check back my e-mail archive - but I think
> '/opt/local/bin/gmake' is broken. Don't you have /usr/bin/make?
>
>
13:49  ~$ which make
/usr/bin/make
13:52  ~$ which gmake
/opt/local/bin/gmake
13:52  ~$

I don't recall what the fix was.  Should I uninstall gmake?


> I thought petsc configure prefred /usr/bin/make - if it was found.
>
> One more -ve for macports..
>
> Satish
>
> ------
>
>
> ================================================================================
> TEST configureMake from
> config.packages.make(/Users/markadams/Codes/petsc/config/BuildSystem/config/packages/make.py:61)
> TESTING: configureMake from
> config.packages.make(config/BuildSystem/config/packages/make.py:61)
>   Check for user specified make - or gmake, make
> Checking for program /opt/local/bin/gmake...found
>           Defined make macro "MAKE" to "/opt/local/bin/gmake"
>
> ================================================================================
> gmake[2]: *** read jobs pipe: No such file or directory.  Stop.
> gmake[2]: *** Waiting for unfinished jobs....
> gmake[2]: *** write jobserver: Broken pipe.  Stop.
> gmake[1]: *** [all-recursive] Error 1
> gmake: *** [all] Error 2
> gmake: INTERNAL: Exiting with 1 jobserver tokens available; should be 7!
>
>
>
>
> On Tue, 28 Jan 2014, Mark Adams wrote:
>
> > I managed to get macports to rebuild.  It was not that hard as it turns
> > out, I was just confused about exactly what to do.  GDB broke but I was
> > able to install it after macports updated outdated packages.  PETSc still
> > seem to fail in MPICH, however.
> >
> >
> >
> > On Tue, Jan 28, 2014 at 12:54 PM, Matthew Knepley <knepley at gmail.com>
> wrote:
> >
> > > On Tue, Jan 28, 2014 at 12:51 PM, Jed Brown <jed at jedbrown.org> wrote:
> > >
> > >> Satish Balay <balay at mcs.anl.gov> writes:
> > >> > I agree a better package management system [aka macports/homebrew]
> > >> > should be preferable. But with all the wierd issues that keep
> comping
> > >> > up with users using macports on petsc lists - I can't convince
> myself
> > >> > that it is a better recommendation.
> > >>
> > >> People either need a reliable way to upgrade or the stack will get out
> > >> of date.  Also, system upgrades will be stop-the-world events with
> > >> unknown system changes and the only safe thing is to reinstall the
> > >> entire stack.  Very few people can remember all the installation
> quirks
> > >> they have gone through, and even then, it takes time to reinstall
> > >> everything.
> > >
> > >
> > > This is largely ideology. Some of us have used OSX for development for
> > > years
> > > with little productivity impact.
> > >
> > >   Matt
> > >
> > >
> > >>  > I would aswell recommend virtualbox with linux as a superior
> choice.
> > >>
> > >> I recommend
> > >>
> > >>   # dd if=/dev/zero of=/dev/disk0
> > >>
> > >> and install a decent operating system with a package manager on your
> > >> now-impeccably-clean disk.
> > >>
> > >
> > >
> > >
> > > --
> > > What most experimenters take for granted before they begin their
> > > experiments is infinitely more interesting than any results to which
> their
> > > experiments lead.
> > > -- Norbert Wiener
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140128/043ccc73/attachment.html>