From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 19733@debbugs.gnu.org
Subject: bug#19733: disfunctional gcc binary when GCJ or gfortran is installed
Date: Sat, 19 Dec 2015 18:52:10 +0100 [thread overview]
Message-ID: <87si2yxr5h.fsf@gnu.org> (raw)
In-Reply-To: <87wpuqonl3.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 13 Oct 2015 16:22:16 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
>> Commit 5f6887e8 fixes this for GCJ, but we still have this problem for
>> all variants of gfortran, gcc-objc, and gccgo, all of which are built
>> using the ‘custom-gcc’ procedure.
>>
>> It’s probably safe to add a build phase like this to ‘custom-gcc’:
>>
>> (add-after 'install 'remove-broken-or-conflicting-files
>> (lambda* (#:key outputs #:allow-other-keys)
>> (for-each delete-file
>> (find-files (string-append (assoc-ref outputs "out") "/bin")
>> ".*(c\\+\\+|cpp|g\\+\\+|gcc.*)"))
>> #t))
>
> Sounds like it should work. The pattern should also include ‘gcov’.
Could you give it a try?
Ludo’, trying to tidy up the bug database. :-)
next prev parent reply other threads:[~2015-12-19 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 16:30 bug#19733: disfunctional gcc binary when GCJ or gfortran is installed Ricardo Wurmus
2015-10-13 9:44 ` Ricardo Wurmus
2015-10-13 14:22 ` Ludovic Courtès
2015-12-19 17:52 ` Ludovic Courtès [this message]
2015-12-21 15:38 ` Ricardo Wurmus
2015-12-21 21:30 ` Ludovic Courtès
2016-03-10 6:29 ` Ricardo Wurmus
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=87si2yxr5h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19733@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).