> On 4 Aug 2019, at 21:42, Eric Botcazou wrote:
>
>> This patch has now been on mainline for some time without any apparent
>> issue, the problem is also present on the open branches, may I backport it?
>
> OK, thanks.
Done for 9.2.
Iain
> This patch has now been on mainline for some time without any apparent
> issue, the problem is also present on the open branches, may I backport it?
OK, thanks.
--
Eric Botcazou
Hi Eric,
> On 30 Jun 2019, at 10:54, Eric Botcazou wrote:
>
>> 2019-06-30 Iain Sandoe
>>
>> * gnatlink.adb (Link_Step): Remove duplicate -static-libgcc switches.
>> Push -shared-libgcc explicitly, when it is the target default (unless
>> overidden by the static flag).
>> When
> 2019-06-30 Iain Sandoe
>
> * gnatlink.adb (Link_Step): Remove duplicate -static-libgcc switches.
> Push -shared-libgcc explicitly, when it is the target default (unless
> overidden by the static flag).
> When the user has put an instance of shared/static-libgcc do not push
>
Hi Eric,
Gnatlink has code that checks for duplicate '-shared-libgcc’ switches (but not
duplicate ‘static-libgcc’) and also pushes ’static-libgcc' onto the link line
for
targets that default to static linking, provided '-shared-libgcc' is not
present.
For targets that should use a shared libgcc
