All of lore.kernel.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] go.bbclass: change GOTMPDIR to improve reproducibility
Date: Tue, 9 Dec 2025 17:49:16 +0800	[thread overview]
Message-ID: <d49e5d5c-eafb-441c-946e-e361d23f3aab@windriver.com> (raw)
In-Reply-To: <CANNYZj_dF96XaooeJP90LMDCk5XMuw3swcyZtEBW46sS+3mfUQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]


On 12/8/25 18:39, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Mon, 8 Dec 2025 at 10:18, Changqing Li via lists.openembedded.org
> <changqing.li=windriver.com@lists.openembedded.org> wrote:
>> In the following patch, you said "Additionally, the top level build directory cannot be named 'go-something'." 
>> https://git.openembedded.org/openembedded-core/commit/?id=9985b17a30bb9b9f1bc82a44662687db5cead66e 
>> Can you help to explain why it cannot be named 'go-something'? "go-build-tmp" works well in my env.  if it cannot be named
>>
>> as "go-something",  how about "gobuild-tmp"?
> This was 4 years ago and honestly I don't remember anything about the
> patch, other than it was a pain to find the particular settings that
> work. You can probably set up a yocto build from the revision just
> before the patch and apply parts of it to see why 'go-something'
> didn't work at that point.
>
> We should be careful with further tweaks.

Understand,  thanks.  I tried with kirkstone branch,  and set GOTMPDIR 
to go-tmp,  then bitbake buildah,  build successfully.

But maybe I should set it to "tmp-go-build"  to avoid possible regression.

//Changqing

>
> Alex

[-- Attachment #2: Type: text/html, Size: 2460 bytes --]

  reply	other threads:[~2025-12-09  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <187F32821D48D4AA.919836@lists.openembedded.org>
2025-12-08  9:18 ` [OE-core] [PATCH 1/2] go.bbclass: change GOTMPDIR to improve reproducibility Changqing Li
2025-12-08 10:39   ` Alexander Kanavin
2025-12-09  9:49     ` Changqing Li [this message]
2025-12-08  9:11 changqing.li
2025-12-08 10:41 ` [OE-core] " Alexander Kanavin
2025-12-09  2:37   ` Changqing Li
2025-12-09  9:39     ` Alexander Kanavin
2025-12-09 10:12       ` Changqing Li
2025-12-09 10:19         ` Alexander Kanavin
2025-12-15 18:06         ` Alexander Kanavin

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=d49e5d5c-eafb-441c-946e-e361d23f3aab@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.