public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus.boeck02 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/100598] New: MinGW Canadian cross toolchain fails to build due to missing BASEVER in genversion.c Date: Fri, 14 May 2021 08:57:02 +0000 [thread overview] Message-ID: <bug-100598-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100598 Bug ID: 100598 Summary: MinGW Canadian cross toolchain fails to build due to missing BASEVER in genversion.c Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: markus.boeck02 at gmail dot com Target Milestone: --- I am currently unable to build trunk version of gcc due to a compiler error when compiling the file genversion.c. This happens when crosscompiling a GCC toolchain for a x86_64-w64-mingw32 host. The compiler error: ../../gcc/genversion.c: In function ‘int main()’: ../../gcc/genversion.c:37:20: error: ‘BASEVER’ was not declared in this scope char basever[] = BASEVER; ^~~~~~~ ../../gcc/genversion.c:50:11: error: ‘DEVPHASE’ was not declared in this scope phase = DEVPHASE[0]; ^~~~~~~~ ../../gcc/genversion.c:73:39: error: expected ‘)’ before ‘BASEVER’ printf ("#define version_string \"" BASEVER DATESTAMP DEVPHASE REVISION "\"\n"); ^~~~~~~ ../../gcc/genversion.c:74:42: error: expected ‘)’ before ‘PKGVERSION’ printf ("#define pkgversion_string \"" PKGVERSION "\"\n\n"); ^~~~~~~~~~ ../../gcc/genversion.c:82:39: error: expected ‘)’ before ‘BUGURL’ printf ("#define bug_report_url \"" BUGURL "\"\n\n"); ^~~~~~ make[2]: *** [build/genversion.o] Error 1 make[2]: *** Waiting for unfinished jobs.... The compile command used in the build is: g++ -c -DIN_GCC -DGENERATOR_FILE -I. -Ibuild -I../../gcc -I../../gcc/build -I../../gcc/../include -I../../gcc/../libcpp/include -I/mnt/c/GCC-Build/NewestLinux/Libraries/include \ -o build/genversion.o ../../gcc/genversion.c where g++ is 7.5.0 shipped with Ubuntu 18.04 which I am using as build environment. The configure command used is: ../configure --target=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --disable-bootstrap --enable-libstdcxx-debug --with-tune=znver1 --prefix=/mnt/c/GCC --with-sysroot=/mnt/c/GCC-Build/NewestLinux --with-build-sysroot=/mnt/c/GCC-Build/NewestLinux --disable-libstdcxx-pch --disable-multilib --enable-libgomp --with-cross-host --with-libiconv-prefix=/mnt/c/GCC-Build/NewestLinux/Libraries --disable-libstdcxx-verbose --enable-languages=c,c++,fortran,lto,objc,obj-c++,d --disable-nls --disable-win32-registry --enable-shared --with-gnu-as --with-gnu-ld --enable-threads=posix --program-suffix=-12 --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-__cxa_atexit --enable-plugin --program-prefix= --enable-checking=release
next reply other threads:[~2021-05-14 8:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-14 8:57 markus.boeck02 at gmail dot com [this message] 2021-05-14 9:07 ` [Bug other/100598] " marxin at gcc dot gnu.org 2021-05-14 17:24 ` burnus at gcc dot gnu.org 2021-05-14 21:26 ` [Bug other/100598] [12 Regression] " burnus at gcc dot gnu.org 2021-05-16 1:52 ` unlvsur at live dot com 2021-05-17 12:17 ` rguenth at gcc dot gnu.org 2021-05-18 9:56 ` cvs-commit at gcc dot gnu.org 2021-05-18 9:59 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-100598-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).