From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: J?rg Vehlow <lkml@jv-coder.de>, Khem Raj <raj.khem@gmail.com>,
Jose Quaresma <quaresma.jose@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Joerg Vehlow <joerg.vehlow@aox.de>
Subject: Re: [OE-core] [PATCH] go: Always pass interpreter to linker
Date: Fri, 29 Apr 2022 13:45:23 +0100 [thread overview]
Message-ID: <58c8fae2950790db746d5059a7f0ecd9993fed81.camel@linuxfoundation.org> (raw)
In-Reply-To: <c01611bd-8a0b-b91c-ff8a-bae9b877d1ee@jv-coder.de>
On Thu, 2022-04-14 at 07:24 +0200, J?rg Vehlow wrote:
> Hi,
>
> Am 4/11/2022 um 6:04 PM schrieb Khem Raj:
> > On Mon, Apr 11, 2022 at 6:30 AM Jose Quaresma <quaresma.jose@gmail.com> wrote:
> > >
> > >
> > >
> > > J?rg Vehlow <lkml@jv-coder.de> escreveu no dia segunda, 11/04/2022 à(s) 13:35:
> > > >
> > > > From: Joerg Vehlow <joerg.vehlow@aox.de>
> > > >
> > > > When gos internal linker is used, it uses hardcoded paths to the
> > > > interpreter (dynamic linker). For x86_64 this hardcoded path is
> > > > /lib64/ld-linux-x86-64.so.2, but yocto's default dynamic linker path
> > > > is /lib64/ld-linux-x86-64.so.2.
> > >
> > >
> > > Is this correct? The first path is the seme one of the second.
> >
> > its a typo, Sadly we do differ in baselib naming convention on x86_64
> > ( without multilib )
> > compared to other distributions which are inherently multilib and use
> > /lib64 OE instead uses
> > /lib when multilib is not enabled but lib64/ when multilib is enabled.
>
> Any comment on the content of the patch or do I have to send a v2 with a
> fixed commit message?
It merged:
https://git.yoctoproject.org/poky/commit/?id=460012e04a89e0b84fd5949c9a2229ef46e7a341
Cheers,
Richard
prev parent reply other threads:[~2022-04-29 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 12:35 [PATCH] go: Always pass interpreter to linker Joerg Vehlow
2022-04-11 13:30 ` [OE-core] " Jose Quaresma
2022-04-11 13:32 ` Joerg Vehlow
2022-04-11 16:04 ` Khem Raj
2022-04-14 5:24 ` Joerg Vehlow
2022-04-29 12:45 ` Richard Purdie [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=58c8fae2950790db746d5059a7f0ecd9993fed81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joerg.vehlow@aox.de \
--cc=lkml@jv-coder.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=quaresma.jose@gmail.com \
--cc=raj.khem@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