monero-project/monero

Installing Monero from a package

DISCLAIMER: These packages are not part of this repository or maintained by this project's contributors, and as such, do not go through the same review process to ensure their trustworthiness and security.

Packaging for your favorite distribution would be a welcome contribution!

• Debian 12 (Bookworm) or later
• Arch Linux:
• Alpine Linux:
• macOS (homebrew)

sudo apt install monero

Dependencies

The following table summarizes the tools and libraries required to build. A few of the libraries are also included in this repository (marked as "Vendored"). By default, the build uses the library installed on the system and ignores the vendored sources. However, if no library is found installed on the system, then the vendored source will be built and used. The vendored sources are also used for statically-linked builds because distribution packages often include only shared library binaries (.so) but not static library archives (.a).

Install all dependencies at once on macOS with the provided Brewfile:

• GCC — 7 — NO — build-essential — base-devel — base-devel — gcc — NO
• CMake — 3.10 — NO — cmake — cmake — cmake — cmake — NO
• pkg-config — any — NO — pkg-config — base-devel — base-devel — pkgconf — NO
• Boost — 1.69 — NO — libboost-all-dev — boost — boost-devel — boost-devel — NO — C++ libraries
• OpenSSL — 1.1.1 — NO — libssl-dev — openssl — openssl-devel — openssl-devel — NO — cryptography
• libzmq — 4.2.0 — NO — libzmq3-dev — zeromq — zeromq-devel — zeromq-devel — NO — ZeroMQ library
• libunbound — 1.4.16 — NO — libunbound-dev — unbound — unbound-devel — unbound-devel — NO — DNS resolver
• libsodium — ? — NO — libsodium-dev — libsodium — libsodium-devel — libsodium-devel — NO — cryptography
• libunwind — any — NO — libunwind-dev — libunwind — libunwind-devel — libunwind-devel — YES — Stack traces
• libreadline — 6.3.0 — NO — libreadline-dev — readline — readline-devel — readline-devel — YES — Input editing
• GTest — 1.5 — YES — libgtest-dev — gtest — gtest-devel — gtest-devel — YES — Test suite
• ccache — any — NO — ccache — ccache — ccache — ccache — YES — Compil. cache
• Doxygen — any — NO — doxygen — doxygen — doxygen — doxygen — YES — Documentation
• Graphviz — any — NO — graphviz — graphviz — graphviz — graphviz — YES — Documentation

Obtaining stack traces and core dumps on Unix systems

We generally use the tool gdb (GNU debugger) to provide stack trace functionality, and ulimit to provide core dumps in builds which crash or segfault.

Type thread apply all bt within gdb in order to obtain the stack trace

Enter ulimit -c unlimited on the command line to enable unlimited filesizes for core dumps

Enter echo core | sudo tee /proc/sys/kernel/corepattern to stop cores from being hijacked by other tools

• To use gdb in order to obtain a stack trace for a build that has stalled:
• If however the core dumps or segfaults:
• If a program crashed and cores are managed by systemd, the following can also get a stack trace for that crash:

Table of Contents

• Development resources
• Vulnerability response
• Announcements
• Introduction
• About this project
• Supporting the project
• Contributing
• Scheduled software/network upgrades
• Release staging schedule and protocol
• Compiling Monero from source
• Dependencies
• Guix builds
• Installing Monero from a package
• Running monerod

Development resources

• Web: getmonero.org
• Mail: [email protected]
• GitHub: https://github.com/monero-project/monero
• IRC: #monero-dev on Libera
• It is HIGHLY recommended that you join the #monero-dev IRC channel if you are developing software that uses Monero. Due to the nature of this open source software project, joining this channel and idl

Vulnerability response

• Our Vulnerability Response Process encourages responsible disclosure
• We are also available via HackerOne
• Monero is continuously fuzzed by OSS-Fuzz