On 12/20/2019 05:27 AM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Dec 19, 2019 at 03:47:13PM -0600, Neal Gompa wrote:
>> == Release Notes ==
>> The user /usr/bin/cc and /usr/bin/c++ symlinks are now managed by
>> update-alternatives. If you would like to change these symlinks to
>> point to another compiler, like clang, for example, you can use these
>> commands:
>>
>> `update-alternatives --set cc /usr/bin/clang`
>>
>> `update-alternatives --set c++ /usr/bin/clang++`
>>
>
> I don't know if I want *more* alternatives usage in Fedora. I like the
> fact that a basic buildroot is generally supposed to work without
> scriptlets... On the other hand, I think we're already using
> alternatives for ld...
>
> Aside from making it possible to swap the system compiler with
> alternatives, what benefit do we get? Are there other, less script-y
> approaches that we could use?
I'm not sure that the benefits are really that big. For most cases, instead
of setting alternatives, the obvious solution would be to set $CC. Can you
expand a bit on why alternatives, which is effectively a global setting,
is preferred to a local override?
This is a good point, and something I don't have numbers for yet. As
mentioned in my other response, I've only done rebuilds with CC=/usr/bin/cc
*and* the alternatives changes together. These changes together get around
~70% of the packages building with clang.
-Tom
Zbyszek
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org