NaCl docs: mention static libraries for SJLJ

native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst

Index: native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
diff --git a/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst b/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
index 2324774fa8c20b4d393bc058155489d823d9f034..d58c94186f492a189c90636cdbc5a60745235a47 100644
--- a/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
+++ b/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
@@ -183,6 +183,12 @@ calls to ``abort()``. The usual ``-fno-exceptions`` flag is also
 supported. PNaCl will support full zero-cost exception handling in the
 future.
 
+.. note:: When using naclports_ or other prebuilt static libraries, you'll want
+          to make sure you rebuild these libraries with exception handling

[Mark Seaborn, 2015/02/18 18:00:08]

How does a developer do that?

Isn't -fexceptions the default when compiling C++?

[JF, 2015/02/18 18:19:14]

What do you mean? There are instructions on this above, how would you suggest
improving them?
Yes, it's implied above when -fno-exceptions is mentioned. Do you suggest saying
-fexceptions is the default?

[Mark Seaborn, 2015/02/18 18:36:03]

Sorry, I didn't look at all of the context.

Saying "rebuild" here suggests that nacl-ports uses -fno-exceptions by default. 
Is that the case?

If not, maybe say "...make sure these libraries are not being built with
-fno-exceptions"?

[JF, 2015/02/18 18:43:28]

I clarified a few things, PTAL.

+          enabled. For naclports, you'll want to modify the port's ``build.sh``.
+
+.. _naclports: https://code.google.com/p/naclports
+
 NaCl supports full zero-cost C++ exception handling.
 
 Inline Assembly