tahoe-lafs/trac-2024-07-25

Unable to build Tahoe-LAFS v1.10.0 on FreeBSD 10 #2269

New issue

Closed

opened 2014-08-02 22:09:08 +00:00 by manas · 14 comments

manas commented

2014-08-02 22:09:08 +00:00

Owner

Hello,

I am trying to set up Tahoe-LAFS v1.10.0 on FreeBSD 10 inside a jail. Please see the attached text file. In summary, an error seen is
conftest.c:1:10: fatal error: 'sys/epoll.h' file not found among many others like unexpected token, unknown use of instruction mnemonic without a size suffix etc. Please see the text file for full details.

Thanks,
Manas

Hello, I am trying to set up Tahoe-LAFS v1.10.0 on FreeBSD 10 inside a jail. Please see the attached text file. In summary, an error seen is `conftest.c:1:10: fatal error: 'sys/epoll.h' file not found` among many others like `unexpected token`, `unknown use of instruction mnemonic without a size suffix` etc. Please see the text file for full details. Thanks, Manas

tahoe-lafs added the

labels 2014-08-02 22:09:08 +00:00

tahoe-lafs added this to the undecided milestone 2014-08-02 22:09:08 +00:00

manas commented

2014-08-02 22:14:47 +00:00

Author

Owner

The system here is not accepting attachments. Full log is here: http://pastebin.com/mePP3cXq

The system here is not accepting attachments. Full log is here: <http://pastebin.com/mePP3cXq>

daira commented

2014-08-04 17:31:02 +00:00

Author

Owner

See #2270 for the inability to add ticket attachments.

zooko commented

2014-08-05 05:21:28 +00:00

Author

Owner

This build failure on FreeBSD 10 would be fixed by https://tahoe-lafs.org/trac/pycryptopp/ticket/85

This build failure on FreeBSD 10 would be fixed by <https://tahoe-lafs.org/trac/pycryptopp/ticket/85>

daira commented

2014-08-07 14:06:43 +00:00

Author

Owner

Replying to zooko:

This build failure on FreeBSD 10 would be fixed by https://tahoe-lafs.org/trac/pycryptopp/ticket/85

Wait, how do we know that? "unknown use of instruction mnemonic without a size suffix" sounds as though it is from assembler code, but "'sys/epoll.h' file not found" doesn't.

Replying to [zooko](/tahoe-lafs/trac-2024-07-25/issues/2269#issuecomment-136867): > This build failure on FreeBSD 10 would be fixed by <https://tahoe-lafs.org/trac/pycryptopp/ticket/85> Wait, how do we know that? "unknown use of instruction mnemonic without a size suffix" sounds as though it is from assembler code, but "'sys/epoll.h' file not found" doesn't.

daira commented

2014-08-07 14:08:40 +00:00

Author

Owner

Oh, but the epoll error wasn't what caused the build to fail.

manas commented

2014-08-09 22:31:30 +00:00

Author

Owner

Do you have any workarounds to recommend so that I can run Tahoe-LAFS on FreeBSD 10?

bawtA commented

2014-10-01 06:28:51 +00:00

Author

Owner

I'm also interested in a workaround so I can use Tahoe-LAFS on FreeBSD 10. If there is no workaround, will this be fixed in v1.11?

daira commented

2014-10-02 01:17:04 +00:00

Author

Owner

This is a pycryptopp bug. The pycryptopp ticket (https://tahoe-lafs.org/trac/pycryptopp/ticket/85) seems to have got stalled, I'm not sure why.

This is a pycryptopp bug. The pycryptopp ticket (<https://tahoe-lafs.org/trac/pycryptopp/ticket/85>) seems to have got stalled, I'm not sure why.

cloud_trouble commented

2014-11-30 07:32:53 +00:00

Author

Owner

Basic steps (on FreeBSD 10):

install debootstrap from sysutils/debootstrap
mkdir /path/to/jail
debootstrap jessie /path/to/jail
kldload linprocfs (and others)
mount -t linprocfs none /path/to/jail/proc (same for dev and sys)
jail /path/to/jail jail_name jail_IP /etc/init.d/rc 2
jexec JID /bin/sh
apt-get install tahoe-lafs
create non-root user and configure tahoe-lafs.

Search for "FreeBSD Debian jail" for better details.

I found a workaround for this issue. You can run tahoe-lafs on FreeBSD using a Debian kFreeBSD jail. Just create a debian jail with debootstrap from ports/sysutils/debootstrap and then install tahoe-lafs using apt-get install tahoe-lafs. Basic steps (on FreeBSD 10): install debootstrap from sysutils/debootstrap mkdir /path/to/jail debootstrap jessie /path/to/jail kldload linprocfs (and others) mount -t linprocfs none /path/to/jail/proc (same for dev and sys) jail /path/to/jail jail_name jail_IP /etc/init.d/rc 2 jexec JID /bin/sh apt-get install tahoe-lafs create non-root user and configure tahoe-lafs. Search for "FreeBSD Debian jail" for better details.

manas commented

2015-01-21 18:42:07 +00:00

Author

Owner

I got the email about the planned 1.10.1 release.

Will this issue be fixed in time for the release?

I got the email about the planned 1.10.1 release. Will this issue be fixed in time for the release?

daira commented

2015-01-21 20:06:14 +00:00

Author

Owner

The problem is actually with pycryptopp, so it's independent of the Tahoe-LAFS release (and a "quickstart" build will normally pick up the latest pycryptopp version). Nevertheless we should try to fix https://tahoe-lafs.org/trac/pycryptopp/ticket/85 soon.

The problem is actually with pycryptopp, so it's independent of the Tahoe-LAFS release (and a "quickstart" build will normally pick up the latest pycryptopp version). Nevertheless we should try to fix <https://tahoe-lafs.org/trac/pycryptopp/ticket/85> soon.

tahoe-lafs added

packaging

and removed

code

labels 2015-04-14 07:06:16 +00:00

tahoe-lafs modified the milestone from undecided to soon (release n/a)

2015-04-14 07:06:16 +00:00

manas commented

2015-05-04 21:03:38 +00:00

Author

Owner

Bumping this so that it gets some attention.

daira commented

2015-05-04 21:30:43 +00:00

Author

Owner

Thanks for the reminder. The current status is that the pull request https://github.com/tahoe-lafs/pycryptopp/pull/26 has review comments and needs more work.

Thanks for the reminder. The current status is that the pull request <https://github.com/tahoe-lafs/pycryptopp/pull/26> has review comments and needs more work.

exarkun commented

2020-01-17 15:18:13 +00:00

Author

Owner

pycryptopp is no longer a dependency of Tahoe-LAFS.

tahoe-lafs added the

was already fixed

label 2020-01-17 15:18:13 +00:00

exarkun closed this issue

2020-01-17 15:18:13 +00:00