gnustep/libs-base
0
0
Fork 0
mirror of https://github.com/gnustep/libs-base.git synced 2025-04-22 16:33:29 +00:00
Code Issues Projects Releases Packages Wiki Activity

improve warning about poor/no locale/characterset support in compiler

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@34309 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
rfm 2011-12-17 15:05:38 +00:00
parent 233003cff2
commit a4f98e5b2e
3 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
ChangeLog
View file

@ -1,3 +1,9 @@
2011-12-17 Richard Frith-Macdonald <rfm@gnu.org>
* configure.ac: Try to make detection of compilers which don't support
locale/characterset handling for string literals somewhat friendly.
* configure: regenerate
2011-12-17 Fred Kiefer <FredKiefer@gmx.de>
* Source/NSPortCoder.m (-versionForClassName:): Use NSInteger for

7
configure vendored
View file

@ -1489,7 +1489,7 @@ Optional Features:
Disable importing of an existing GNUstep config
file and use inbuilt defaults instead.
--disable-unicodeconstants
Permits the use of a compiler which does not support unicode
Ignores the use of a compiler which does not support unicode
string constants.
--enable-nxconstantstring
Enables the use of the NXConstantString class for old compilers.
@ -5268,9 +5268,8 @@ $as_echo "yes" >&6; };
else
{ $as_echo "$as_me:$LINENO: result: no" >&5
$as_echo "no" >&6; };
{ { $as_echo "$as_me:$LINENO: error: Your compiler does not appear to support UTF-8 string constants and any code which depends on non US-ASCII text in string constants would perform incorrectly. If you do not care about this (or you know your code will only ever produce ASCII or UTF-8 string literals), please confgure using --disable-unicodeconstants" >&5
$as_echo "$as_me: error: Your compiler does not appear to support UTF-8 string constants and any code which depends on non US-ASCII text in string constants would perform incorrectly. If you do not care about this (or you know your code will only ever produce ASCII or UTF-8 string literals), please confgure using --disable-unicodeconstants" >&2;}
{ (exit 1); exit 1; }; }
{ $as_echo "$as_me:$LINENO: WARNING: Your compiler does not appear to support locales or command line options to control handling of charactersets. This means that using any source code code containing non US-ASCII text in string literals may give unexpected results (or crashes) at runtime. However, as long as any such literals only use the UTF-8 characterset, this is unlikely to be a problem. Please confgure using --disable-unicodeconstants to avoid seeing this warning." >&5
$as_echo "$as_me: WARNING: Your compiler does not appear to support locales or command line options to control handling of charactersets. This means that using any source code code containing non US-ASCII text in string literals may give unexpected results (or crashes) at runtime. However, as long as any such literals only use the UTF-8 characterset, this is unlikely to be a problem. Please confgure using --disable-unicodeconstants to avoid seeing this warning." >&2;}
fi
fi
export LANG="$saved_LANG"

4
configure.ac
View file

@ -1031,7 +1031,7 @@ GS_EXEC_CHARSET=
GS_INPUT_CHARSET=
AC_ARG_ENABLE(unicodeconstants,
[ --disable-unicodeconstants
Permits the use of a compiler which does not support unicode
Ignores the use of a compiler which does not support unicode
string constants.],,)
if test "$enable_unicodeconstants" != "no"; then
AC_LANG_PUSH(C)
@ -1063,7 +1063,7 @@ if test "$enable_unicodeconstants" != "no"; then
GS_INPUT_CHARSET=-finput-charset=UTF-8
else
AC_MSG_RESULT([no]);
AC_MSG_ERROR([Your compiler does not appear to support UTF-8 string constants and any code which depends on non US-ASCII text in string constants would perform incorrectly. If you do not care about this (or you know your code will only ever produce ASCII or UTF-8 string literals), please confgure using --disable-unicodeconstants])
AC_MSG_WARN([Your compiler does not appear to support locales or command line options to control handling of charactersets. This means that using any source code code containing non US-ASCII text in string literals may give unexpected results (or crashes) at runtime. However, as long as any such literals only use the UTF-8 characterset, this is unlikely to be a problem. Please confgure using --disable-unicodeconstants to avoid seeing this warning.])
fi
fi
export LANG="$saved_LANG"