The instructions in "Installing Tahoe" do not mention C compiler requirement. #701
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#701
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On my recently created ubuntu server edition 9.04 install, I just followed the directions on "Installing Tahoe" found here:
http://allmydata.org/source/tahoe/trunk/docs/install.htmlhttp://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst
Running "python setup.py build" ends with with:
distutils.errors.DistutilsError: Setup script exited with error: command 'gcc' failed with exit status 1
Add brief mention of a C compiler requirement to "Installing Tahoe" (or perhaps the "
InstallDetails" "AdvancedInstall" wiki page).I misunderstood the build failure, and the solution was to install the python development headers. I see that from the InstallDetails page, if I follow the DownloadDebianPackages link, then scroll to the section on building from source on debian, it mentions the python-dev package.
Perhaps the "Installing Tahoe" page could clarify that the full python C development environment is required?
Here's the relevant snippet:
The intent (since changeset:d45780faf085fb55) is that building Tahoe doesn't require
g++
orPython.h
. For that to work, however, requires that all the dependencies either happen to already be installed or else get installed from a binary egg at build time. What platform are you on, and what dependenc(y|ies) are failing to install from binaries?Oh, by the way, I see that our collection of binary eggs is commented-out in source:setup.cfg. Could you please try commenting-in the line that tells
setup.py
to look in a certain directory on the tahoe test grid for binary eggs?The reason it is commented-out is that the tahoe test grid is too unreliable (it sometimes stalls for tens of minutes due to some transient storage server having disconnected without sending a TCP FIN packet, I think). If commenting that in fixes your build issue then maybe we could copy all those binary eggs over to the volunteer grid.
AdvancedInstall says: "Several of these [libraries]third-party use compiled C code, so they do require a compile step."
There's also wiki/FAQ#Q26_compile_error.