Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: gcc: update to 9.2.0 and enable gcc-go on musl + go and objc/objc++ on cross targets
Date: Sun, 08 Sep 2019 22:12:55 +0200	[thread overview]
Message-ID: <20190908201255.MVkWiX3IdBBVFK8s1VN6cUqnkM71FlDOs_LVZzvHqHQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14289@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

There's a closed pull request on the void-packages repository

gcc: update to 9.2.0 and enable gcc-go on musl + go and objc/objc++ on cross targets
https://github.com/void-linux/void-packages/pull/14289

Description:
This updates `gcc` to 9.2.0 and while doing that, enables `gcc-go` on `musl`. It also enables `go`, `objc` and `objc++` support in crosstoolchains, allowing us to also enable them for cross targets. That mainly means our cross targets and native targets will all have `gcc` built with the same languages and subpackages, which should be a lot easier to deal with (and possibly enable crosscompiling for some GNUstep stuff etc)

(except on `mips*-musl`, as `libucontext` does not have MIPS support yet, so only enable `objc` and `objc++` on those)

Crosstoolchains updates:

- [x] aarch64
- [x] aarch64-musl
- [x] armv5tel
- [x] armv5tel-musl
- [x] armv6l
- [x] armv6l-musl
- [x] armv7l
- [x] armv7l-musl
- [x] i686
- [x] i686-musl
- [x] mips-musl
- [x] mipshf-musl
- [x] mipsel-musl
- [x] mipselhf-musl
- [x] ppc64le
- [x] ppc64le-musl
- [x] ppc64
- [x] ppc64-musl
- [x] ppc
- [x] ppc-musl
- [x] x86_64-musl

Testing:

- [x] ppc64le
- [x] ppc64le-musl
- [x] ppc64
- [x] ppc64-musl
- [x] ppc
- [x] ppc-musl
- [ ] x86_64
- [ ] x86_64-musl
- [x] aarch64 (build)
- [x] aarch64-musl (build)
- [ ] armv7l (build)

      parent reply	other threads:[~2019-09-08 20:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-07 17:35 [PR PATCH] [WIP] gcc: update to 9.2.0 and enable gcc-go on musl voidlinux-github
2019-09-07 18:18 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-07 18:18 ` voidlinux-github
2019-09-07 18:19 ` voidlinux-github
2019-09-07 18:19 ` voidlinux-github
2019-09-07 18:59 ` voidlinux-github
2019-09-07 19:01 ` voidlinux-github
2019-09-07 23:45 ` voidlinux-github
2019-09-07 23:48 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-07 23:48 ` voidlinux-github
2019-09-07 23:52 ` voidlinux-github
2019-09-07 23:52 ` voidlinux-github
2019-09-08  1:20 ` [PR PATCH] [Updated] gcc: update to 9.2.0 and enable gcc-go on musl + go and objc/objc++ on cross targets voidlinux-github
2019-09-08  1:20 ` voidlinux-github
2019-09-08  1:56 ` voidlinux-github
2019-09-08  1:56 ` voidlinux-github
2019-09-08  2:27 ` voidlinux-github
2019-09-08 10:31 ` voidlinux-github
2019-09-08 15:30 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-08 15:30 ` voidlinux-github
2019-09-08 19:02 ` voidlinux-github
2019-09-08 19:03 ` voidlinux-github
2019-09-08 20:12 ` voidlinux-github [this message]

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=20190908201255.MVkWiX3IdBBVFK8s1VN6cUqnkM71FlDOs_LVZzvHqHQ@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).