build binary eggs for linux-armv6l (raspberry pi)

[zooko]

This is one of a collection of tickets about binary eggs that need to be built for specific platforms.

See src/allmydata/_auto_deps.py for Tahoe-LAFS trunk's current dependencies, and ​https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-dep-eggs/README.html for the eggs that have been built and uploaded.

[daira]

zooko wrote:

From #804, if someone builds binary eggs of the dependencies for linux-armv6l, that would make it easier and faster to install Tahoe-LAFS on raspberry pi.

It is currently missing all eggs, and I think we just need to support Python 2.7.

[zooko]

Here are instructions for how to build binary eggs:

Packaging

[kapiteined]

Replying to zooko:

Here are instructions for how to build binary eggs:

Packaging

Hmm.. i tried but get an error:

python -c "import setuptools; execfile('setup.py')" bdist_egg[[BR]]
Traceback (most recent call last):[[BR]]
File "<string>", line 1, in <module>[[BR]]
File "setup.py", line 24, in <module>[[BR]]
basedir = os.path.dirname(os.path.abspath(__file__))[[BR]]
NameError: name '__file__' is not defined[[BR]]

My knowledge of python is next to zero, so a foolproof cut and paste line to build this egg would be great

Kind regards,
Ed

[daira]

Try this:

python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg

[daira]

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

[kapiteined]

made with: python setup.py bdist_egg

[kapiteined]

made with: python -c "import setuptools; file = 'setup.py'; execfile('setup.py')" bdist_egg

[kapiteined]

Replying to daira:

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

Worked like a charm, the egg file from both commands are attached, the original name was:
dist/allmydata_tahoe-1.10.0-py2.7.egg

Could someone change the Packaging page to include the right commands?

[zooko]

Thanks, kapiteined and daira! kapiteined: what's your name and contact info, and what computer did you build it on, and what operating system was it running? Thanks again!

[kapiteined]

Replying to zooko:

Thanks, kapiteined and daira! kapiteined: what's your name and contact info, and what computer did you build it on, and what operating system was it running? Thanks again!

Hi Zooko, my e-mail address is ed AT kapitein DOT org.
It was build on the pi itself running rasbian, updated to the latest version about a week ago.

Feel free to contact me to try out a release candidate for the pi package.

[daira]

Replying to kapiteined:

Replying to daira:

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

Worked like a charm, the egg file from both commands are attached, the original name was:
dist/allmydata_tahoe-1.10.0-py2.7.egg

That's an egg for Tahoe itself, which we don't actually need. We need the eggs for Tahoe's dependencies that use C/C++ code, which are the 6 table columns at ​https://tahoe-lafs.org/source/tahoe/deps/tahoe-lafs-dep-eggs/README.html:

• ​Twisted (use the source tarball)
• ​pyOpenSSL
• ​pycrypto
• ​pycryptopp
• ​zfec
• ​zope.interface

Could someone change the Packaging page to include the right commands?

Will do.

[daira]

Replying to daira:

Replying to kapiteined:

Could someone change the Packaging page to include the right commands?

Will do.

Done.

[tilllt]

pyOpenSSL seems to need the "long" packaging command as well:

python -c "import setuptools; file = 'setup.py'; execfile('setup.py')" bdist_egg

[daira]

Replying to tilllt:

pyOpenSSL seems to need the "long" packaging command as well:

python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg

Fixed in Packaging.

[zooko]

Okay, I'm officially closing all tickets that have to do with binary eggs on Linux as wontfix. Binary eggs have never worked on Linux, and never will. I hate this, but I hereby stop struggling against it.

[daira]

It might be useful to maintain these eggs for Raspberry pi because it's difficult to compile them on the pi.

[warner]

I'm +1 on hosting ARM eggs. I've got an rPi lying around, I could probably build them if I get some free time.

[daira]

The necessary eggs are already attached to this ticket, aren't they?

[exarkun]

We have since stopped CI for Raspberry Pi/ARMv6l. Also eggs are probably obsolete at this point (a similar ticket might be filed about wheels, if Raspberry Pi/ARMv6l again becomes a supported platform).