On Mon, Aug 5, 2013 at 10:49 AM, John Peterson <[email protected]> wrote:
> > > > On Mon, Aug 5, 2013 at 6:51 AM, Manav Bhatia <[email protected]>wrote: > >> hmm... trying to figure that out myself. >> >> I have not upgraded the compilers, except my macports gcc from 4.7 -> 4.8. >> I don't see why that would affect this behavior since I am not using this >> compiler. (Not to imply that there couldn't be other issues at my end.) >> > > Does any of your software stack (MPI/PETSc/etc) come from macports, or > have you hand-built everything with system GCC? > > Honestly I'm surprised that system GCC has been working for you at all... > we have been using hand-built GCC since I think Lion because of weird > segfaults in system-level libraries like this. > > Obviously I'm not 100% certain, but I don't think there's any way that > libmesh code is causing a segfault in localtime(). > > -- > John > I use only MPI from macports. I am not sure which compiler macport uses to build MPI, but I am going to guess it uses the macport gcc. I handbuilt petsc and slepc, but it uses the system gcc, while my libmesh builds have been using clang++ (boy, what a hodge-podge of compilers at my end!) I don't know what to say about clang... maybe I got luck so far. At the moment, I have recompiled my library with perflog disabled so that I can finish some things at my end. Will get back to this issue in a couple of days. It is still puzzling though... ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
