Orvid King
Orvid King
Which compilers & runtimes do you need to support? As far as I know we're on the way towards fully replacing all uses of folly::format with fmt as it is...
I expect you may run into other issues since velox seems to believe you're on an m1 mac, but is trying to build Folly as x86_64, but I'll put up...
This appears to be failing to link against boost::context, glog, and at least a couple parts of Folly. How are you currently attempting to link against folly?
https://github.com/facebook/folly/commit/33177445f694ee6f8298d4023cf655443ee6a3cf should be the fix for this, though it hasn't made it into a release yet.
The current version is already in use with clang 12 + libstd++, and this actually appears to break that, causing it to fail to detect that coroutines are available at...
This still breaks things. I think the issue here may be a bit more fundamental: Our internal setup builds using clang, and uses libstdc++, and has coroutines enabled. I'm not...
Which CPU architecture is this using? arm32 or aarch64? F14 is an unordered_map that uses SSE (for x86_64) and neon (for aarch64) instructions for higher speed and falls back to...
Unfortunately the larger log still doesn't have what call is actually triggering this, so I'll need a larger log to actually see the error. There is no way to disable...
I'm not able to reproduce this locally with Visual Studio 2022.2. The version of fmt you're building against is quite old (the last patch for fmt v5 was in 2018,...
You need to actually link folly in in order to use it.