Cereal does not compile with libc++ due to use of unique_ptr<void> about cereal

[AzothAmmo]

You are correct in that unique_ptr<void> does some strange things if reset() is called on it. In every case we do this it is never holding any actual data.

I have this pretty much fixed locally but some linker errors with libc++ are causing a hold-up.

[AzothAmmo]

Are you compiling under linux or mac? If you are on linux, can you tell me the configuration you used when installing libc++ and if you are using libc++abi, libsupc++, or libcxxrt? What do your build options look like?

[randvoorhies]

If you're building on mac, can you tell me what version of clang and libc++ you're using?

[cnweaver]

Sorry, I've been slow to respond; I've been trying to get libc++ working on linux, but have not yet succeeded.
I am primarily on Mac OS, and I'm using the trunk versions of clang (r186247) and libc++ (r185856).

[AzothAmmo]

Compiling and linking without issue using head revisions of libc++ and libc++abi. I can't test the unit tests because that'd require me to rebuild boost using libc++. If you want to do that, go ahead. Marking closed for now. Changes are already in master.

[cnweaver]

The build succeeds and all unit tests pass with a suitably compiled boost. Thanks!