Subject: Re: bug#19733: disfunctional gcc binary when GCJ or gfortran is installed

From: Ricardo Wurmus <[email-masked]>
Date: Mon, 21 Dec 2015 16:38:51 +0100

Ludovic Courtès <[email-masked]> writes:

> [email-masked] (Ludovic Courtès) skribis:
>
>> Ricardo Wurmus <[email-masked]> 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.  :-)

Wouldn’t this cause a rebuild of a very large number of packages?
Should I push the above (with ‘gcov’ added to the pattern) to a wip
branch?

~~ Ricardo