Closed nitins17 closed 2 years ago
I pushed these containers:
gcr.io/tensorflow-sigs/build:57-python3.9
gcr.io/tensorflow-sigs/build:57-python3.8
gcr.io/tensorflow-sigs/build:57-python3.7
Re-apply the build and push to gcr.io for staging
label to
rebuild and push again. This comment will only be posted once.
I pushed these containers:
gcr.io/tensorflow-sigs/build:57-python3.10
gcr.io/tensorflow-sigs/build:57-python3.9
gcr.io/tensorflow-sigs/build:57-python3.8
gcr.io/tensorflow-sigs/build:57-python3.7
Re-apply the build and push to gcr.io for staging
label to rebuild and push again. This comment will only be posted once.
Hi did this PR has relationships with -cxxopt="-D_GLIBCXX_USE_CXX11_ABI=1" and do you plan enable it in TensorFlow release binary? Thanks!
Hi did this PR has relationships with -cxxopt="-D_GLIBCXX_USE_CXX11_ABI=1" and do you plan enable it in TensorFlow release binary? Thanks!
Hi,
This PR is for updating the TensorFlow's Linux wheel to be manylinux2014 compliant. As far as I can tell, D_GLIBCXX_USE_CXX11_ABI
would still be equal to 0 because we set --with-default-libstdcxx-abi="gcc4-compatible"
; see with-default-libstdcxx-abi
in https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html
@nitins17 Do you know what was the reason for including --with-default-libstdcxx-abi="gcc4-compatible"
flag?
@nitins17 Do you know what was the reason for including
--with-default-libstdcxx-abi="gcc4-compatible"
flag?
I'm not sure. @mihaimaruseac wdyt?
@nitins17 Do you know what was the reason for including
--with-default-libstdcxx-abi="gcc4-compatible"
flag?I'm not sure. @mihaimaruseac wdyt?
What was the conclusion about this point in the last SIG build meeting?
Hi did this PR has relationships with -cxxopt="-D_GLIBCXX_USE_CXX11_ABI=1" and do you plan enable it in TensorFlow release binary? Thanks!
Hi,
This PR is for updating the TensorFlow's Linux wheel to be manylinux2014 compliant. As far as I can tell,
D_GLIBCXX_USE_CXX11_ABI
would still be equal to 0 because we set--with-default-libstdcxx-abi="gcc4-compatible"
; seewith-default-libstdcxx-abi
in https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html
On this, after the discussion in the March 2022 edition of the TF Sig Build meeting, the manylinux2014 upgrade will also include the change to new libstdcxx ABI. For more information on this and the manylinux2014 rollout, please take a look at this community thread.
Thanks!
Hi did this PR has relationships with -cxxopt="-D_GLIBCXX_USE_CXX11_ABI=1" and do you plan enable it in TensorFlow release binary? Thanks!
Hi, This PR is for updating the TensorFlow's Linux wheel to be manylinux2014 compliant. As far as I can tell,
D_GLIBCXX_USE_CXX11_ABI
would still be equal to 0 because we set--with-default-libstdcxx-abi="gcc4-compatible"
; seewith-default-libstdcxx-abi
in https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.htmlOn this, after the discussion in the March 2022 edition of the TF Sig Build meeting, the manylinux2014 upgrade will also include the change to new libstdcxx ABI. For more information on this and the manylinux2014 rollout, please take a look at this community thread.
Thanks!
That's great, thanks for this!!
Note that the images, when not cached, take quite a long time to build both dt7 and dt9 -- eventually we'll remove dt7, tentatively "after the TF 2.9 release."
Modifies the build environment to be manylinux2014 compatible
Changes include: