Xemuth Messages: 387 Registered: August 2018 Location: France
Senior Member
When using the Bazaar/plugin/assimp package, I got an error at linking (only when using CLANG) (MSVS work perfect) :
(): Linking has failed
(): lld-link: error: duplicate symbol: std::__throw_bad_alloc()
(): >>> defined at Core.a(heap.o)
(): >>> defined at libc++.a(new.cpp.obj)
():
(): lld-link: error: duplicate symbol: operator new(unsigned long long)
(): >>> defined at Core.a(heap.o)
(): >>> defined at libc++.a(new.cpp.obj)
...
The only way I have found to get around this issu is to put the flag "USEMALLOC" but I don't think it's a good way.
I don't know if this"problem" is related to Upp or assimp.
Someone can help me by explaining what's happening ?
The ASSIMP case is a good example of U++ efficiency (thanks to Mirek ).
The same ASSIMP example compiled with MSC without USEMALLOC is much faster than with USEMALLOC.
Now it would be great to get CLANG working without USEMALLOC.
The ASSIMP case is a good example of U++ efficiency (thanks to Mirek ).
The same ASSIMP example compiled with MSC without USEMALLOC is much faster than with USEMALLOC.
Now it would be great to get CLANG working without USEMALLOC.
Just for the info: I have looked into it, removed all funny new/delete related code in ASSIMP, but it still does not work.
The ASSIMP case is a good example of U++ efficiency (thanks to Mirek ).
The same ASSIMP example compiled with MSC without USEMALLOC is much faster than with USEMALLOC.
Now it would be great to get CLANG working without USEMALLOC.
Just for the info: I have looked into it, removed all funny new/delete related code in ASSIMP, but it still does not work.
Members
Pages
Help
Register
Login
Home
