You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is more informational than bug report or feature request because I don't really know how to automatically detect such situation and I don't want to suggest building libraries ourselves from scratch.
To build pyrun linked statically against sqlite3 with icu support following changes were needed:
add libraries from icu-config --ldflags (-licui18n, -licuuc, -licudata) to _sqlite3 description in Runtime/Setup.PyRun-2.7
add -static-libstdc++ -static-libgcc to CXX variable in Makefile.pre and change LINKCC from CC to CXX - this is required because icu libraries are written in c++ and require its standard library, so linker has to know how to link statically against libstdc++. However if dynamic linking to libstdc++ is acceptable this paragraph is not needed and it's sufficient to add -lstdc++ to changes in first item.
I've noticed that this issue looks like blog post, sorry for abusing your tracker.
The text was updated successfully, but these errors were encountered:
This issue is more informational than bug report or feature request because I don't really know how to automatically detect such situation and I don't want to suggest building libraries ourselves from scratch.
To build pyrun linked statically against sqlite3 with icu support following changes were needed:
icu-config --ldflags
(-licui18n
,-licuuc
,-licudata
) to_sqlite3
description inRuntime/Setup.PyRun-2.7
-static-libstdc++ -static-libgcc
toCXX
variable inMakefile.pre
and changeLINKCC
fromCC
toCXX
- this is required because icu libraries are written in c++ and require its standard library, so linker has to know how to link statically againstlibstdc++
. However if dynamic linking tolibstdc++
is acceptable this paragraph is not needed and it's sufficient to add-lstdc++
to changes in first item.I've noticed that this issue looks like blog post, sorry for abusing your tracker.
The text was updated successfully, but these errors were encountered: