Opened at 2014-08-02T22:09:08Z
Closed at 2020-01-17T15:18:13Z
#2269 closed defect (was already fixed)
Unable to build Tahoe-LAFS v1.10.0 on FreeBSD 10
Reported by: | manas | Owned by: | zooko |
---|---|---|---|
Priority: | normal | Milestone: | soon (release n/a) |
Component: | packaging | Version: | 1.10.0 |
Keywords: | freebsd jail build | Cc: | |
Launchpad Bug: |
Description
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
Change History (15)
comment:1 Changed at 2014-08-02T22:14:47Z by manas
comment:2 Changed at 2014-08-04T17:31:02Z by daira
See #2270 for the inability to add ticket attachments.
comment:3 follow-up: ↓ 4 Changed at 2014-08-05T05:21:28Z by zooko
This build failure on FreeBSD 10 would be fixed by https://tahoe-lafs.org/trac/pycryptopp/ticket/85
comment:4 in reply to: ↑ 3 Changed at 2014-08-07T14:06:43Z by daira
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.
comment:5 Changed at 2014-08-07T14:08:40Z by daira
Oh, but the epoll error wasn't what caused the build to fail.
comment:6 Changed at 2014-08-09T22:31:30Z by manas
Do you have any workarounds to recommend so that I can run Tahoe-LAFS on FreeBSD 10?
comment:7 Changed at 2014-10-01T06:28:51Z by bawtA
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?
comment:8 Changed at 2014-10-02T01:17:04Z by daira
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.
comment:9 Changed at 2014-11-30T07:32:53Z by cloud_trouble
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.
comment:10 Changed at 2015-01-21T18:42:07Z by manas
I got the email about the planned 1.10.1 release.
Will this issue be fixed in time for the release?
comment:11 Changed at 2015-01-21T20:06:14Z by daira
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.
comment:12 Changed at 2015-04-14T07:06:16Z by daira
- Component changed from code to packaging
- Keywords changed from freebsd,jail,build to freebsd jail build
- Milestone changed from undecided to soon (release n/a)
comment:13 Changed at 2015-05-04T21:03:38Z by manas
Bumping this so that it gets some attention.
comment:14 Changed at 2015-05-04T21:30:43Z by daira
- Owner set to zooko
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.
comment:15 Changed at 2020-01-17T15:18:13Z by exarkun
- Resolution set to was already fixed
- Status changed from new to closed
pycryptopp is no longer a dependency of Tahoe-LAFS.
The system here is not accepting attachments. Full log is here: http://pastebin.com/mePP3cXq