public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "winterjasmine1 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109562] New: Failed to build native GCC 12.2.0 on RISC-V64 linux machine Date: Thu, 20 Apr 2023 02:40:10 +0000 [thread overview] Message-ID: <bug-109562-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109562 Bug ID: 109562 Summary: Failed to build native GCC 12.2.0 on RISC-V64 linux machine Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: winterjasmine1 at hotmail dot com Target Milestone: --- Created attachment 54885 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54885&action=edit error log when building GCC 12.2.0 natively on RISC-V linux machine Failed to build native GCC 12.2.0 on RISC-V64 linux machine. Steps: ``` $sudo apt-get install autoconf automake autotools-dev curl python3 libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev $ cd gcc-12.2.0 $ contrib/download_prerequisites $ mkdir build && cd build $ ../configure --enable-languages=c,c++,fortran --prefix=$HOME/opt/gcc-12.2.0 --disable-multilib $ make -j4 ``` error info: ``` /usr/include/stdio.h:592:14: error: old-style parameter declarations in prototyped function definition 592 | extern char *fgets (char *__restrict __s, int __n, FILE *__restrict __stream) | ^~~~~ ../../../libgcc/libgcc2.c:2457: error: expected ‘{’ at end of input ../../../libgcc/libgcc2.c:2457: warning: control reaches end of non-void function [-Wreturn-type] make[3]: *** [Makefile:501: _ashrdi3.o] Error 1 ``` The full error log is attached.
next reply other threads:[~2023-04-20 2:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-20 2:40 winterjasmine1 at hotmail dot com [this message] 2023-04-20 2:44 ` [Bug target/109562] " pinskia 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-109562-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).