From 109c3705ffe306f99a070b4bb65bf86c2124eed5 Mon Sep 17 00:00:00 2001 From: Roman Donchenko Date: Wed, 10 Sep 2025 03:45:36 +0300 Subject: docs: fix assorted typos (#14152) --- docs/source/initialsetup/compilingmame.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/source/initialsetup') diff --git a/docs/source/initialsetup/compilingmame.rst b/docs/source/initialsetup/compilingmame.rst index a4559842b39..1e467fff552 100644 --- a/docs/source/initialsetup/compilingmame.rst +++ b/docs/source/initialsetup/compilingmame.rst @@ -577,7 +577,7 @@ Including subsets of supported systems SUBTARGET Set emulator subtarget to build. Some pre-defined subtargets are provided, using Lua scripts in *scripts/target/mame* and system driver filter files in - *src/mame*. User-defined substargets can be created using the **SOURCES** + *src/mame*. User-defined subtargets can be created using the **SOURCES** or **SOURCEFILTER** option. SOURCES Specify system driver source files and/or folders to include. Usually used @@ -762,7 +762,7 @@ the ``_FORTIFY_SOURCE`` macro is set in the RPM build environment, and not by distributing a modified version of GCC.) If you get compilation errors in ``bits/string_fortified.h`` you should first -ensure that the ``_FORTIY_SOURCE`` macro is defined via the environment (e.g. +ensure that the ``_FORTIFY_SOURCE`` macro is defined via the environment (e.g. a **CFLAGS** or **CXXFLAGS** environment variable). You can check to see whether the ``_FORTIFY_SOURCE`` macro is a built-in macro with your version of GCC with a command like this: -- cgit v1.2.3