By default, auditwheel repair doesn't graft in libstdc++ and libgcc_s libraries since it assumes those are found on the host machine. At our company, the gcc found on the host machine is quite a bit older than the gcc we want to be using, so we install gcc in a non-standard location. This means that any wheels we create with auditwheel repair are instantly broken because they try to use libstdc++ and libgcc_s from the host machine.
There should be an option to override the default behavior for excluding these libraries so that users can graft them in if wanted/needed.
By default,
auditwheel repairdoesn't graft in libstdc++ and libgcc_s libraries since it assumes those are found on the host machine. At our company, the gcc found on the host machine is quite a bit older than the gcc we want to be using, so we install gcc in a non-standard location. This means that any wheels we create withauditwheel repairare instantly broken because they try to use libstdc++ and libgcc_s from the host machine.There should be an option to override the default behavior for excluding these libraries so that users can graft them in if wanted/needed.