From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH v2 2/2] ld: write full paths to dependency-file
Date: Mon, 18 Sep 2023 21:35:37 +0200 [thread overview]
Message-ID: <e615c08d-f734-4303-9df8-27de2d2cc5d3@t-8ch.de> (raw)
In-Reply-To: <9d844234-3e05-42f3-8bfe-3ddf814c8bd8@suse.com>
On 2023-09-18 15:38:21+0200, Jan Beulich wrote:
> On 16.09.2023 12:36, Thomas Weißschuh wrote:
> > When relative paths are written to the dependency-file it forces the
> > users of it to run from the same directory.
> > To avoid this only write absolute paths.
>
> Using relative paths, otoh, may allow to move build trees around. First and
> foremost the two behaviors may relevant when (not) building in the source
> tree itself. Furthermore the compiler, gcc at least, looks to also write
> relative paths when relative paths were given.
Fair enough. Let's drop this patch then.
Thomas
prev parent reply other threads:[~2023-09-18 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 10:36 [PATCH v2 0/2] Improve handling of included linker scripts in dependency-file Thomas Weißschuh
2023-09-16 10:36 ` [PATCH v2 1/2] ld: write resolved path to included file to dependency-file Thomas Weißschuh
2023-09-18 13:28 ` Jan Beulich
2023-09-16 10:36 ` [PATCH v2 2/2] ld: write full paths " Thomas Weißschuh
2023-09-18 13:38 ` Jan Beulich
2023-09-18 19:35 ` Thomas Weißschuh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e615c08d-f734-4303-9df8-27de2d2cc5d3@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).