diff options
author | 2019-02-18 21:55:45 +1100 | |
---|---|---|
committer | 2019-02-18 21:55:45 +1100 | |
commit | 34ebe564b0d515ed05cfbdca9d31456b7f91d990 (patch) | |
tree | 314d7ff35c3c9551a1148a4a28e9159117cf659e /docs/source/initialsetup/compilingmame.rst | |
parent | 8ffff5d2d3bcebbdbefec2508ddd2ecd264a399a (diff) |
(nw) omission, formatting
Diffstat (limited to 'docs/source/initialsetup/compilingmame.rst')
-rw-r--r-- | docs/source/initialsetup/compilingmame.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/initialsetup/compilingmame.rst b/docs/source/initialsetup/compilingmame.rst index 44d416d3108..b8a854db322 100644 --- a/docs/source/initialsetup/compilingmame.rst +++ b/docs/source/initialsetup/compilingmame.rst @@ -438,7 +438,7 @@ 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: -**gcc -dM -E - | grep _FORTIFY_SOURCE** +**gcc -dM -E - < /dev/null | grep _FORTIFY_SOURCE** If ``_FORTIFY_SOURCE`` is defined to a non-zero value by default, you can work around it by adding **-U_FORTIFY_SOURCE** to the compiler flags (e.g. by using @@ -465,7 +465,7 @@ like this: **make TARGETOS=windows PTR64=1 OVERRIDE_CC=x86_64-w64-mingw32-gcc OVERRIDE_CXX=x86_64-w64-mingw32-g++ OVERRIDE_LD=x86_64-w64-mingw32-ld MINGW64=/usr** (The additional packages required for producing a standard MinGW32 x64 build on -a Fedora Linux host are `mingw64-gcc-c++`, `mingw64-winpthreads-static` and +a Fedora Linux host are ``mingw64-gcc-c++``, ``mingw64-winpthreads-static`` and their dependencies. Non-standard builds may require additional packages.) Using libc++ on Linux |