Skip to content
This repository was archived by the owner on Jul 11, 2019. It is now read-only.

build issues #1

Open
moonbucks opened this issue Feb 2, 2017 · 0 comments
Open

build issues #1

moonbucks opened this issue Feb 2, 2017 · 0 comments

Comments

@moonbucks
Copy link

Hi,

I tried to build the codes, but it didn't work.
Error messages I've got were as follows.

ninja: Entering directory `out/Debug'
[1/80] CXX obj/src/monitor/monitor_tests.cpu_core.o
FAILED: obj/src/monitor/monitor_tests.cpu_core.o
../../build/llvm-build/bin/clang++ -MMD -MF obj/src/monitor/monitor_tests.cpu_core.o.d -DDEBUG -D_DEBUG -I../../src -I../../src/bare/arch/test -I../../deps/googletest/googletest/include -I../../deps/libcxx/include -Wall -Wextra -Werror -Wsign-compare -fcolor-diagnostics -fstrict-aliasing -fno-threadsafe-statics -std=c11 -Wheader-hygiene -g -O0 -std=c++11 -nostdinc++ -nostdinc++  -c ../../src/monitor/cpu_core.cc -o obj/src/monitor/monitor_tests.cpu_core.o
In file included from ../../src/monitor/cpu_core.cc:1:
In file included from ../../src/monitor/cpu_core.h:6:
In file included from ../../src/bare/phys_atomics.h:4:
In file included from ../../src/bare/phys_ptr.h:248:
../../src/bare/arch/test/phys_ptr_arch.h:58:37: error: redefinition of 'operator unsigned long'
template<> inline phys_ref<size_t>::operator size_t() const {
                                    ^
../../src/bare/arch/test/phys_ptr_arch.h:26:39: note: previous definition is here
template<> inline phys_ref<uint64_t>::operator uint64_t() const {
                                      ^
../../src/bare/arch/test/phys_ptr_arch.h:65:5: error: redefinition of 'operator='
    operator =(const size_t& value) {
    ^
../../src/bare/arch/test/phys_ptr_arch.h:33:5: note: previous definition is here
    operator =(const uint64_t& value) {
    ^
2 errors generated.
[2/80] CXX obj/deps/libcxx/src/libc++.system_error.o
[3/80] CXX obj/deps/libcxx/src/libc++.stdexcept.o
FAILED: obj/deps/libcxx/src/libc++.stdexcept.o
../../build/llvm-build/bin/clang++ -MMD -MF obj/deps/libcxx/src/libc++.stdexcept.o.d -DDEBUG -D_DEBUG -I../../deps/libcxx/include -I../../deps/libcxxabi/include -Wall -Wextra -Werror -Wsign-compare -fcolor-diagnostics -fstrict-aliasing -fno-threadsafe-statics -std=c11 -Wheader-hygiene -fPIC -fstrict-aliasing -Wall -Wextra -Wshadow -Wconversion -Wnewline-eof -Wpadded -Wmissing-prototypes -Wstrict-aliasing=2 -Wstrict-overflow=4 -g -O0 -std=c++11 -nostdinc++ -nostdinc++  -c ../../deps/libcxx/src/stdexcept.cpp -o obj/deps/libcxx/src/libc++.stdexcept.o
In file included from ../../deps/libcxx/src/stdexcept.cpp:10:
../../deps/libcxx/include/__refstring:30:12: error: padding size of 'std::__1::__libcpp_refstring::_Rep_base' with 4 bytes to alignment boundary [-Werror,-Wpadded]
    struct _Rep_base
           ^
1 error generated.
[4/80] CXX obj/deps/libcxx/src/libc++.regex.o
FAILED: obj/deps/libcxx/src/libc++.regex.o
../../build/llvm-build/bin/clang++ -MMD -MF obj/deps/libcxx/src/libc++.regex.o.d -DDEBUG -D_DEBUG -I../../deps/libcxx/include -I../../deps/libcxxabi/include -Wall -Wextra -Werror -Wsign-compare -fcolor-diagnostics -fstrict-aliasing -fno-threadsafe-statics -std=c11 -Wheader-hygiene -fPIC -fstrict-aliasing -Wall -Wextra -Wshadow -Wconversion -Wnewline-eof -Wpadded -Wmissing-prototypes -Wstrict-aliasing=2 -Wstrict-overflow=4 -g -O0 -std=c++11 -nostdinc++ -nostdinc++  -c ../../deps/libcxx/src/regex.cpp -o obj/deps/libcxx/src/libc++.regex.o
../../deps/libcxx/src/regex.cpp:72:8: error: padding size of 'std::__1::(anonymous namespace)::collationnames' with 7 bytes to alignment boundary [-Werror,-Wpadded]
struct collationnames
       ^
../../deps/libcxx/src/regex.cpp:193:8: error: padding size of 'std::__1::(anonymous namespace)::classnames' with 6 bytes to alignment boundary [-Werror,-Wpadded]
struct classnames
       ^
2 errors generated.
[5/80] CXX obj/deps/libcxx/src/libc++.strstream.o
[6/80] CXX obj/deps/libcxx/src/libc++.string.o
ninja: build stopped: subcommand failed.

With all those dependency scripts were run, what is the problem ?
Normally those are supposed to be warnings
but somehow all those are turned out to be errors thus I can't go forward.
Do I need to resolve the issues by fixing the codes?
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant