diff options
Diffstat (limited to 'solenv/gbuild')
| -rwxr-xr-x | solenv/gbuild/config.guess | 4 | ||||
| -rw-r--r-- | solenv/gbuild/platform/com_GCC_class.mk | 2 | ||||
| -rwxr-xr-x | solenv/gbuild/platform/unittest-failed-MACOSX.sh | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/solenv/gbuild/config.guess b/solenv/gbuild/config.guess index a7448442748c..61b5c7b0f3f7 100755 --- a/solenv/gbuild/config.guess +++ b/solenv/gbuild/config.guess @@ -1324,9 +1324,9 @@ EOF fi fi elif test "$UNAME_PROCESSOR" = i386 ; then - # Avoid executing cc on OS X 10.9, as it ships with a stub + # Avoid executing cc on macOS 10.9, as it ships with a stub # that puts up a graphical alert prompting to install - # developer tools. Any system running Mac OS X 10.7 or + # developer tools. Any system running macOS 10.7 or # later (Darwin 11 and later) is required to have a 64-bit # processor. This is not true of the ARM version of Darwin # that Apple uses in portable devices. diff --git a/solenv/gbuild/platform/com_GCC_class.mk b/solenv/gbuild/platform/com_GCC_class.mk index 4c3531934d5e..4b2786df1856 100644 --- a/solenv/gbuild/platform/com_GCC_class.mk +++ b/solenv/gbuild/platform/com_GCC_class.mk @@ -147,7 +147,7 @@ gb_ICU_PRECOMMAND := $(call gb_Helper_extend_ld_path,$(WORKDIR_FOR_BUILD)/Unpack # UIConfig class -# Mac OS X sort(1) cannot read a response file +# macOS sort(1) cannot read a response file define gb_UIConfig__command $(call gb_Helper_abbreviate_dirs,\ $(SORT) -u $(UI_IMAGELISTS) /dev/null > $@ \ diff --git a/solenv/gbuild/platform/unittest-failed-MACOSX.sh b/solenv/gbuild/platform/unittest-failed-MACOSX.sh index 7994dbd56b01..049da92b4c3c 100755 --- a/solenv/gbuild/platform/unittest-failed-MACOSX.sh +++ b/solenv/gbuild/platform/unittest-failed-MACOSX.sh @@ -19,7 +19,7 @@ cat << EOF Error: a unit test failed, please do one of: -make $1Test_$2 CPPUNITTRACE="lldb --" # for interactive debugging on OS X +make $1Test_$2 CPPUNITTRACE="lldb --" # for interactive debugging on macOS make $1Test_$2 VALGRIND=memcheck # for memory checking You can limit the execution to just one particular test by: |