Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kai <kai.kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Kai Kang <kai.kang@eng.windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] glibc: fix multilib headers conflict for arm
Date: Tue, 5 Mar 2024 09:23:51 +0800	[thread overview]
Message-ID: <2783e698-9f43-4843-ac77-db41fedd35e3@windriver.com> (raw)
In-Reply-To: <b023614f7765fc003a4aa854440c0b66d200d27b.camel@linuxfoundation.org>

On 3/5/24 01:00, Richard Purdie wrote:
> On Mon, 2024-03-04 at 09:12 +0800, Kai Kang wrote:
>> From: Kai Kang <kai.kang@windriver.com>
>>
>> The header files conflic when multilib enabled for arm:
>>
>>> Error: Transaction test error:
>>>    file /usr/include/finclude/math-vector-fortran.h conflicts between attempted installs of
>>      lib32-libc6-dev-2.39+git0+312e159626-r0.armv7at2hf_neon and libc6-dev-2.39+git0+312e159626-r0.cortexa72
>>
>> Invoke function oe_multilib_header to resolve it.
>>
>> Signed-off-by: Kai Kang <kai.kang@windriver.com>
>> ---
>>   meta/recipes-core/glibc/glibc-package.inc | 2 ++
>>   1 file changed, 2 insertions(+)
> It may fix conflicts but it appears to break the fortran compiler:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2987/steps/14/logs/stdio
>
> I've not specifically bisected it to this but it does seem most likely.

OK. I'll figure it out.

Regards,
kai

>
> Cheers,
>
> Richard


-- 
Kai Kang
Wind River Linux



      reply	other threads:[~2024-03-05  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  1:12 [PATCH] glibc: fix multilib headers conflict for arm kai.kang
2024-03-04 17:00 ` [OE-core] " Richard Purdie
2024-03-05  1:23   ` Kai [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=2783e698-9f43-4843-ac77-db41fedd35e3@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=kai.kang@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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