Jacques Distler

_Sigh._ With a fresh install, you need to specify the path ``` ruby bundle config build.iconv --with-iconv-dir=... ruby bundle install --path vendor/bundle ``` Subsequent invocation (with the same installation) should...

So ... Is there a resolution to this issue? Something along the lines of 1. Install the `libiconv package` following the instructions [here](http://gnuwin32.sourceforge.net/packages/libiconv.htm). 2. Run`ruby bundle config build.iconv --with-iconv-dir=/path/to/dir/containing/libiconv.so``ruby bundle...

In the absence of further input, I'm gonna assume that did the trick. Closing.

OK. Reopening. > (does this need a new thread? It seems I had issues posting logs as this thread got longer) It would be a lot less confusing to keep...

Sounds like a problem with the installation of the `itextomml` gem. The only place `swig_runtime_data` appears is in ``` `vendor/bundle/ruby/2.3.0/gems/itextomml-1.5.2/ext/itex2MML_ruby.c` ``` (and in the shared library that gets compiled from...

> The upper casing of that single `s` did not fix things. _Obviously_, it didn't, because the error message still complains about the lower-case `s`. I think you need to...

Sorry about this. I guess I need to know more about the packaging of gem extensions. How about the copy of `itex2MML.so` in `vendor/bundle/ruby/2.3.0/gems/itextomml-1.5.2/lib/` ? (N.B.: we're trying to verify...

I'm a little confused. I thought the logs you posted earlier indicated that you has successfully installed the `sqlite3` gem in your bundle. Evidently not... There's a lot of discussion...

[`itextomml 1.5.3`](https://rubygems.org/gems/itextomml) has been released. That should fix the 2nd of your 3 issues.

Crap! I missed a couple of pointer-type conversions which make compilation fail on 32bit systems. Very unhappy to say that I had to release `itextomml 1.5.4` to fix that.