Rok Mandeljc

> If uses the IBM compiler is fine and I wont get any ABI issues can I proceed? ABI-wise, it shouldn't make much difference if you use gcc or IBM...

> Although, as long as pyinstaller isn't being installed as an egg, it doesn't really matter. If `setuptools` (or maybe `pip`) were not explicitly updated, that might still be a...

Afraid you'll have to try and see what works. I have very limited experience with AIX 7.2, and none with 7.3. So I cannot comment on ABI compatibility (but I...

> Just some weird things I noticed on AIX 7.2 and 7.3 when using gcc we sometimes run into errors when running the binary we need to do a few...

> If I use gcc I get a gevent error and adding gevent as part of hidden imports fixes the issue. Any chance you can copy & paste the original...

Aha, so you are using pre-compiled libzmq? When you build an application bundle on 7.2, does the libzmq shared library end up collected in the frozen application bundle? At run-time...

> [@rokm](https://github.com/rokm) > > libintl.a part of gettext when swapped out for a version built on AIX 7.2 causes core dumps as well, is it possible that libintl.a if built...

> libintl.a depends on libiconv.a both are bundled, but the .so looks for the dependency under /opt/freeware/lib If that's the case, then the issue is that the .so has hard-coded...

Well, at the end of the day, I guess there are only two possibilities here: a) the issue is that our bootloader is not built with `-D_THREAD_SAFE` and/or `-D_THREAD_SAFE_ERRNO`, and...

It indeed looks like `bearclaw` is inserting its own import path hooks into `sys.path_hooks`; and since those are based on python's `FileFinder`, they have no chance of finding modules in...