Hi Mark,
Thanks for the reply!
On Wed, 2022-08-17 at 13:23 +0200, Mark Wielaard wrote:
> Hi Richard,
>
> On Mon, Aug 15, 2022 at 09:29:03PM +0100, Richard Purdie wrote:
> > On Mon, 2022-08-15 at 21:55 +0200, Mark Wielaard wrote:
> > > I might be misinterpreting the issue you are seeing.
> > >
>
ck how to make
> this work.
>
> On Mon, Aug 15, 2022 at 12:13:28PM +0100, Richard Purdie via Gcc wrote:
> > I'm wondering if we'd be able to improve path handling in the -f*-
> > prefix-map compiler options to cover relative paths?
> > [...]
> > In case it
On Mon, 2022-08-15 at 17:15 +, Joseph Myers wrote:
> On Mon, 15 Aug 2022, Richard Purdie via Gcc wrote:
>
> > Currently it works well for absolute paths but if a file uses a
> > relative path or a path with a symlink in, or a non-absolute path, it
> > will miss those c
On Mon, 2022-08-15 at 12:13 +0100, Richard Purdie via Gcc wrote:
> Hi,
>
> I'm wondering if we'd be able to improve path handling in the -f*-
> prefix-map compiler options to cover relative paths?
>
> Currently it works well for absolute paths but if a file uses a
&g
Hi,
I'm wondering if we'd be able to improve path handling in the -f*-
prefix-map compiler options to cover relative paths?
Currently it works well for absolute paths but if a file uses a
relative path or a path with a symlink in, or a non-absolute path, it
will miss those cases. For relative pat
