>>
>> 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 uses yacc and makes a *lot* of assumptions about the
>> compiler!
> I completely agree! We used the r
On Sat, Oct 20, 2012 at 8: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?
>
I completely agree! We used the release
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 uses yacc and makes a *lot* of assumptions about the
compiler!
-Ben
On Oct 20, 2012, at 9:30 AM, "Cody Permann"
ma
On Wed, Oct 3, 2012 at 7:34 AM, Kirk, Benjamin (JSC-EG311) <
[email protected]> wrote:
> >> Thought I'd follow up here. I've been working in libMesh trunk for
> awhile, so
> >> I hadn't tried out the branch on my laptop for some time. I did last
> night
> >> and
> >> these issues go away th
