I see, are you talking about ${MLPREFIX} variable? The target itself
compiles fine, all are 32-bit binaries in userspace. I have this issue only
for SDK.
On Tue, Sep 14, 2021 at 7:21 PM Khem Raj wrote:
>
>
> On 9/14/21 6:13 PM, Arun wrote:
> > The packages that SDK is trying to build are
On 9/14/21 6:13 PM, Arun wrote:
The packages that SDK is trying to build are userspace packages and they
haven't been ported for 64-bit. There are quite a few of them and short
of fixing 64-bit compile issues for all of them, I am trying to see if I
can build SDK without these packages built
The packages that SDK is trying to build are userspace packages and they
haven't been ported for 64-bit. There are quite a few of them and short of
fixing 64-bit compile issues for all of them, I am trying to see if I can build
SDK without these packages built for. 64-bit. The SDK users will
On Tue, Sep 14, 2021 at 3:41 PM Arun wrote:
>
> Bumping this question...
>
> Is there a way for me to disable building of 64-bit packages when building
> SDK with a multilib config? I have no use for 64-bit userspace package
> artifacts.
I think since kernel is 64bit it might be building some
Bumping this question...
Is there a way for me to disable building of 64-bit packages when building SDK
with a multilib config? I have no use for 64-bit userspace package artifacts.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54720):
I have a custom project where I am building for 64-bit kernel and 32-bit
userspace using multilib config
*# for 32bit userspace build*
*require conf/multilib.confMULTILIBS =
"multilib:lib32"DEFAULTTUNE_virtclass-multilib-lib32 = "armv7athf-neon"*
I am successfully able to build the target
