From: Sam James <sam@gentoo.org>
To: Sam James <sam@gentoo.org>
Cc: Matthias Klose <doko@debian.org>,
Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
YunQiang Su <wzssyqa@gmail.com>,
binutils@sourceware.org
Subject: Re: [PATCH] gprofng: 30700 tmpdir/gp-collect-app_F test fails
Date: Fri, 18 Aug 2023 07:49:17 +0100 [thread overview]
Message-ID: <877cpszvxp.fsf@gentoo.org> (raw)
In-Reply-To: <f4c4c9956ccb5bc55fe95f51ee858e3558aa6acbe8d0d0ca0e8716bafbc1fbab@mu.id>
Sam James <sam@gentoo.org> writes:
> Matthias Klose <doko@debian.org> writes:
>
>> On 18.08.23 07:10, Sam James via Binutils wrote:
>>>> Is it legal to create a build directory inside a source tree?
>>>>
>>> No, the source tree should be treated as immutable please. It's ok
>>> to create directories within the build dir, but not the source tree.
>>
>> you are confusing things. In general you have the option to build
>
> I don't think I am. I just took the question to be generally about
> whether you can modify the source tree. If the build tree is within
> that, then it doesn't really count modulo the issue you mention below.
Right, I get your point now -- you were saying that YunQiang Su's use
case should be fine (because it's a build dir within the source tree).
I was just saying that Vladimir can't make his own directories during
the build in the source tree.
prev parent reply other threads:[~2023-08-18 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 20:33 vladimir.mezentsev
2023-08-17 4:22 ` YunQiang Su
2023-08-17 18:44 ` Vladimir Mezentsev
2023-08-18 2:11 ` YunQiang Su
2023-08-18 5:01 ` Vladimir Mezentsev
2023-08-18 5:09 ` YunQiang Su
2023-08-18 5:10 ` Sam James
2023-08-18 6:38 ` Matthias Klose
2023-08-18 6:45 ` Sam James
[not found] ` <f4c4c9956ccb5bc55fe95f51ee858e3558aa6acbe8d0d0ca0e8716bafbc1fbab@mu.id>
2023-08-18 6:49 ` Sam James [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=877cpszvxp.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=binutils@sourceware.org \
--cc=doko@debian.org \
--cc=vladimir.mezentsev@oracle.com \
--cc=wzssyqa@gmail.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).