From: csanchezdll@gmail.com (Carlos Sánchez de La Lama)
To: Marius Bakke <mbakke@fastmail.com>, Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: gcc-4.9: Update to 4.9.4.
Date: Tue, 25 Oct 2016 09:03:11 +0200 [thread overview]
Message-ID: <7tzilsykpc.fsf@gmail.com> (raw)
In-Reply-To: <87funl1y3w.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Mon, 24 Oct 2016 18:00:03 +0100")
Hi Marius, Mark,
> Only packages with a large impact in terms of rebuilds (as calculated by
> `guix refresh -l <package-name>`). Obviously gcc is one such package.
> http://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html
Thanks! That is exactly the information I was looking for.
> Most changes go to 'master' first and are later merged into
> 'core-updates'. However, changes that would force a large number of
> rebuilds need to be pushed to another branch, to allow our build farm to
> rebuild before its merged to 'master'.
Understood, makes a lot of sense.
> If you are porting to a new architecture, I would definitely recommend
> basing your work on 'core-updates', which will likely be merged into
> 'master' in the next two weeks. If you need gcc-4.9.4, that's another
> reason to base your work on 'core-updates'.
I am (I think) almost there, I expect to be able to succesfully build
hello on my ppc machine soon (it's a slow machine, so iterations take
time). I do not feel like changing to core-updates now (though I would
have been better had I worked there since the beggining). Once I have
bootstrapped, I will review the changes and rebase the "core" ones to
core-updates. I should be there before two weeks' time.
Thanks!
Carlos
next prev parent reply other threads:[~2016-10-25 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 7:51 [PATCH] gnu: gcc-4.9: Update to 4.9.4 Carlos Sánchez de La Lama
2016-10-24 13:16 ` Leo Famulari
2016-10-24 14:35 ` Carlos Sánchez de La Lama
2016-10-24 17:00 ` Marius Bakke
2016-10-25 7:03 ` Carlos Sánchez de La Lama [this message]
2016-10-24 20:07 ` Mark H Weaver
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=7tzilsykpc.fsf@gmail.com \
--to=csanchezdll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.