Squirrel Errors After Recent Update
13 views
Skip to first unread message
Shane Keniley
May 30, 2019, 1:17:02 PM5/30/19
to zapdos-users
Hello all,
After the most recent updates to Zapdos, Crane, and Squirrel I've run in to compilation errors that I didn't see before. I updated Moose and libmesh, pulled the changes to Zapdos and Crane, and tried compiling both. Crane compiled fine, but Zapdos ran into errors with Squirrel. I thought I just didn't update squirrel, but I tried updating the squirrel submodule as well as cloning a fresh version of squirrel into ~/projects/ and compiling that. Either way the errors are the same. I've attached the output when I run "make -j4" here. They're all something like this:
/Users/keniley/projects/squirrel/src/bcs/VelocityFunctionTemperatureOutflowBC.C:50:24: error: member function 'value' not viable: 'this' argument has
type 'const Function', but function is not marked const
_vel_y_func.value(_t, _q_point[_qp]),
There are no differences between the 'master' branch of arfc/squirrel and what I have. Is anyone else running into this issue? And if not, what exactly did I do wrong...?
Casey Icenhour
May 30, 2019, 1:24:48 PM5/30/19
to zapdos...@googlegroups.com
Looks like your squirrel submodule isn't actually up to date, since that BC header file has been fixed in master. What commit is your submodule pointing to? It should have the SHA b135ea4 if you are pointing to the most up-to-date commit on the master branch.
--
You received this message because you are subscribed to the Google Groups "zapdos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zapdos-users...@googlegroups.com.
To post to this group, send email to zapdos...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zapdos-users/8e7748d2-8d4c-4c6b-a706-7bc3bf0e3a40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Casey Icenhour
May 30, 2019, 1:27:10 PM5/30/19
to zapdos...@googlegroups.com
Nevermind, I'm seeing the same issues......stay tuned while I see what's up. Everything tested well on our testing system earlier.
Casey Icenhour
May 30, 2019, 1:37:12 PM5/30/19
to zapdos...@googlegroups.com
So I found a fix for my machine - update your copy of MOOSE. This move to const Function is a very recent change, so if your version of MOOSE is older than a couple days, you might not have that new code. If you still have this problem after updating and rebuilding (I think there's a libmesh update somewhere in there too, so be sure to run that script), then we can dig deeper.
Alexander Lindsay
May 30, 2019, 1:39:50 PM5/30/19
to zapdos...@googlegroups.com
You probably will need to use the moose next branch to get it to compile, at least for the next day or so.
To view this discussion on the web visit https://groups.google.com/d/msgid/zapdos-users/CANxnQmN3Obfiquf37GwiGX2m6S8jei6co%2BtEUJfjFxkQe9WS8g%40mail.gmail.com.
Shane Keniley
May 30, 2019, 2:54:43 PM5/30/19
to zapdos-users
Yep, switching to the 'next' branch did the trick. Everything compiles again! Thank you both for the assistance.
On Thursday, May 30, 2019 at 12:39:50 PM UTC-5, Alexander Lindsay wrote:
You probably will need to use the moose next branch to get it to compile, at least for the next day or so.
On Thu, May 30, 2019 at 11:37 AM Casey Icenhour <ctic...@ncsu.edu> wrote:
So I found a fix for my machine - update your copy of MOOSE. This move to const Function is a very recent change, so if your version of MOOSE is older than a couple days, you might not have that new code. If you still have this problem after updating and rebuilding (I think there's a libmesh update somewhere in there too, so be sure to run that script), then we can dig deeper.
On Thu, May 30, 2019 at 11:26 AM Casey Icenhour <ctic...@ncsu.edu> wrote:
Nevermind, I'm seeing the same issues......stay tuned while I see what's up. Everything tested well on our testing system earlier.
On Thu, May 30, 2019 at 11:24 AM Casey Icenhour <ctic...@ncsu.edu> wrote:
Looks like your squirrel submodule isn't actually up to date, since that BC header file has been fixed in master. What commit is your submodule pointing to? It should have the SHA b135ea4 if you are pointing to the most up-to-date commit on the master branch.
On Thu, May 30, 2019 at 11:17 AM Shane Keniley <smkfi...@gmail.com> wrote:
Hello all,--After the most recent updates to Zapdos, Crane, and Squirrel I've run in to compilation errors that I didn't see before. I updated Moose and libmesh, pulled the changes to Zapdos and Crane, and tried compiling both. Crane compiled fine, but Zapdos ran into errors with Squirrel. I thought I just didn't update squirrel, but I tried updating the squirrel submodule as well as cloning a fresh version of squirrel into ~/projects/ and compiling that. Either way the errors are the same. I've attached the output when I run "make -j4" here. They're all something like this:/Users/keniley/projects/squirrel/src/bcs/VelocityFunctionTemperatureOutflowBC.C:50:24: error: member function 'value' not viable: 'this' argument has
type 'const Function', but function is not marked const
_vel_y_func.value(_t, _q_point[_qp]),
There are no differences between the 'master' branch of arfc/squirrel and what I have. Is anyone else running into this issue? And if not, what exactly did I do wrong...?
You received this message because you are subscribed to the Google Groups "zapdos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zapdos...@googlegroups.com.
To post to this group, send email to zapdos...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zapdos-users/8e7748d2-8d4c-4c6b-a706-7bc3bf0e3a40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "zapdos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zapdos...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages