diff options
| author | Andrea Gelmini <andrea.gelmini@gelma.net> | 2017-12-19 21:31:10 +0100 |
|---|---|---|
| committer | Julien Nabet <serval2412@yahoo.fr> | 2017-12-20 10:43:47 +0100 |
| commit | e4404de89548bcf7e632b31f4c3461733e2684d3 (patch) | |
| tree | be89d61ebef6e954d06e4b8ec6449da9a0d14339 /configure.ac | |
| parent | 3ee517d480b60c0db59bf43f6f52c27f7368d883 (diff) | |
Fix typos
Change-Id: I361b5283b092171eaaaf46fa3c1fb13faa53bd7a
Reviewed-on: https://gerrit.libreoffice.org/46821
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index 4e00de777ec4..f88481b6c45e 100644 --- a/configure.ac +++ b/configure.ac @@ -6060,7 +6060,7 @@ elif test "$GCC" = "yes" -o "$COM_IS_CLANG" = TRUE; then dnl The only reason why libstdc++ headers fail with Clang in C++11 mode is because they dnl use the __float128 type that Clang doesn't know (libstdc++ checks whether __float128 dnl is available during its build, but it's usually built using GCC, and so c++config.h - dnl hardcodes __float128 being supported). At least for some older libstc++, the only + dnl hardcodes __float128 being supported). At least for some older libstdc++, the only dnl place where __float128 is used is in a template specialization, -D__float128=void dnl will avoid the problem there while still causing a problem if somebody actually uses dnl the type. (But some later libstdc++ are known to use __float128 also in algorithm -> |