From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28284-done@debbugs.gnu.org
Subject: bug#28284: GCC 4.7.4 fails to build since April 2017
Date: Tue, 07 Nov 2017 22:07:53 +0100 [thread overview]
Message-ID: <874lq5lrva.fsf@gnu.org> (raw)
In-Reply-To: <87mv3xztyy.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 07 Nov 2017 21:58:45 +0100")
Ludovic Courtès writes:
>> I was working on the $ORIGIN stuff inside (a copy of) the gcc-4.7.4
>> builder -- that code is of course (re)used by all other gcc packages.
>
> Though the $ORIGIN stuff is separate, right? Will be nice to have.
Sure, i figure this will take some time to get in if at all. We'll have
to see what the pros and cons are. Different story/thread.
>> From 22d5353991784409e3a8e671611c5ccff3ff7b68 Mon Sep 17 00:00:00 2001
>> From: Jan Nieuwenhuizen <janneke@gnu.org>
>> Date: Mon, 6 Nov 2017 22:50:05 +0100
>> Subject: [PATCH] gnu: gcc-4.7: Resurrect building with gcc-5.4.0.
>>
>> * gnu/packages/patches/gcc-4-compile-with-gcc-5.patch: New file.
>> * gnu/local.mk (dist_patch_DATA): Add it.
>> * gnu/packages/gcc.scm (gcc-4.7): Use it.
>
> Go for it!
Pushed to master as 625492ee1a5a8e515b97d4b76734584c1b420243
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2017-11-07 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 21:26 bug#28284: GCC 4.7.4 fails to build since April 2017 Mark H Weaver
2017-11-06 21:58 ` Jan Nieuwenhuizen
2017-11-07 10:25 ` Ludovic Courtès
2017-11-07 17:29 ` Jan Nieuwenhuizen
2017-11-07 20:58 ` Ludovic Courtès
2017-11-07 21:07 ` Jan Nieuwenhuizen [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lq5lrva.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=28284-done@debbugs.gnu.org \
--cc=ludo@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).