vesoft-inc / vesoft-inc/nebula-cpp
NebulaGraph CPP complie error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 19
- Forks
- 25
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
I didn't encounter any errors when running cmake, but I ran into the following errors when running make ..
/home/wangqian/lib/cppnebulagraph/nebula-cpp/include/common/datatypes/Date.h:26:25: error: expected ‘)’ before ‘days’
26 | explicit Date(uint64_t days);
| ~ ^~~~~
| )
/home/wangqian/lib/cppnebulagraph/nebula-cpp/include/common/datatypes/Date.h:133:7: error: ‘uint64_t’ does not name a type
133 | uint64_t month : 4;
**then i add the #include but errors like this : **
In file included from /home/wangqian/lib/cppnebulagraph/nebula-cpp/include/common/geo/io/wkb/ByteOrderDataIOStream.h:10,
from /home/wangqian/lib/cppnebulagraph/nebula-cpp/src/geo/io/wkb/ByteOrderDataIOStream.cpp:6:
/home/wangqian/lib/cppnebulagraph/nebula-cpp/include/common/geo/io/wkb/ByteOrder.h:11:6: error: elaborated-type-specifier for a scoped enum must not use the ‘class’ keyword [-Werror]
11 | enum class ByteOrder : uint8_t {
| ~~~~ ^~~~~
| -----
/home/wangqian/lib/cppnebulagraph/nebula-cpp/include/common/geo/io/wkb/ByteOrder.h:11:22: error: found ‘:’ in nested-name-specifier, expected ‘::’
11 | enum class ByteOrder : uint8_t {
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting include/common/datatypes/Date.h and include/common/geo/io/wkb/ByteOrder.h, then review the compiler and CMake configuration used before running make. Reproduce the reported errors and determine the build configuration needed for these headers to compile; done means the project builds without the shown errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100