leezu commented on issue #20095: URL: https://github.com/apache/incubator-mxnet/issues/20095#issuecomment-841314954
> So do we still need to put libgomp.so into the wheels but will have to do it in another way or just simply ignore this right now? If we want to be compliant with manylinux2014 policy, yes, we need to put it in the wheel. But the easiest option for now is probably to ask users to install system libgomp. That works because libgomp maintainers were careful to avoid `soversion` bumps of the libgomp and the newer libgomps are still compatible with the older ones. If we want to package libgomp.so into the wheel, we have to be careful because manylinux2014 requires us to compile on CentOS7, which comes with a very old libgomp that may contains bugs. So if we would put that in the wheel, mxnet may run slower for users of newer distributions, compared to if they install system libgomp. We would need to benchmark that first. If it indeed causes a slowdown, we'd have two options: 1) Build a newer libgomp from source on CentOS7 and package the optimized/new libgomp (this is not officially supported by gcc, but "possible" - though may take substantial effort). 2) wait until perennial manylinux https://github.com/pypa/manylinux/issues/542 get's adapted and switch the CD to CentOS 8 So I'd suggest to ask users to install libgomp for now (don't be fully manylinux2014 compliant) and revisit the decision once https://github.com/pypa/manylinux/issues/542 is resolved -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
