On Wed, Nov 13, 2013 at 12:27 AM, Mark Hatle wrote:
> On 11/12/13, 8:24 PM, Otavio Salvador wrote:
>>
>> On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle
>> wrote:
>>>
>>> The various gcc related symlinks should be provided as alternatives
>>> instead
>>> of hard coded symlinks. This will permit mul
On 11/12/13, 8:24 PM, Otavio Salvador wrote:
On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle wrote:
The various gcc related symlinks should be provided as alternatives instead
of hard coded symlinks. This will permit multiple toolchains on a system.
Multiple toolchains could come from multilib c
On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle wrote:
> The various gcc related symlinks should be provided as alternatives instead
> of hard coded symlinks. This will permit multiple toolchains on a system.
>
> Multiple toolchains could come from multilib configurations or alternative
> open sourc
The various gcc related symlinks should be provided as alternatives instead
of hard coded symlinks. This will permit multiple toolchains on a system.
Multiple toolchains could come from multilib configurations or alternative
open source or commerical sources.
Note, gccbug was skipped since it do
