Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Timo Ley
synapse
Commits
0c0ae2e8
Commit
0c0ae2e8
authored
10 years ago
by
Matthew Hodgson
Browse files
Options
Downloads
Patches
Plain Diff
clean up TurnedToDust's ArchLinux notes a bit
parent
52eb5d6a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.rst
+26
-18
26 additions, 18 deletions
README.rst
with
26 additions
and
18 deletions
README.rst
+
26
−
18
View file @
0c0ae2e8
...
@@ -154,29 +154,37 @@ On OSX, if you encounter clang: error: unknown argument: '-mno-fused-madd' you
...
@@ -154,29 +154,37 @@ On OSX, if you encounter clang: error: unknown argument: '-mno-fused-madd' you
will need to export CFLAGS=-Qunused-arguments.
will need to export CFLAGS=-Qunused-arguments.
ArchLinux
ArchLinux
--------------
---------
ArchLinux with the default installation of prerequisites, and your System itself. The installation may encounter a few Hiccups.
Installation on ArchLinux may encounter a few hiccups as Arch defaults to
python 3, but synapse currently assumes python 2.7 by default.
p
ython2.7 is Needed and I believe by default Arch uses Python3.
p
ip may be outdated (6.0.7-1 and needs to be upgraded to 6.0.8-1 )::
pip is outdated (6.0.7-1 and needs to be upgraded to 6.0.8-1 ):
$ sudo pip2.7 install --upgrade pip
- $ sudo pip2.7 install --upgrade pip
You also may need to call 2.7 again during the install request:
You also may need to explicitly specify python 2.7 again during the install
- $ sudo pip2.7 install --process-dependency-links https://github.com/matrix-org/synapse/tarball/master
request::
$ pip2.7 install --process-dependency-links \
https://github.com/matrix-org/synapse/tarball/master
If you encounter an error with lib bcrypt Causing an Wrong Elf Class: ELFCLASS32 (x64 Systems):
If you encounter an error with lib bcrypt causing an Wrong ELF Class:
you need to remove py-bcrypt itself and then reinstall it to correctly compile under your architecture
ELFCLASS32 (x64 Systems), you may need to reinstall py-bcrypt to correctly
- $ sudo pip2.7 uninstall py-bcrypt
compile it under the right architecture. (This should not be needed if
- $ sudo pip2.7 install py-bcrypt
installing under virtualenv)::
$ sudo pip2.7 uninstall py-bcrypt
$ sudo pip2.7 install py-bcrypt
During setup of homeserver you need to call (depending) python2.7 directly again:
During setup of homeserver you need to call python2.7 directly again::
- $ sudo python2.7 -m synapse.app.homeserver \
$ python2.7 -m synapse.app.homeserver \
--server-name machine.my.domain.name \
--server-name machine.my.domain.name \
--config-path homeserver.yaml \
--config-path homeserver.yaml \
--generate-config
--generate-config
S
ubstituting your host and domain name as appropriate.
...s
ubstituting your host and domain name as appropriate.
Windows Install
Windows Install
---------------
---------------
...
@@ -239,12 +247,12 @@ fix try re-installing from PyPI or directly from
...
@@ -239,12 +247,12 @@ fix try re-installing from PyPI or directly from
ArchLinux
ArchLinux
---------
---------
If running $ synctl start , causes the following error
"subprocess.CalledProcessError: Command '['python', '-m', 'synapse.app.homeserver', '--daemonize', '-c', 'homeserver.yaml', '--pid-file', 'homeserver.pid']' returned non-zero exit status 1"
You need to call 2.7 again by directly using
If running `$ synctl start` fails wit 'returned non-zero exit status 1', you will need to explicitly call Python2.7 - either running as::
- $ python2.7 -m synapse.app.homeserver --daemonize -c homeserver.yaml --pid-file homeserver.pid
$ python2.7 -m synapse.app.homeserver --daemonize -c homeserver.yaml --pid-file homeserver.pid
...or by editing synctl with the correct python executable.
Homeserver Development
Homeserver Development
======================
======================
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment