-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--with-default-msvcrt=ucrt breaks libgomp build #520
Comments
Well, I think the problem is caused by _UCRT... |
/* 7.8.1 Macros for format specifiers
*
* MS runtime does not yet understand C9x standard "ll"
* length specifier. It appears to treat "ll" as "l".
* The non-standard I64 length specifier causes warning in GCC,
* but understood by MS runtime functions.
*/
#if defined(_UCRT) || __USE_MINGW_ANSI_STDIO
#define PRId64 "lld"
#define PRIi64 "lli"
#define PRIo64 "llo"
#define PRIu64 "llu"
#define PRIx64 "llx"
#define PRIX64 "llX"
#else
#define PRId64 "I64d"
#define PRIi64 "I64i"
#define PRIo64 "I64o"
#define PRIu64 "I64u"
#define PRIx64 "I64x"
#define PRIX64 "I64X"
#endif |
I think it should be |
IDK :( . the second answer to the Stack Overflow question says:
|
ah right |
@Prince213 look at this: https://sourceforge.net/p/mingw-w64/bugs/853/ |
Errors related to env.c now disappears, but new ones come:
|
Just some extra information: I think I ran into a related issue. I got: My build was: |
@lurobi please try |
@Prince213 any ideas? |
@Prince213 thank you! @lurobi can you confirm please? |
Confirmed: I was able to build gcc 9 and 10 branches on develop because of
that patch. I hit an unrelated issue which prevented me from compiling gcc
trunk.
I am not specifically setting that msvcrt flag if that is relevant.
…On Thu, Feb 11, 2021, 2:56 PM niXman ***@***.***> wrote:
@Prince213 <https://github.com/Prince213> thank you!
@lurobi <https://github.com/lurobi> can you confirm please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#520 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6JG4NIH45IOJFAYTKGD2TS6Q76VANCNFSM4P4DCCFA>
.
|
@lurobi Please try with --with-default-msvcrt=ucrt as this problem is probably related to UCRT. |
I am unable to compile gcc using Command:
|
To disable |
Here is the upstream fix: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c51f1e7427e6a5ae2a6d82b5a790df77a3adc99a |
Seeing the same errors with gcc 10.3.0 and UCRT: In file included from /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/affinity-fmt.c:68: /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/../../affinity-fmt.c: In function 'gomp_display_affinity': /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/../../affinity-fmt.c:388:22: error: unknown conversion type character 'l' in format [-Werror=format=] 388 | sprintf (buf, "0x%" PRIx64, (uint64_t) gomp_integral (handle)); | ^~~~~ In file included from /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/affinity-fmt.c:34: /usr/i686-w64-mingw32/include/inttypes.h:37:18: note: format string is defined here 37 | #define PRIx64 "llx" | ^ In file included from /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/affinity-fmt.c:68: /home/build/mingw-w64-gcc/gcc/libgomp/config/mingw32/../../affinity-fmt.c:388:22: error: too many arguments for format [-Werror=format-extra-args] 388 | sprintf (buf, "0x%" PRIx64, (uint64_t) gomp_integral (handle)); | ^~~~~ Looking at |
Seeing the same error over here when not using
It seems another patch is necessary for that configuration to build, not that I'm interested in it, I'm trying to find the culprit for #498 and stumbled upon this, right now I can't find a way to build a toolchain using UCRT. |
Command:
./build --mode=gcc-10.2.0 --buildroot=/e/mingw1020 --no-multilib --no-extras --jobs=6 --rt-version=v7.0.0 --with-default-msvcrt=ucrt --enable-languages=c,c++ --threads=posix --exceptions=seh --arch=x86_64 --bin-compress
Log:
The text was updated successfully, but these errors were encountered: