[Top][All Lists]

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

Re: Hurd port for GCC Go

From: Thomas Schwinge
Subject: Re: Hurd port for GCC Go
Date: Fri, 14 Jun 2013 16:42:06 +0200
User-agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.4.1 (i486-pc-linux-gnu)


On Thu, 13 Jun 2013 10:39:58 +0200, I wrote:
> On Wed, 12 Jun 2013 15:36:39 +0200, Svante Signell <svante.signell@gmail.com> 
> wrote:
> > On Tue, 2013-06-11 at 10:31 +0200, Thomas Schwinge wrote:
> > > On Fri, 07 Jun 2013 11:14:31 +0200, Svante Signell 
> > > <svante.signell@gmail.com> wrote:
> > > > Attached are patches to enable gccgo to build properly on Debian
> > > > GNU/Hurd on gcc-4.7 (4.7.3-4).
> > > 
> > > Thanks!  I've begun integrating them into my GCC tree (based on upstream
> > > GCC trunk, so some changes to be done to your patches), and get it in a
> > > state for Fotis to base his GSoC work on.
> > 
> > Where to find your GCC tree?
> Only locally at the moment; will find a place to publish it.  As the .git
> directory weighs in the order of 1 GiB, I don't just want to push that
> onto darnassus (for example); even if we told people to first clone the
> upstream Git repository and only then add darnassus as an additional
> remote, I bet some would forget doing that.  Hmm, it seems that I might
> be able to host Git branches upstream, so I'll explore that:
> <http://gcc.gnu.org/wiki/GitMirror#Git-only_branches>.

I have now pushed my working branch to tschwinge/t/hurd/go, and will
update this from time to time, both for integrating further changes (my
own as well as those that you send me), and merge in GCC trunk changes.
On that branch, use something like »git diff :/refs/top-bases/baseline«
to diff your working tree against the branch's base.  When reviewing the
commit history on that branch, it may be helpful to exclude any bulk
merges from trunk, so use something like »git log HEAD ^origin/trunk«.

Fotis and Svante, please base any futher work for the Hurd port for GCC
Go on that branch.  Send patches by email, for now.

> I got as far as having GCC Go compiling with GCC trunk sources; more to
> come later.

> > Also I had problems to tracing this commit:
> > <http://git.savannah.gnu.org/cgit/hurd/glibc.git/commit/?h=t/context_functions&id=018259d791f1ced4b2ced88c393cc74de15006ed>.
> > I did not find anything related to context_functions at
> > http://git.savannah.gnu.org/cgit/hurd/glibc.git/
> Follow »[...]« in the Branches section to see all branches.  Anyway, it's
> a TopGit branch,
> <http://www.gnu.org/software/hurd/source_repositories/glibc.html>, so for
> getting a patch out of that, you'll need to diff the top of that branch
> against its base branch, using »tg patch t/context_functions« if you have
> TopGit installed, or something like »git diff
> top-bases/t/context_functions t/context_functions« manually.
> > Furthermore, for testing purposes, is it straight-forward to add the new
> > functions getcontext/setcontext/makecontext*/movecontext to the debian
> > sources, e.g. 2.13-39+hurd.3 or 2.17-6 (when that is released?).
> It is, and Samuel is already building 2.17-3+hurd.4 packages, so you
> might just wait for these to appear on debian-ports.

These packages are available now.  Thanks Samuel!


Attachment: pgpzEE2UTrCAH.pgp
Description: PGP signature

reply via email to

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