Possibly one of the files you are linking is not proper LLVM IR - maybe the build system generated a native library for some reason.
- Alon On Wed, Jun 11, 2014 at 10:40 PM, André Fiedler <[email protected]> wrote: > Seems it's compiled with an older version. I did try to re-compiled it > with latest Emscripten, but getting this messages: > > $ sudo emcc -O1 -g0 -I./include/ ../templates/zbar-main.c >> ./zbar/.libs/libzbar.a --js-library ../templates/zbar-callbacks.js -o >> ./zbar-processor-content.js >> /Users/xxx/Downloads/emsdk_portable/clang/e1.16.0_64bit/llvm-nm: >> /var/folders/6d/h53dfksj169fwbfs0nqgx7s80000gn/T/emscripten_temp_fZKgdE/ar_output_47210_0/__.SYMDEF >> SORTED: unrecognizable file type >> warning: unresolved symbol: zbar_image_set_data >> warning: unresolved symbol: zbar_image_first_symbol >> warning: unresolved symbol: zbar_processor_create >> warning: unresolved symbol: zbar_symbol_get_type >> warning: unresolved symbol: zbar_image_set_size >> warning: unresolved symbol: zbar_processor_destroy >> warning: unresolved symbol: zbar_image_free_data >> warning: unresolved symbol: zbar_processor_user_wait >> warning: unresolved symbol: zbar_get_addon_name >> warning: unresolved symbol: zbar_image_set_format >> warning: unresolved symbol: zbar_get_symbol_name >> warning: unresolved symbol: zbar_process_image >> warning: unresolved symbol: zbar_image_destroy >> warning: unresolved symbol: zbar_image_create >> warning: unresolved symbol: zbar_processor_init >> warning: unresolved symbol: zbar_symbol_get_data >> warning: unresolved symbol: zbar_processor_is_visible >> warning: unresolved symbol: zbar_symbol_next >> warning: unresolved symbol: _zbar_error_spew >> > > What's wrong? > > Am Donnerstag, 12. Juni 2014 01:22:20 UTC+2 schrieb Alon Zakai: >> >> Possible you hit a bug. If you can reduce it a testcase, please file >> that. Also possible the program is not portable in some way (see >> https://github.com/kripken/emscripten/wiki/Debugging for some tools to >> check). >> >> - Alon >> >> >> >> On Wed, Jun 11, 2014 at 3:36 AM, André Fiedler <[email protected]> >> wrote: >> >>> I've used this Emscripten port of ZBar: >>> >>> https://github.com/yurydelendik/zbarjs/blob/master/zbar-processor.js >>> >>> ZBar is a Bar- and QR-Code Reader. If I scan a QR-Code containing >>> special chars like the German "Ü", it returns "ﾃ". Non special chars work >>> fine. >>> >>> Any hints why this happens? I don't think it's ZBars fault, it's widely >>> used. >>> >>> greetings André >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "emscripten-discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
