From: Jon Mason <jdmason@kudzu.us>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Vasyl Vavrychuk <vvavrychuk@gmail.com>,
Ross Burton <ross.burton@arm.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH 2/3] external-arm-toolchain: in libc.so GNU ld script use base_libdir
Date: Mon, 29 Apr 2024 09:54:22 -0400 [thread overview]
Message-ID: <Zi+mjstvIGWi5o4f@kudzu.us> (raw)
In-Reply-To: <20240418155738.GY28791@denix.org>
On Thu, Apr 18, 2024 at 11:57:38AM -0400, Denys Dmytriyenko wrote:
> On Thu, Apr 18, 2024 at 04:54:05PM +0300, Vasyl Vavrychuk wrote:
> > On Wed, Apr 17, 2024 at 11:12 PM Denys Dmytriyenko <denis@denix.org> wrote:
> > >
> > > On Wed, Apr 17, 2024 at 02:30:41PM +0300, Vasyl Vavrychuk wrote:
> > > > - sed -i -e "s# /${EAT_LIBDIR}/${EAT_TARGET_SYS}# ../../${EAT_LIBDIR}#g" -e "s# /usr/${EAT_LIBDIR}/# /usr/lib/#g" -e "s# /usr/${EAT_LIBDIR}/${EAT_TARGET_SYS}# .#g" -e "s# /${EAT_LIBDIR}/ld-linux# ../../${EAT_LIBDIR}/ld-linux#g" ${D}${libdir}/libc.so
> > > > + sed -i -e "s# /${EAT_LIBDIR}/${EAT_TARGET_SYS}# ../../${EAT_LIBDIR}#g" -e "s# /usr/${EAT_LIBDIR}/# /usr/lib/#g" -e "s# /usr/${EAT_LIBDIR}/${EAT_TARGET_SYS}# .#g" -e "s# /${EAT_LIBDIR}/ld-linux# ../../${base_libdir}/ld-linux#g" ${D}${libdir}/libc.so
> > >
> > > Here ^^^ it's not clear why only the last of the sed replacements gets
> > > updated, not all of them?
> >
> > 1. `/${EAT_LIBDIR}/${EAT_TARGET_SYS}` path is not used in libc.so in
> > Arm GNU Toolchain v13.2.Rel1 in targets "arm-none-linux-gnueabihf" and
> > "aarch64-none-linux-gnu". I am not sure in which versions for ARM or
> > Linaro toolchain this path was used in libc.so. Should I replace it
> > blindly?
>
> Yeah, this list has grown with different versions of the toolchain, where
> almost every new version required a slightly different adjustment in the
> past.
>
> And the external toolchain recipe was always trying to be version agnostic
> and work with a wide range of toolchain versions.
>
> But I guess we could simplify the list of supported versions to what is
> currently available for download - I see that 11.x and 12.x are supported
> now.
>
> Can you please check if libc.so is the same in those versions? If so, we
> can potentially drop all other sed mods from here. Thanks.
meta-arm is going to release very, very soon. If this series should
go in, then this needs to get wrapped up ASAP.
Vasyl, can you check about libc.so (per Denys's question/comment
above, and possibly do another version if his suggestion is correct)?
Thanks,
Jon
>
>
> > 2. Rest two expressions replace input string to "/usr/lib" or ".", so
> > they are not affected by usrmerge.
>
> --
> Denys
>
next prev parent reply other threads:[~2024-04-29 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:30 [PATCH 0/3] external-arm-toolchain: fix build when usrmege enabled Vasyl Vavrychuk
2024-04-17 11:30 ` [PATCH 1/3] external-arm-toolchain: wrap base_libdir vs libdir manipulations under usrmerge check Vasyl Vavrychuk
2024-04-17 20:06 ` [meta-arm] " Denys Dmytriyenko
2024-04-17 11:30 ` [PATCH 2/3] external-arm-toolchain: in libc.so GNU ld script use base_libdir Vasyl Vavrychuk
2024-04-17 20:12 ` [meta-arm] " Denys Dmytriyenko
2024-04-18 13:54 ` Vasyl Vavrychuk
2024-04-18 15:57 ` Denys Dmytriyenko
2024-04-29 13:54 ` Jon Mason [this message]
2024-08-30 15:57 ` Romain Naour
2024-05-24 11:19 ` Parthiban
2024-04-17 11:30 ` [PATCH 3/3] external-arm-toolchain: remove ${base_libdir}/libpthread*.so from FILES:${PN} Vasyl Vavrychuk
2024-04-17 20:13 ` [meta-arm] " Denys Dmytriyenko
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=Zi+mjstvIGWi5o4f@kudzu.us \
--to=jdmason@kudzu.us \
--cc=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=ross.burton@arm.com \
--cc=vvavrychuk@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 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.