bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns


From: Louis Jenkins
Subject: RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns
Date: Sat, 4 Mar 2017 22:38:06 +0000

Hello Samuel,

 

Thank you for your prompt reply. I had no idea that the project was updated, but I am glad that this is the case as it should make it easier to potentially get involved.

 

As for Svante Signell, I was googling his name a bit and the most relevant I could find was for svante.signell@gmail.com would that be his appropriate email address, or is there a way to search or communicate through the mailing list to find him? I apologize if it actually is obvious, I’m quite new to this.

 

From: Samuel Thibault
Sent: Saturday, March 4, 2017 9:13 AM
To: Louis Jenkins
Cc: summer-of-code@gnu.org
Subject: Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

 

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

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]