-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: reference to 'bfs' is ambiguous #37
Comments
Hey, |
Sure, i'm building at Here is the error message:
Here is my compiler and OS version:
|
Hi, which modifications did you perform in order to be able to compile with gcc? I tried reproducing your issue and had to change compile flags in CMakeLists.txt. With gcc 8 everything seems to be fine. In general, we recommend compiling with clang. We haven't really been testing with gcc. |
@MMory I remove line 38 in I really don't think it's something related to compiler option. Because as I mentioned earlier: line 33 in I believe that some compiler option or newer compiler will have the ability to figure out that |
I agree that those lines are at least redundant and they break compilation for at least one major compiler, so I suggest we remove them. My question above regarding modifications was referring to removal of -MP and -Wno-return-type-c-linkage. |
I didn’t do any modifications in CMakeLists to resolve any compilation error caused by compiler options . However, -Wno-return-type-c-linkage did appear as a warning on my side |
Thanks for the detailed error message; it will be fixed today ;-) |
Hi,
In files
tools/phasar/myphasartool.cpp
andtools/phasar/phasar.cpp
there is a namespace alias:
namespace bfs = boost::filesystem;
, which is conflict with line 33 of fileinclude/phasar/Utils/Logger.h
. Sincetools/phasar/myphasartool.cpp
andtools/phasar/phasar.cpp
both have statementusing namespace psr;
.Simply comment out the line
namespace bfs = boost::filesystem;
in bothtools/phasar/myphasartool.cpp
andtools/phasar/phasar.cpp
will solve this issue.I'm using gcc 7.4 on Ubuntu 18.04. And i believe all the newer compilers would complain this error.
The text was updated successfully, but these errors were encountered: