summaryrefslogtreecommitdiff
path: root/expat
diff options
context:
space:
mode:
authorTor Lillqvist <tlillqvist@suse.com>2012-10-04 11:36:33 +0300
committerTor Lillqvist <tlillqvist@suse.com>2012-10-04 11:36:33 +0300
commit9d9f2a382d12eb3ad5335495dc8bb5f644f9fc32 (patch)
tree09a69345daf974b2268d72101eabc1683e2eafa4 /expat
parent72abe64ee0fb803d6187da176495ed765e795ccd (diff)
The "working on that" is now done
Change-Id: Ib5a9decaf97817333bbac9853589af7fc9adf94c
Diffstat (limited to 'expat')
-rw-r--r--expat/README9
1 files changed, 0 insertions, 9 deletions
diff --git a/expat/README b/expat/README
index 52496b9480a0..d7ce6824d686 100644
--- a/expat/README
+++ b/expat/README
@@ -36,14 +36,5 @@ libexpat in builds where that is used, why is a separate Unicode one
needed when an internal expat is used? Good question. Next
question. Patches welcome.
-Another interesting issue is the disable-dynloading case: When we link
-all needed LO code into one executable (as for iOS apps) or into one
-shared library (as in a tentative approach for Android apps) there is
-a problem with linking two libraries (ascii_expat_xmlparse and
-expat_xmlparse) that contain exactly the same symbols... Obviously
-just the one that happens to be mentioned first on the linking command
-line gets linked in, and code that then thinks it is calling the other
-one will mysteriously crash or silently fail. Working on that...
-
From:
[http://expat.sourceforge.net/]