Re: cygport may not create debug info if top directory contains a symlink

[Jon Turney <jon.turney@dronecode.org.uk>]

On 18/09/2023 18:24, Brian Inglis via Cygwin-apps wrote:
> On 2023-09-18 04:41, Christian Franke via Cygwin-apps wrote:
>> Brian Inglis wrote:
>>> On 2023-09-17 08:01, Jon Turney via Cygwin-apps wrote:
>>>> On 16/09/2023 15:17, Christian Franke via Cygwin wrote:
>>>>> Found during tests of busybox package:
>>>>> If the path of the top build directory contains a symlink and the 
>>>>> project's build scripts normalize pathnames, no debug info is 
>>>>> created by cygport.
>>>>>
>>>>> This is because options like
>>>>>   -fdebug-prefix-map=${B}=/usr/src/debug/${PF}
>>>>> have no effect because ${B} contains a symlink but the compiler is 
>>>>> run with the real source path.
>>>>
[...]
> 
>>>> Sidenote: we should probably also be using file-prefix-map, now 
>>>> we're on a gcc which supports it.
> 
> ... also macro-prefix-map, although it looks like changing to 
> -ffile-prefix-map is equivalent to -f*-prefix-map which future proofs 
> the options!

So I updated to using -ffile-prefix-map in cygport 0.36.8, since that 
seems like the "Right Thing(TM)"

I discovered today that, amazingly, this breaks compiling ruby, since in 
one place it does:

#include __FILE__

(yeah, that's pretty jaw dropping...)