Hi Pelle:
Thanks for the update.
Running
Pelles C 13.0.0 RC2
on
Windows 11 24H2
This code:
/****************************************************************************
* *
* Filename: hello.c *
* *
* Purpose : Standard C sample for Pelles C for Windows. *
* *
* History : Date Reason *
* 02-09-10 Created *
* *
****************************************************************************/
#include <windows.h>
#include <stdio.h>
/* entry point */
int main(void)
{
printf("Hello, world!\n");
return 0;
}
Compiled with:
"C:\Program Files\PellesC\Bin\pocc.exe" /Gd /Go /MT /O2 /utf-8 /W2 /Ze /Zx /Tamd64-coff hello.c
Errors as:
Setting 64-bit environment for Pelles C...
Compiling "E:\T\hello.c" with Pelles C pocc.exe
C:\Program Files\PellesC\Include\Win\wow64apiset.h(1): fatal error #1065: Failed converting input from 'UTF-8'.
Linking ................
POLINK: fatal error: File not found: 'E:\T\hello.obj'.
The same hello.c code compiled without the /utf-8 option
"C:\Program Files\PellesC\Bin\pocc.exe" /Gd /Go /MT /O2 /W2 /Ze /Zx /Tamd64-coff hello.c
Errors as:
Setting 64-bit environment for Pelles C...
Compiling "E:\T\hello.c" with Pelles C pocc.exe
C:\Program Files\PellesC\Include\Win\wow64apiset.h(1): fatal error #1065: Failed converting input from 'ANSI'.
Linking ................
POLINK: fatal error: File not found: 'E:\T\hello.obj'.
If the C:\Program Files\PellesC\Include\Win\wow64apiset.h file is loaded into an editor and saved in UTF-8 No BOM format, then there is no error compiling with the /utf-8 option.
Hello Robert,
Thank you.
"Interesting" problem. In the comment on line 8, in <wow64apiset.h>, there is a typo: a garbage "tick" character with byte code 180. This looks too much like the beginning of a (broken) codepoint, causing a conversion from UTF-8 to UTF-16 to fail.
I will fix this.