Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails with Ulib causing duplicate symbols #91

Open
boazsegev opened this issue Jul 17, 2017 · 2 comments
Open

Build fails with Ulib causing duplicate symbols #91

boazsegev opened this issue Jul 17, 2017 · 2 comments

Comments

@boazsegev
Copy link
Contributor

First, a big THANK YOU! for your work 馃憤馃徎馃憤馃徎馃憤馃徎

I've been trying to build the tests, but I keep getting the following error:

duplicate symbol __ZdlPv in:
    ../../intermediate/release_x64/gmake/x64/release/nativejson/memorystat.o
    ../../thirdparty/ULib/src/ulib/.libs/libulib.a(all_cpp.o)
duplicate symbol __ZdaPv in:
    ../../intermediate/release_x64/gmake/x64/release/nativejson/memorystat.o
    ../../thirdparty/ULib/src/ulib/.libs/libulib.a(all_cpp.o)
duplicate symbol __Znwm in:
    ../../intermediate/release_x64/gmake/x64/release/nativejson/memorystat.o
    ../../thirdparty/ULib/src/ulib/.libs/libulib.a(all_cpp.o)
duplicate symbol __Znam in:
    ../../intermediate/release_x64/gmake/x64/release/nativejson/memorystat.o
    ../../thirdparty/ULib/src/ulib/.libs/libulib.a(all_cpp.o)
ld: 4 duplicate symbols for architecture x86_64

I've tried removing the Ulib test, but it does't remove the linkage (only the test itself?)

I've also tried the make clean and as may ideas as I could think of...

I tried it both using the makefile and by running the premake.sh and make -f benchmark.make config=release_x64 && make -f nativejson.make config=release_x64...

Nothing helped so far.

Any help will be greatly appreciated. Besides, this might be an actual issue.

@boazsegev
Copy link
Contributor Author

P.S.

I removed Ulib from premake5.lua and the benchmarks built correctly.

I'm leaving the issue open because Ulib might be causing a real issue. I'm not sure that the fact that I'm posting this workaround qualifies as a real solution.

As a side-note, I wonder if there's a possibility to make the linkage conditional the nosing premake5...?

@ColinH
Copy link
Contributor

ColinH commented Nov 7, 2017

Same issue here, although it didn't even get to the linker stage without a little change. The C++11 detection in ULib doesn't seem to work with the C++14 flags, so UValueIter was not defined...

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

No branches or pull requests

2 participants