From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] gcc fails to build with gccgo enabled for cross targets since gcc10
Date: Thu, 21 Jan 2021 14:20:11 +0100 [thread overview]
Message-ID: <20210121132011.jt5pNRkDdRov4YKKGqLFVtODuqd2m6ZPmmfbcdk4l_8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28076@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Closed issue by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/28076
Description:
getting output like this: https://build.voidlinux.org/builders/aarch64-musl_builder/builds/31247/steps/shell_3/logs/stdio
```
...
/usr/lib/gcc/aarch64-linux-musl/10.2.1/../../../../aarch64-linux-musl/bin/ld: /usr/aarch64-linux-musl/usr/lib/libgo.so: undefined reference to `getcontext'
/usr/lib/gcc/aarch64-linux-musl/10.2.1/../../../../aarch64-linux-musl/bin/ld: /usr/aarch64-linux-musl/usr/lib/libgo.so: undefined reference to `makecontext'
/usr/lib/gcc/aarch64-linux-musl/10.2.1/../../../../aarch64-linux-musl/bin/ld: /usr/aarch64-linux-musl/usr/lib/libgo.so: undefined reference to `setcontext'
...
```
which indicates that something is wrong with libgo in the crosstoolchain; not exactly sure what's going on here
for now i disabled gccgo for cross+musl, but once we've figured this out we will need to reenable it and revbump gcc
could use some help figuring this out
@pullmoll @Johnnynator
next prev parent reply other threads:[~2021-01-21 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 11:24 [ISSUE] " q66
2021-01-21 11:27 ` q66
2021-01-21 11:30 ` q66
2021-01-21 12:43 ` pullmoll
2021-01-21 13:05 ` pullmoll
2021-01-21 13:15 ` q66
2021-01-21 13:19 ` q66
2021-01-21 13:19 ` pullmoll
2021-01-21 13:20 ` q66 [this message]
2021-01-21 13:20 ` q66
2021-01-21 13:20 ` pullmoll
2021-01-21 13:33 ` q66
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=20210121132011.jt5pNRkDdRov4YKKGqLFVtODuqd2m6ZPmmfbcdk4l_8@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).