Comment 4 for bug 1842134

> Well, if it was a matter of never having been tested on 32-bits, that's something we can also address by removing the builds for 32-bits.

I have fixed the 32-bits bug that caused the bad tests.
I also fixed all the compilation warnings on i386 and armhf.

By now all of these fixes have been applied to the link-grammar repository and I expect a new release in a few days.

> Specifically, the issues for armhf are with linking:
> ...
> /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 7362 >= 3462 for section `.strtab'

These warnings are not related specifically to link-grammar. They happen in some other packages for armhf and embedded processors. People suggest that the default segment for strings is too small for some embedded processors, or that there is a toolchain problem. I don't know which is correct, if any. I guess it will now work find even with these linkage warnings (I still need to install an armhf guest machine to test it.)

Please see for example::
https://bugzilla.samba.org/show_bug.cgi?id=13754 (samba on armhf)
https://stackoverflow.com/questions/45501504/ld-invalid-string-offset-for-section-strtab
https://www.google.com/search?q="ld"+"invalid+string+offset"+"section+strtab" (ggogle search)

All of these problems are totally unrelated to Python and SQLite, so there is no need to block them.

Summary:
The problems related to the library itself have been fixed.
Please don't remove link-grammar from i386 and armhf.
Just build it again from the upcoming release.
The blocking from Python and SQLite can be release just now as there is no reason here for them.