Re: [Libmesh-devel] Compiler Fiasco Upate

2012-10-22 Thread Kirk, Benjamin (JSC-EG311)
That error is eerily familiar to what I get on OSX when I use boost.unit in my app code. No resolution yet, but definitely let me know if you figure it out! On Oct 22, 2012, at 4:00 PM, "Cody Permann" mailto:[email protected]>> wrote: On Mon, Oct 22, 2012 at 4:50 PM, Paul T. Bauman mai

Re: [Libmesh-devel] Compiler Fiasco Upate

2012-10-22 Thread Cody Permann
On Mon, Oct 22, 2012 at 4:50 PM, Paul T. Bauman wrote: > Sorry I haven't been able to be more helpful in reproducing the errors. Is > the pretty much settled at this point (i.e. ditching the non-release > version of fparser) or is there still some more stuff y'all would like me > to try? Don't

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Cody Permann
On Mon, Oct 22, 2012 at 9:08 AM, Roy Stogner wrote: > > On Mon, 22 Oct 2012, Kirk, Benjamin (JSC-EG311) wrote: > > To be clear, 4.5 is a proper release. >> >> The issue is they distribute two packages - the peon version >> consisting of two files (which we propose we move to) and the >> developer

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Roy Stogner
On Mon, 22 Oct 2012, Kirk, Benjamin (JSC-EG311) wrote: > To be clear, 4.5 is a proper release. > > The issue is they distribute two packages - the peon version > consisting of two files (which we propose we move to) and the > developers version for Jose who want to muck with fparser. > > We prese

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Roy Stogner
On Mon, 22 Oct 2012, Cody Permann wrote: > On Sat, Oct 20, 2012 at 9:56 AM, Kirk, Benjamin (JSC-EG311) wrote: > I'll let Roy weigh in, but my observation has been that 90% of the > current build requirements are to make the source > compressor/obfuscator that in the end produces a single sou

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Kirk, Benjamin (JSC-EG311)
If it helps, the script I used to setup my port config is here: https://github.com/benkirk/Documents/blob/master/it/scripts/mac.sh On Oct 22, 2012, at 9:04 AM, "Cody Permann" mailto:[email protected]>> wrote: On Mon, Oct 22, 2012 at 7:52 AM, Kirk, Benjamin (JSC-EG311) mailto:benjamin.ki

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Cody Permann
On Mon, Oct 22, 2012 at 7:52 AM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > Cody, back to the subject though - > > Yeah, on the automake branch with macports gcc4.5 everyhing is ok, even in > debug mode. > > I've tried with gcc4.6 and 4.7. I'll give 4.5 a shot. > What happe

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Kirk, Benjamin (JSC-EG311)
Cody, back to the subject though - Yeah, on the automake branch with macports gcc4.5 everyhing is ok, even in debug mode. What happens when you run ./bootstrap ./contrib/bin/buildall.sh? -Ben On Oct 20, 2012, at 9:30 AM, "Cody Permann" mailto:[email protected]>> wrote: On Wed, Oct 3

Re: [Libmesh-devel] OS X Compilers

2012-10-22 Thread Cody Permann
On Sat, Oct 20, 2012 at 9:56 AM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote: > >> > >> I'll double check with the latest port of everything, although I do > think a lot of this is self imposed - why don't we use the released fparser > package? > >> > >> The development version us