public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/108682] libffi needs to merge upstream to get LoongArch support Date: Fri, 03 Mar 2023 07:54:42 +0000 [thread overview] Message-ID: <bug-108682-4-EEorqAhHgV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108682-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682 --- Comment #2 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- I applied the LoongArch port patch (upstream PR 678, config.guess and config.sub changes stripped and Makefile.am conflict resolved manually) and use autogen.sh to regenerate the build system. But libgo build still fails with: libtool: compile: /home/xry111/git-repos/gcc-build/./gcc/gccgo -B/home/xry111/git-repos/gcc-build/./gcc/ -B/home/xry111/gcc-trunk/loongarch64-unknown-linux-gnu/bin/ -B/home/xry111/gcc-trunk/loongarch64-unknown-linux-gnu/lib/ -isystem /home/xry111/gcc-trunk/loongarch64-unknown-linux-gnu/include -isystem /home/xry111/gcc-trunk/loongarch64-unknown-linux-gnu/sys-include -O2 -g -I . -c -fgo-pkgpath=internal/goarch ../../../gcc/libgo/go/internal/goarch/goarch.go zgoarch.go -fPIC -o internal/.libs/goarch.o zgoarch.go:7:14: error: expected ‘;’ or ‘)’ or newline 7 | _BigEndian = | ^ zgoarch.go:7:3: error: reference to undefined name ‘_BigEndian’ 7 | _BigEndian = | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:18:19: error: reference to undefined name ‘_BigEndian’ 18 | const BigEndian = _BigEndian | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:21:29: error: reference to undefined name ‘_DefaultPhysPageSize’ 21 | const DefaultPhysPageSize = _DefaultPhysPageSize | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:25:19: error: reference to undefined name ‘_PCQuantum’ 25 | const PCQuantum = _PCQuantum | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:28:20: error: reference to undefined name ‘_Int64Align’ 28 | const Int64Align = _Int64Align | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:35:22: error: reference to undefined name ‘_MinFrameSize’ 35 | const MinFrameSize = _MinFrameSize | ^ ../../../gcc/libgo/go/internal/goarch/goarch.go:39:20: error: reference to undefined name ‘_StackAlign’ 39 | const StackAlign = _StackAlign | ^
next prev parent reply other threads:[~2023-03-03 7:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-06 10:08 [Bug libffi/108682] New: " robinlee.sysu at gmail dot com 2023-03-03 4:14 ` [Bug libffi/108682] " xry111 at gcc dot gnu.org 2023-03-03 4:16 ` xry111 at gcc dot gnu.org 2023-03-03 7:54 ` xry111 at gcc dot gnu.org [this message] 2023-03-03 8:33 ` schwab@linux-m68k.org 2023-03-03 8:45 ` xry111 at gcc dot gnu.org 2023-05-22 6:28 ` xry111 at gcc dot gnu.org 2023-05-22 16:34 ` ian at airs dot com 2023-05-22 16:34 ` ian at airs dot com 2023-05-23 8:17 ` xry111 at gcc dot gnu.org 2023-05-23 16:22 ` ian at airs dot com 2023-05-24 7:40 ` xry111 at gcc dot gnu.org 2023-08-23 6:16 ` cvs-commit at gcc dot gnu.org 2023-08-23 14:12 ` xry111 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-108682-4-EEorqAhHgV@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).