Hello Allan,
Thanks for following up.
> On 02 Apr 2020, at 10:37, Allan Sandfeld Jensen wrote:
> -r is used for relinking. The idea behind the change was to make it directly
> suitable for that.
In my mind, it was just a means to convey "I will relink this somehow
later on, don't complain if
On Wednesday, 1 April 2020 19:48:11 CEST Olivier Hainque wrote:
>
> -r 's business was to arrange for the linker not to
> complain because the closure is incomplete, leaving us
> with complete control of the closure.
>
> It doesn't seem to me there was a really strong motivation
> to suddenly
Hello Iain,
> On 1 Apr 2020, at 22:42, Iain Sandoe wrote:
>
> perhaps I’m missing something here, but it is quite possible for a target
> to override and provide a customised version of LINK_COMMAND_SPEC.
>
> Darwin does this: see config/darwin.h
>
> So, AFAIU, a port owner has the last call
Olivier Hainque wrote:
Hello again,
On 01 Apr 2020, at 19:48, Olivier Hainque wrote:
* gcc.c (LINK_COMMAND_SPEC): Handle -r like -nostdlib.
Would it be possible to revert to the previous behavior
and document it ?
Or maybe allow it to be controllable by the target ports ?
Hello again,
> On 01 Apr 2020, at 19:48, Olivier Hainque wrote:
>
>* gcc.c (LINK_COMMAND_SPEC): Handle -r like -nostdlib.
>
> Would it be possible to revert to the previous behavior
> and document it ?
>
> Or maybe allow it to be controllable by the target ports ?
>
> Or provide
Hello,
While working on the migration of our production
ports to gcc-9, we stumbled on a problem with the
behavioral changed introduced by
commit 0b7fb27b698da38fd13108ecc914613f85f66f9d
Author: Allan Sandfeld Jensen
Date: Fri Sep 21 01:38:24 2018 +0600
Fix and document -r option
