public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lancethepants at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-101246-4-fQ1YfwYcoT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101246-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101246

--- Comment #5 from Lance Fredrickson <lancethepants at gmail dot com> ---
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. 

gccgo-10 for x86_64 & uclibc-ng did build, but when compiling a simple program
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 developed.

  parent reply	other threads:[~2021-07-08 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 19:17 [Bug go/101246] New: " lancethepants at gmail dot com
2021-06-28 19:25 ` [Bug go/101246] " ian at airs dot com
2021-06-28 20:36 ` lancethepants at gmail dot com
2021-06-28 20:42 ` ian at airs dot com
2021-06-28 20:48 ` lancethepants at gmail dot com
2021-07-08 21:20 ` lancethepants at gmail dot com [this message]
2021-08-19 19:36 ` lancethepants at gmail dot com
2022-02-23 16:55 ` lancethepants at gmail dot com
2022-03-04 18:47 ` cvs-commit at gcc dot gnu.org
2022-03-04 18:53 ` lancethepants at gmail dot com
2022-03-04 18:56 ` ian at airs dot com

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-101246-4-fQ1YfwYcoT@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: link
Be 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).