Hi Robert,
Here is my output if I run cmake with clean cache:
-- The C compiler identification is GNU 7.2.0
-- The CXX compiler identification is GNU 7.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
--
Hello William,
There seems to be a deeper issue and the #include is no more than
a bandaid that helps us narrow down the possible causes. I have a feeling
this might track back to CMakeLists.txt. Do you mind providing the output
of your:
cmake -DCMAKE_INSTALL_PREFIX=../install ../trunk
Thanks Robert, that solved my issue.
Le 12/03/2018 à 18:27, Robert Caulk a écrit :
Hey Will,
Looks like Thomas Chauve is encountering the same issue. I am unable
to recreate this problem so will one of you please try adding:
#include
to JointedCohesiveFrictionalpm.hpp and then
Hey Will,
Looks like Thomas Chauve is encountering the same issue. I am unable to
recreate this problem so will one of you please try adding:
#include
to JointedCohesiveFrictionalpm.hpp and then recompiling?
Thanks!
Robert
On Fri, Mar 9, 2018 at 10:51 AM, William Chèvremont <
In fact, for the git rebase, I updade py computer and forget to run this
command again. Now fixed.
For the compile error, my linux and compiler are following:
>$ gcc --version
gcc (Ubuntu 7.2.0-8ubuntu3.2) 7.2.0
>$ lsb_release -a
LSB Version:
This being said I don't think the merge can be the cause of William's
compile error.
The question is why gcc can't find std::random_device.
Just weird.
B
/
/
On 03/09/2018 06:35 PM, Bruno Chareyre wrote:
Let us continue the discussion here on yade-dev, William is member.
Merge commits are
Hi William,
Thanks for mentioning.
You can send compiler errors to yade-dev (are you member of yade-dev?
else I suggest you join) or even better to a bug report.
It is better to specificy revision numbers, to.
Your last revision [1] made it through the buildbot.
Do you still have the problem
7 matches
Mail list logo
