[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns
From: |
Samuel Thibault |
Subject: |
Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns |
Date: |
Sat, 4 Mar 2017 15:13:18 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Louis Jenkins, on ven. 03 mars 2017 20:20:20 +0000, wrote:
> However, again, before I delve further I would like to know first if it is
> still active, or can potentially be restarted.
So, assuming that this is about porting Go to the GNU/Hurd system, you
need to be aware that some work has been done by Svante Signell. He
managed to get the thing built, but apparently there are some runtime
issues, just taking a random package for instance:
https://buildd.debian.org/status/fetch.php?pkg=golang-github-eknkc-amber&arch=hurd-i386&ver=0.0~git20161231.0.9be5e8a-1&stamp=1484728210&raw=0
fatal error: unexpected signal during runtime execution
Also, he focused on gccgo for a start, but we need to propagate the work
to google's golang. If you could check with him what is left, what to
do, etc. that'd be great :)
Samuel
- Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns,
Samuel Thibault <=
- RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Louis Jenkins, 2017/03/04
- Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Samuel Thibault, 2017/03/04
- RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Louis Jenkins, 2017/03/04
- Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Samuel Thibault, 2017/03/04
- Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Svante Signell, 2017/03/04
- RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Louis Jenkins, 2017/03/04
- Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns, Svante Signell, 2017/03/04