Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "AshishKumar Mishra" <ashishkumar.mishra@bmwtechworks.in>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC_V2] [meta-oe]: Improving ext* sparse image generation: migrating from img2simg to ext2simg_android for ext* filesystem
Date: Sun, 01 Mar 2026 20:45:43 -0800	[thread overview]
Message-ID: <1127752.1772426743792609011@lists.openembedded.org> (raw)
In-Reply-To: <1030996.1771825388005282969@lists.openembedded.org>

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

Hi Gyorgy Sarvari ,

w.r.t "What happens if you add "-Wl,-rpath=../${baselib} -Wl,-rpath=../../${baselib}" (or similar) to LDFLAGS?"

Added below in meta-oe/recipes-devtools/e2fsprogs-ext4sparse/e2fsprogs-ext4sparse_1.0.bb as suggested
BUILD_LDFLAGS += "-Wl,-rpath,../${baselib} -Wl,-rpath,../../${baselib}"
TARGET_LDFLAGS += "-Wl,-rpath,../${baselib} -Wl,-rpath,../../${baselib}"

Can i push the patch now in master for this functionality?
or Is there any other process / feedback that i need to work?

Based on additional feedback, can work on the current implementation and share the patches again

Thanks,
Ashish Kumar Mishra

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

  reply	other threads:[~2026-03-02  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  8:06 [RFC_V2] [meta-oe]: Improving ext* sparse image generation: migrating from img2simg to ext2simg_android for ext* filesystem AshishKumar Mishra
2026-02-22 22:03 ` [oe] " Gyorgy Sarvari
2026-02-23  5:43   ` AshishKumar Mishra
2026-03-02  4:45     ` AshishKumar Mishra [this message]
2026-03-03  6:20       ` [oe] " Gyorgy Sarvari
2026-03-03  6:24         ` AshishKumar Mishra
2026-07-21 16:29         ` AshishKumar Mishra

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=1127752.1772426743792609011@lists.openembedded.org \
    --to=ashishkumar.mishra@bmwtechworks.in \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox