All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: richard.purdie@linuxfoundation.org, ross.burton@arm.com,
	"hongxu.jia@eng.windriver.com" <hongxu.jia@eng.windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/9] multilib_header.bbclass: need multilib headers for nativesdk builds
Date: Fri, 7 Feb 2025 13:21:58 +0800	[thread overview]
Message-ID: <e75c42db-e992-4436-bb46-1bc0b4c295fb@windriver.com> (raw)
In-Reply-To: <b029a8a84294c6cad08dae46a5cfec398bc04a6d.camel@linuxfoundation.org>

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

Sorry for replying late, I am just back from the vacation

On 2/6/25 15:39, Richard Purdie via lists.openembedded.org wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 2025-01-29 at 16:58 +0000, Ross Burton via
> lists.openembedded.org wrote:
>> On 21 Jan 2025, at 08:55, hongxu via lists.openembedded.org
>> <hongxu.jia=eng.windriver.com@lists.openembedded.org>  wrote:
>>> The nativesdk multilib support required it to fix multilib headers
>>> conflict
>> So the context here is that luajit apparently needs to be able to
>> build native code with the same word size as the target.  But this
>> demonstrates nicely that nobody has tried to build a 32-bit luajit on
>> a 64-bit non-x86 machine, for example:
>>
>>> gcc: error: unrecognized command-line option ‘-m32’
>> So if the goal is “build luajit everywhere” then this doesn’t solve
>> that problem.
> I've been giving this a lot of. Part of me does like this solution but
> equally, it is complicating something which is already quite complex
> for a comparatively isolated problem. As Ross mentions, it only fixes
> this for a small subsection there too, it isn't a universal fix.
>
> Some of the patches in the series are simple/trivial but others have
> what looks like quite fragile logic (e.g. the libgcc paths).
>
> I'm not convinced merging this and trying to support multilib
> nativesdk-gcc is in our best interests unfortunately.

Agree with you, follow your suggestion, I will drop libgcc patches to 
supportmultilib nativesdk-gcc

and pick up the simple/trivial patches from the series and resend them 
in v2, including:

  [OE-core] [PATCH 3/9] toolchain-shar-relocate.sh: support multiple 
dynamic loaders for multilib
  [OE-core] [PATCH 4/9] script/relocate_sdk.py: check dynamic loader 
arch before relocating interpreter

//Hongxu

> Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#210907):https://lists.openembedded.org/g/openembedded-core/message/210907
> Mute This Topic:https://lists.openembedded.org/mt/110730419/3617049
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub  [hongxu.jia@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

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

  reply	other threads:[~2025-02-07  5:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  8:55 [PATCH 1/9] perl: fix do_install failed for nativesdk-perl Hongxu Jia
2025-01-21  8:55 ` [PATCH 2/9] multilib_header.bbclass: need multilib headers for nativesdk builds Hongxu Jia
2025-01-27 13:18   ` [OE-core] " Mathieu Dubois-Briand
2025-01-29 16:58   ` Ross Burton
2025-02-06  7:39     ` Richard Purdie
2025-02-07  5:21       ` Hongxu Jia [this message]
2025-01-21  8:55 ` [PATCH 3/9] toolchain-shar-relocate.sh: support multiple dynamic loaders for multilib Hongxu Jia
2025-01-21  8:55 ` [PATCH 4/9] script/relocate_sdk.py: check dynamic loader arch before relocating interpreter Hongxu Jia
2025-01-21  8:55 ` [PATCH 5/9] libgcc-common: apply multilib symlinks for nativesdk libgcc Hongxu Jia
2025-01-21  8:55 ` [PATCH 6/9] meta/conf/bitbake.conf: support multiarch for nativesdk Hongxu Jia
2025-01-21  8:55 ` [PATCH 7/9] gcc-configure-common.inc: add multlib support for i686/i586/x86_64 nativesdk gcc Hongxu Jia
2025-01-22  4:20   ` [OE-core] " Khem Raj
2025-01-23  4:53   ` [PATCH v2 " Hongxu Jia
2025-01-23 15:49     ` [OE-core] " Yoann Congal
2025-01-23 17:17     ` hongxu
2025-01-21  8:55 ` [PATCH 8/9] Add recipe nativesdk-multiconfig-multlib-toolchain-packager Hongxu Jia
2025-01-21  9:05   ` Patchtest results for " patchtest
2025-01-21  9:12   ` [PATCH v2 8/9] nativesdk-multiconfig-multlib-toolchain-packager: add recipe Hongxu Jia
2025-01-21  8:55 ` [PATCH 9/9] selftest/multiconfig: test multiconfig multlib nativesdk gcc Hongxu Jia

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=e75c42db-e992-4436-bb46-1bc0b4c295fb@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=hongxu.jia@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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.