ROM with open-source tools
This guide details the technical requirements for deploying a stock ROM 2.4b6 codebase on a modern Linux environment, focusing on resolving legacy C compiler incompatibilities and directory structure assumptions that cause boot-time crashes.
Modernize Makefile and Compiler Flags
Stock ROM Makefile uses outdated flags and hardcoded paths. You must add -lcrypt to the linker flags because the crypt function is no longer part of the standard glibc. Additionally, add -Wno-unused-result to suppress warnings that modern GCC treats as errors when dealing with legacy file I/O code.
CC = gcc
PROF = -O -g
NOCRYPT =
L_FLAGS = $(PROF) -lcrypt
C_FLAGS = -Wall $(PROF) $(NOCRYPT) -Wno-unused-result -Wno-pointer-sign⚠ Common Pitfalls
- •Failure to include -lcrypt will result in 'undefined reference to crypt' errors during the linking phase.
Resolve Implicit Function Declarations
Modern C standards (C99 and later) require all functions to be declared before use. ROM 2.4 relies on many implicit declarations. You must add standard headers to merc.h to cover exit(), read(), write(), and close().
#include <stdlib.h>
#include <unistd.h>
#include <time.h>
#include <string.h>⚠ Common Pitfalls
- •Missing unistd.h will cause the build to fail on systems using GCC 10 or later due to the removal of implicit function declarations.
Fix Const Char Pointer Discards
ROM's handling of string literals frequently discards the 'const' qualifier, which triggers errors in modern compilers. You must update function signatures in merc.h and the corresponding .c files, or use explicit casting in the short term to allow compilation.
/* Change from: */
void log_string( char *str );
/* To: */
void log_string( const char *str );Initialize Area File Directory Structure
The ROM binary expects a specific relative directory structure. If the 'area' folder is not exactly one level above or in the same directory as the binary (depending on your startup script), the MUD will fail to find 'area.lst' and abort. Create the 'log' and 'player' directories manually as the stock code does not initialize them.
mkdir -p area log player god notes⚠ Common Pitfalls
- •ROM will crash with a 'Segmentation Fault' or 'File Not Found' if the 'player' directory is missing when the first user attempts to create a character.
Validate area.lst and Boot Sequence
The file 'area.lst' is a manifest. If a file is listed but does not exist on disk, ROM will throw a 'Bug' message and terminate. Open 'area.lst' and ensure every .are file matches the case-sensitive filename in the directory.
help.are
social.are
rom.are
group.are
$
⚠ Common Pitfalls
- •Stock ROM area files often use lowercase, but some archives unzip with mixed case. Linux is case-sensitive; ensure the manifest and filesystem match exactly.
Execute and Monitor Initial Boot
Run the binary from the area directory. Use the port argument (default is 4000). Immediately check the stderr output or the generated log file for 'Bug' entries, which indicate malformed vnums or missing help files.
cd area
../src/rom 4000 > ../log/boot.log 2>&1 &What you built
Successfully compiling and booting ROM 2.4 on a modern system requires bridging the gap between 1990s C practices and current compiler strictness. Once the MUD is running, your next priority should be implementing an OLC (On-Line Creation) patch, as the stock codebase requires manual editing of area files and a full reboot to see changes.
.