This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Stefan Scherfke
Recipients Stefan Scherfke
Date 2016-11-22.12:35:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479818142.38.0.0931531711664.issue28772@psf.upfronthosting.co.za>
In-reply-to
Content
Hi all,

I am trying to build a custom Conda installer for Python 3.6.0b4.

I could successfully build an run Python.  However, when I run
the generated Conda installer, it dies with a "Bus error".

It happens when Conda's meta-installer script tries to replace
the build-prefix (e.g., /home/stefan/conda/asdf) with the prefix
of the actual installation (e.g., /tmp/py36).

Therefore, it opens all files in binary mode, reads their contents, replaces stuff, and writes the new contents back to the original file.

This works fine with text files but it dies when it hits the first binary file.

Here is a minimal example that reproduces the error:

$ /tmp/py36/bin/python
Python 3.6.0b4 (default, Nov 22 2016, 10:32:29)
[GCC 6.2.1 20160916 (Red Hat 6.2.1-2)] on linux
>>>
>>> path = '/tmp/py36/lib/libpython3.6m.so.1.0'
>>> f = open(path, 'wb')
BusError

Can anyone reproduce this?  Is this a compilation error or an issue
with Python itself?  It works without issues with Python 3.5.

Cheers,
Stefan

PS: If need, I can upload the Conda installer somewhere.  It's ~40MiB.
History
Date User Action Args
2016-11-22 12:35:42Stefan Scherfkesetrecipients: + Stefan Scherfke
2016-11-22 12:35:42Stefan Scherfkesetmessageid: <1479818142.38.0.0931531711664.issue28772@psf.upfronthosting.co.za>
2016-11-22 12:35:42Stefan Scherfkelinkissue28772 messages
2016-11-22 12:35:42Stefan Scherfkecreate