Closed GoogleCodeExporter closed 9 years ago
Looks like a problem with https://codereview.chromium.org/92733002.
I think this change should only have changed C++ library to c++ for pepper_33
and above. In pepper_32 and below the default library was still stdc++ and
naclports should mirror this.
jf, can you take a look?
Original comment by sbc@google.com
on 11 Dec 2013 at 2:35
The naclports change was done mainly to work around the forced linking to
libstdc++ because of the nacl_io dependency on the C++ standard library.
It force-link libstdc++ for non-PNaCl builds, and force-links libc++ for PNaCl
builds since that is now the default in the current canary SDK.
This means that naclports has to be in-sync with the SDK, using the latest
naclports therefore only works with the latest SDK.
It could be possible to fix this by changing the forced-linking logic to detect
the SDK version and only apply the change on 32 and previous. Or the canary SDK
could be used instead :-)
Original comment by j...@google.com
on 11 Dec 2013 at 5:33
FWIW the change to "fix" this prior to version 33 would be to change line 103
of common.sh to:
if [ "${NACL_ARCH}" = "pnacl" -a ${NACL_SDK_VERSION} -gt 32 ]; then
I think it also needs to move down since NACL_SDK_VERSION is defined at 187.
Original comment by j...@chromium.org
on 11 Dec 2013 at 6:36
That looks like the correct fix, yes.
Original comment by sbc@chromium.org
on 11 Dec 2013 at 6:41
Original comment by sbc@google.com
on 30 Sep 2014 at 11:20
Original issue reported on code.google.com by
andy.fis...@gmail.com
on 11 Dec 2013 at 2:04