[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: |
Sun, 16 Jun 2013 12:31:53 +0200 |
User-agent: |
Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.4.1 (i486-pc-linux-gnu) |
Hi!
On Fri, 14 Jun 2013 22:37:03 +0200, Svante Signell <svante.signell@gmail.com>
wrote:
> On Fri, 2013-06-14 at 16:42 +0200, Thomas Schwinge wrote:
> > 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.
> ...
> > 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.
>
> Sorry, I'm not fluent in git. Which command to use to check out your
> branch tschwinge/t/hurd/go? Cannot find it at
> http://git.savannah.gnu.org/cgit/hurd/glibc.git/
That's no surprise, as I've talking about the GCC Git repository,
<http://gcc.gnu.org/wiki/GitMirror>. Clone it, and then create a local
branch based on the one I pushed, so something like:
$ git clone git://gcc.gnu.org/git/gcc.git
$ cd gcc/
$ git checkout -b tschwinge/t/hurd/go origin/tschwinge/t/hurd/go
As I'm still occasionally seeing file corruption as described on
<http://www.gnu.org/software/hurd/open_issues/git-core-2.html> and
<http://www.gnu.org/software/hurd/open_issues/git_duplicated_content.html>,
I suggest you either pass the --quiet flag to any Git command you use, or
clone on a GNU/Linux box and then use rsync or something similar for
copying the repository and working directory to your GNU/Hurd system.
Grüße,
Thomas
pgprumYRga84w.pgp
Description: PGP signature