Compiling blender with alembic on voidlinux (x86_64 / glibc) do not work

Hi all,

The compilation work well without alembic support. If i try to add it, theses errors come:

/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.cc: In function ‘void read_mverts(CDStreamConfig&, const AbcMeshData&)’:
/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.cc:162:41: error: no matching function for call to ‘read_mverts(MVert*&, const P3fArraySamplePtr&, std::nullptr_t)’
162 | read_mverts(mverts, positions, nullptr);
| ^
In file included from /builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.cc:21:
/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.h:80:6: note: candidate: ‘void read_mverts(MVert*, Alembic::abc::v12::P3fArraySamplePtr, Alembic::abc::v12::N3fArraySamplePtr)’
80 | void read_mverts(MVert *mverts,
| ^~~~~~~~~~~
/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.h:82:60: note: no known conversion for argument 3 from ‘std::nullptr_t’ to ‘Alembic::abc::v12::N3fArraySamplePtr’ {aka ‘std::tr1::shared_ptr<Alembic::abc::v12::TypedArraySampleAlembic::Abc::v12::N3fTPTraits >’}
82 | const Alembic::AbcGeom::N3fArraySamplePtr normals);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~^
/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.cc:151:13: note: candidate: ‘void read_mverts(CDStreamConfig&, const AbcMeshData&)’
151 | static void read_mverts(CDStreamConfig &config, const AbcMeshData &mesh_data)
| ^

/builddir/blender-2.83.0/source/blender/io/alembic/intern/abc_reader_mesh.cc:151:13: note: candidate expects 2 arguments, 3 provided
make[2]: *** [source/blender/io/alembic/CMakeFiles/bf_alembic.dir/build.make:148: source/blender/io/alembic/CMakeFiles/bf_alembic.dir/intern/abc_reader_mesh.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:6033: source/blender/io/alembic/CMakeFiles/bf_alembic.dir/all] Error 2
make: *** [Makefile:183: all] Error 2

It compile well on archlinux for example. I think that’s not a bug but something with GCC (gcc 9.3.0)?