From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C5C1D39894FA; Thu, 8 Jul 2021 21:20:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C5C1D39894FA From: "lancethepants at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/101246] gccgo cross-compiler targeting arm fails to build with gcc 11. Missing structs in runtime.inc. Using uclibc-ng Date: Thu, 08 Jul 2021 21:20:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 11.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lancethepants at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 21:20:02 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101246 --- Comment #5 from Lance Fredrickson --- Just to check another architecture, I tried building gccgo-11 for x86_64 and uclibc-ng. With gcc-11 I get the same build-time error with x86_64 as I did with arm.=20 gccgo-10 for x86_64 & uclibc-ng did build, but when compiling a simple prog= ram I get a few undefined errors I don't have with arm. undefined reference to `__wrap_pthread_create' undefined reference to `__morestack_block_signals' undefined reference to `__generic_morestack' undefined reference to `__morestack_unblock_signals' Probably needs to be its own bug report. Not sure if gcc-10 will see more releases, but I would guess it would still be present in gcc-11 if it built. I hope uclibc-ng still gets some love from gcc and is supported. It plays = nice with old kernels, has more supported targets, and is still actively develop= ed.=