|
From: | Riccardo Mottola |
Subject: | Re: Incompatible compiler option fexec-charset |
Date: | Wed, 07 Dec 2011 17:04:50 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 5.1; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5 |
Richard Frith-Macdonald wrote:
On 7 Dec 2011, at 14:40, Riccardo Mottola wrote:Hi, Richard Frith-Macdonald wrote:The check in the configure script (which breaks the build with clang now - apparently it was not tested before being committed)The script provides instruction on how to ignore the check for compilers which don't support the 'standard' gcc behaviors. That worked on my system when I tested it. I put that option in for old versions of gcc and because the latest info I managed to find for clang was that it didn't support characterset specifier flags and didn't check what characterset it was writing using for string literals.Just as information: the check fails on gcc 4.2.1 and I disabled it though the option. However, the man pages lists it as valid option.Hmm ... works for me with gcc-4.1.2 on CentOS, and 4.5.2 on windows, and a 4.7 snapshot on Debian. Most likely there's some problem in the test (though I guess there could be a problem with gcc-4.2.1) ... perhaps locale related in some way (though the test attempts to work in a common locale to avoid that)?
I get this error:configure:5233: gcc -o conftest -g -O2 -finput-charset=ISO-8859-1 -fexec-charset =UTF-8 -I/usr/GNUstep/System/Library/Headers -I/usr/GNUstep/Local/Library/Heade rs -I/usr/GNUstep/Local/Library/Headers -L/usr/GNUstep/System/Library/Libraries -L/usr/GNUstep/Local/Library/Libraries -L/usr/GNUstep/Local/Library/Libraries c
onftest.c >&5 cc1: error: no iconv implementation, cannot convert from ISO-8859-1 to UTF-8conftest.c:75:54: error: no iconv implementation, cannot convert from ISO-8859-1
to UTF-8I have iconv installed though, so I don't undersand what's going on. perhaps it is missing a certain kind of conversion? Also, I have iconv installed as an extra package, while gcc is part of the base system, so depending on an extra package is somehow strange (and it doesn't even work).
Riccardo
[Prev in Thread] | Current Thread | [Next in Thread] |