Gianluigi Tiesi
Gianluigi Tiesi
I had similar problems with other calls that can be easily resolved (I already fixed them for other symbols), the problem is the current toolchain is unable to link static...
I've force pushed a fix, android ndk team cheats to have to buid less versions of static bionic btw 64bit static build still fails for relocation overflow in the link...
@ChanChunSong I've fixed the problem you encountered, static build still fail on aarch64 but does work on arm
Hi, geolite legacy database was not made for utf-8 so clients may or may not use it correctly. The fact the ü is displayed as two chars makes me things...
for example pygeoip is not able to handle utf-8 data, with python3 (or python2 with a working utf-8 locale) you can use a trick to correctly pick the utf-8 string...
are you sure? with that ip I get: ```json { "area_code": 0, "city": "Toshima", "continent": "AS", "country_code": "JP", "country_code3": "JPN", "country_name": "Japan", "dma_code": 0, "latitude": 35.72630000000001, "longitude": 139.6859, "metro_code": null,...
python3 using `GeoLite2-City-CSV_20190610.zip`
this may be an idea for #19
this is fixed but I need to generate new csv, did you modified it by hand? perhaps it needs to be converted in python module
I'm not sure if the format would allow such a thing, it would be an hack and should be tested with client implementations