How to Compile and Run Redis on ARM: Step‑by‑Step Guide
Learn how to compile Redis from source and install it on an ARM-based system running Euler OS 2.8, covering environment setup, dependency building, configuration, service startup, and basic testing with redis-cli, demonstrating that the process mirrors standard installations.
1. Basic Environment Information
OS: Euler OS 2.8
CPU: ARM
2. Compile and Install Redis
· Download the Redis source code: wget http://download.redis.io/releases/redis-4.0.9.tar.gz · Extract the archive: tar -zxvf redis-4.0.9.tar.gz · Enter the deps directory: cd redis-4.0.9/deps · Build Redis dependencies: make -j4 hiredis lua jemalloc linenoise · Return to the root directory and compile Redis:
cd ..make -j4make install3. Configure and Run Redis
· Copy the default configuration file: cp redis.conf /usr/local/etc/ · Edit the configuration to enable daemon mode (change daemonize no to daemonize yes): vim /usr/local/etc/redis.conf · Start the Redis server: service redis start The system will display messages such as:
Starting Redis server...20525:C 19Jun 20:43:25.941 # Redis is starting20525:C 19Jun 20:43:25.941 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=20525, just started20525:C 19Jun 20:43:25.941 # Configuration loaded4. Test Redis
· Connect with redis-cli and perform a simple key‑value operation:
redis-cli127.0.0.1:6379> set test armOK 127.0.0.1:6379> get test "arm" 127.0.0.1:6379> del test (integer) 1 127.0.0.1:6379> get test (nil)
5. Summary
The compilation and execution of Redis on an ARM platform involve no major differences from other architectures; a few straightforward steps are sufficient to install and run Redis successfully.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
