All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Varatharajan, Deepesh" <deepesh.varatharajan@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [walnascar 3/3] bitbake.conf: Switch prefix mapping to use -ffile-prefix-map
Date: Wed, 03 Sep 2025 04:49:40 -0700	[thread overview]
Message-ID: <4495.1756900180442086216@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sqtEcW-wzC3uP7mmiTqAJCVCqzg_Fy5H3anpVUnkg-QDw@mail.gmail.com>

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

Hi Khem,

We backported this patch due to a specific use case on our end. We set the TMPDIR
path length to 399 characters (just under the 400-character limit) and attempted
to build lib32-gcc. While this works fine on the master branch, we encountered the
following error on the walnascar branch:

make: /bin/bash: Argument list too long
make: *** [Makefile:4701: all-gcc] Error 127
ERROR: oe_runmake failed

Upon comparing the logs between the master and walnascar branches, we noticed that
in walnascar, the following flags were passed multiple times:

-fmacro-prefix-map
-fdebug-prefix-map
-fcanon-prefix-map

Since our TMPDIR path is quite long, passing it repeatedly via these flags seems
to be the root cause of the issue.

In the master branch, these were replaced with the more concise "-ffile-prefix-map"
flag, significantly reducing the number of times the long TMPDIR path is passed to
the compiler. This change resolved the error, which is why we backported the patch
to walnascar.

So, can we backport this for walnascar branch in future or do you suggest us to wait for
october release.

Regards,
Deepesh

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

  reply	other threads:[~2025-09-03 11:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 13:29 [OE-core][walnascar 0/3] Patch review Steve Sakoman
2025-08-12 13:29 ` [OE-core][walnascar 1/3] dropbear: patch CVE-2025-47203 Steve Sakoman
2025-08-12 13:29 ` [OE-core][walnascar 2/3] glibc: Forward -ffile-prefix-map option to assembler flags Steve Sakoman
2025-08-12 13:29 ` [OE-core][walnascar 3/3] bitbake.conf: Switch prefix mapping to use -ffile-prefix-map Steve Sakoman
2025-08-13 16:11   ` Gyorgy Sarvari
2025-08-13 16:13     ` Steve Sakoman
2025-08-13 21:21       ` Khem Raj
2025-09-03 11:49         ` Varatharajan, Deepesh [this message]
2025-09-08 15:55           ` [OE-core] [walnascar " Khem Raj
     [not found]     ` <185B5FA5D8F47DA2.29447@lists.openembedded.org>
2025-08-15 16:03       ` [OE-core][walnascar " Steve Sakoman
2025-08-15 18:42         ` Khem Raj

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=4495.1756900180442086216@lists.openembedded.org \
    --to=deepesh.varatharajan@windriver.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.