From 74deedb0fd9f10df336536d7f9857e7ba4272662 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Sun, 20 Oct 2024 15:52:43 -0700 Subject: [PATCH] Shorten another FAQ answer --- faq.html | 5 ++--- faq.md | 6 ++---- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/faq.html b/faq.html index 28db77cc7..51ff7f5bc 100644 --- a/faq.html +++ b/faq.html @@ -3628,9 +3628,8 @@ for more information about pull requests.
If the entry requires gcc and you did not explicitly install gcc in macOS you
will not be able to run or use these entries. This is because macOS gcc is
-actually clang, even /usr/bin/gcc.
That being said many (if not most) of these entries have been fixed and some -others will be looked at, when found.
+actually clang, even/usr/bin/gcc. That being said many (if not most) of these
+entries have been fixed.
In some cases the bugs.html file may note a known macOS problem with an entry. Should you manage to port the entry, and assuming your changes also attempt to preserve the original intent of the IOCCC entry, we would diff --git a/faq.md b/faq.md index d613ac4ea..c99d01206 100644 --- a/faq.md +++ b/faq.md @@ -4464,10 +4464,8 @@ Jump to: [top](#) If the entry requires gcc and you did not explicitly install gcc in macOS you will not be able to run or use these entries. This is because macOS gcc is -actually clang, even `/usr/bin/gcc`. - -That being said many (if not most) of these entries have been fixed and some -others will be looked at, when found. +actually clang, even `/usr/bin/gcc`. That being said many (if not most) of these +entries have been fixed. In some cases the [bugs.html](bugs.html) file may note a known macOS problem with an entry. Should you manage to port the entry, and assuming your changes