* Forcing uninative?
@ 2023-09-20 20:59 Rudolf J Streif
2023-09-20 21:16 ` [yocto] " Alexandre Belloni
0 siblings, 1 reply; 6+ messages in thread
From: Rudolf J Streif @ 2023-09-20 20:59 UTC (permalink / raw)
To: Yocto-mailing-list
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
I need to resurrect a Yocto Project build environment based on honister.
My dev system has since moved on to a newer glibc etc. As expected, I am
getting this warning
WARNING: Your host glibc version (2.37) is newer than that in uninative
(2.34). Disabling uninative so that sstate is not corrupted.
The distro's gcc now is 13.2.1.
Now the following packages do not compile anymore:
* rust-llvm-native : which there is a patch (applied to kirkstone):
https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
* libdnf-native : because std::uint32_t does not exist anymore
I don't care about the sstate as I am creating a new one. However, how
can I force uninative to be used and would it even solve the problem (I
would think so as the idea of uninative is to isolate the build from the
host libraries)?
Thanks,
Rudi
[-- Attachment #2: Type: text/html, Size: 1355 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [yocto] Forcing uninative?
2023-09-20 20:59 Forcing uninative? Rudolf J Streif
@ 2023-09-20 21:16 ` Alexandre Belloni
2023-09-20 21:39 ` Rudolf J Streif
2023-09-21 1:32 ` Khem Raj
0 siblings, 2 replies; 6+ messages in thread
From: Alexandre Belloni @ 2023-09-20 21:16 UTC (permalink / raw)
To: Rudolf J Streif; +Cc: Yocto-mailing-list
Hello,
On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote:
> I need to resurrect a Yocto Project build environment based on honister. My
> dev system has since moved on to a newer glibc etc. As expected, I am
> getting this warning
>
> WARNING: Your host glibc version (2.37) is newer than that in uninative
> (2.34). Disabling uninative so that sstate is not corrupted.
>
> The distro's gcc now is 13.2.1.
>
> Now the following packages do not compile anymore:
>
> * rust-llvm-native : which there is a patch (applied to kirkstone):
> https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
> * libdnf-native : because std::uint32_t does not exist anymore
>
> I don't care about the sstate as I am creating a new one. However, how can I
> force uninative to be used and would it even solve the problem (I would
> think so as the idea of uninative is to isolate the build from the host
> libraries)?
>
You should rather use buildtools. You can install those with
scripts/install-buildtools. The -r option is there to allow you to
select a target release. You can try something like:
poky/scripts/install-buildtools -d ~/YP/buildtools -r yocto-3.4.4 --installer-version 3.4.4
This will then tell you to source buildtools/environment-setup-x86_64-pokysdk-linux
This should be enough to be able to build old releases.
Regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [yocto] Forcing uninative?
2023-09-20 21:16 ` [yocto] " Alexandre Belloni
@ 2023-09-20 21:39 ` Rudolf J Streif
2023-09-20 22:42 ` Richard Purdie
2023-09-21 1:32 ` Khem Raj
1 sibling, 1 reply; 6+ messages in thread
From: Rudolf J Streif @ 2023-09-20 21:39 UTC (permalink / raw)
To: Alexandre Belloni; +Cc: Yocto-mailing-list
Thank you, Alexandre.
On 9/20/23 14:16, Alexandre Belloni wrote:
> Hello,
>
> On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote:
>> I need to resurrect a Yocto Project build environment based on honister. My
>> dev system has since moved on to a newer glibc etc. As expected, I am
>> getting this warning
>>
>> WARNING: Your host glibc version (2.37) is newer than that in uninative
>> (2.34). Disabling uninative so that sstate is not corrupted.
>>
>> The distro's gcc now is 13.2.1.
>>
>> Now the following packages do not compile anymore:
>>
>> * rust-llvm-native : which there is a patch (applied to kirkstone):
>> https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
>> * libdnf-native : because std::uint32_t does not exist anymore
>>
>> I don't care about the sstate as I am creating a new one. However, how can I
>> force uninative to be used and would it even solve the problem (I would
>> think so as the idea of uninative is to isolate the build from the host
>> libraries)?
>>
> You should rather use buildtools. You can install those with
> scripts/install-buildtools. The -r option is there to allow you to
> select a target release. You can try something like:
>
> poky/scripts/install-buildtools -d ~/YP/buildtools -r yocto-3.4.4 --installer-version 3.4.4
>
> This will then tell you to source buildtools/environment-setup-x86_64-pokysdk-linux
OK, I did that. The environment only adds the paths. Then I sourced the
build environment as usual. Unfortunately, it still fails with the same
error messages.
>
> This should be enough to be able to build old releases.
>
> Regards,
>
--
Rudolf J Streif
CEO/CTO
1.855.442.3386
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [yocto] Forcing uninative?
2023-09-20 21:39 ` Rudolf J Streif
@ 2023-09-20 22:42 ` Richard Purdie
0 siblings, 0 replies; 6+ messages in thread
From: Richard Purdie @ 2023-09-20 22:42 UTC (permalink / raw)
To: Rudolf J Streif, Alexandre Belloni; +Cc: Yocto-mailing-list
On Wed, 2023-09-20 at 14:39 -0700, Rudolf J Streif wrote:
> Thank you, Alexandre.
>
> On 9/20/23 14:16, Alexandre Belloni wrote:
> > Hello,
> >
> > On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote:
> > > I need to resurrect a Yocto Project build environment based on honister. My
> > > dev system has since moved on to a newer glibc etc. As expected, I am
> > > getting this warning
> > >
> > > WARNING: Your host glibc version (2.37) is newer than that in uninative
> > > (2.34). Disabling uninative so that sstate is not corrupted.
> > >
> > > The distro's gcc now is 13.2.1.
> > >
> > > Now the following packages do not compile anymore:
> > >
> > > * rust-llvm-native : which there is a patch (applied to kirkstone):
> > > https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
> > > * libdnf-native : because std::uint32_t does not exist anymore
> > >
> > > I don't care about the sstate as I am creating a new one. However, how can I
> > > force uninative to be used and would it even solve the problem (I would
> > > think so as the idea of uninative is to isolate the build from the host
> > > libraries)?
> > >
> > You should rather use buildtools. You can install those with
> > scripts/install-buildtools. The -r option is there to allow you to
> > select a target release. You can try something like:
> >
> > poky/scripts/install-buildtools -d ~/YP/buildtools -r yocto-3.4.4 --installer-version 3.4.4
> >
> > This will then tell you to source buildtools/environment-setup-x86_64-pokysdk-linux
> OK, I did that. The environment only adds the paths. Then I sourced the
> build environment as usual. Unfortunately, it still fails with the same
> error messages.
>
By using an older buildtools-extended tarball you should be able to
gain an older host compiler version which will avoid the compile
failures you mention. I suspect uninative will need to be disabled but
that shouldn't matter for your use case as you're not sharing the
sstate.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [yocto] Forcing uninative?
2023-09-20 21:16 ` [yocto] " Alexandre Belloni
2023-09-20 21:39 ` Rudolf J Streif
@ 2023-09-21 1:32 ` Khem Raj
2023-09-21 1:53 ` Rudolf J Streif
1 sibling, 1 reply; 6+ messages in thread
From: Khem Raj @ 2023-09-21 1:32 UTC (permalink / raw)
To: alexandre.belloni; +Cc: Rudolf J Streif, Yocto-mailing-list
On Wed, Sep 20, 2023 at 2:16 PM Alexandre Belloni via
lists.yoctoproject.org
<alexandre.belloni=bootlin.com@lists.yoctoproject.org> wrote:
>
> Hello,
>
> On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote:
> > I need to resurrect a Yocto Project build environment based on honister. My
> > dev system has since moved on to a newer glibc etc. As expected, I am
> > getting this warning
> >
> > WARNING: Your host glibc version (2.37) is newer than that in uninative
> > (2.34). Disabling uninative so that sstate is not corrupted.
> >
> > The distro's gcc now is 13.2.1.
> >
> > Now the following packages do not compile anymore:
> >
> > * rust-llvm-native : which there is a patch (applied to kirkstone):
> > https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
> > * libdnf-native : because std::uint32_t does not exist anymore
> >
> > I don't care about the sstate as I am creating a new one. However, how can I
> > force uninative to be used and would it even solve the problem (I would
> > think so as the idea of uninative is to isolate the build from the host
> > libraries)?
> >
>
> You should rather use buildtools. You can install those with
> scripts/install-buildtools. The -r option is there to allow you to
> select a target release. You can try something like:
>
> poky/scripts/install-buildtools -d ~/YP/buildtools -r yocto-3.4.4 --installer-version 3.4.4
>
> This will then tell you to source buildtools/environment-setup-x86_64-pokysdk-linux
>
> This should be enough to be able to build old releases.
real issue would be getting native packages compiling with newer
compilers, unless you are ready to do such backports this
is going to be a problem. I would suggest using a supported/tested
distro for honister release inside a VM or container to build it.
>
> Regards,
>
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#61058): https://lists.yoctoproject.org/g/yocto/message/61058
> Mute This Topic: https://lists.yoctoproject.org/mt/101487564/1997914
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [yocto] Forcing uninative?
2023-09-21 1:32 ` Khem Raj
@ 2023-09-21 1:53 ` Rudolf J Streif
0 siblings, 0 replies; 6+ messages in thread
From: Rudolf J Streif @ 2023-09-21 1:53 UTC (permalink / raw)
To: Khem Raj, alexandre.belloni; +Cc: Yocto-mailing-list
On 9/20/23 18:32, Khem Raj wrote:
> On Wed, Sep 20, 2023 at 2:16 PM Alexandre Belloni via
> lists.yoctoproject.org
> <alexandre.belloni=bootlin.com@lists.yoctoproject.org> wrote:
>> Hello,
>>
>> On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote:
>>> I need to resurrect a Yocto Project build environment based on honister. My
>>> dev system has since moved on to a newer glibc etc. As expected, I am
>>> getting this warning
>>>
>>> WARNING: Your host glibc version (2.37) is newer than that in uninative
>>> (2.34). Disabling uninative so that sstate is not corrupted.
>>>
>>> The distro's gcc now is 13.2.1.
>>>
>>> Now the following packages do not compile anymore:
>>>
>>> * rust-llvm-native : which there is a patch (applied to kirkstone):
>>> https://lore.kernel.org/openembedded-core/CANPvuR=G1NxfJb67xD19FoNh4eTDsTM4TDyF+vDbh6crNH=dgw@mail.gmail.com/T/
>>> * libdnf-native : because std::uint32_t does not exist anymore
>>>
>>> I don't care about the sstate as I am creating a new one. However, how can I
>>> force uninative to be used and would it even solve the problem (I would
>>> think so as the idea of uninative is to isolate the build from the host
>>> libraries)?
>>>
>> You should rather use buildtools. You can install those with
>> scripts/install-buildtools. The -r option is there to allow you to
>> select a target release. You can try something like:
>>
>> poky/scripts/install-buildtools -d ~/YP/buildtools -r yocto-3.4.4 --installer-version 3.4.4
>>
>> This will then tell you to source buildtools/environment-setup-x86_64-pokysdk-linux
>>
>> This should be enough to be able to build old releases.
> real issue would be getting native packages compiling with newer
> compilers, unless you are ready to do such backports this
> is going to be a problem. I would suggest using a supported/tested
> distro for honister release inside a VM or container to build it.
Thanks, Khem. Yes, that is what I eventually resorted doing. It's much
quicker to fire up a VM than trying to do the backports. :)
>> Regards,
>>
>> --
>> Alexandre Belloni, co-owner and COO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> You automatically follow any topics you start or reply to.
>> View/Reply Online (#61058): https://lists.yoctoproject.org/g/yocto/message/61058
>> Mute This Topic: https://lists.yoctoproject.org/mt/101487564/1997914
>> Group Owner: yocto+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [raj.khem@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
--
Rudolf J Streif
CEO/CTO
1.855.442.3386
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-09-21 1:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-20 20:59 Forcing uninative? Rudolf J Streif
2023-09-20 21:16 ` [yocto] " Alexandre Belloni
2023-09-20 21:39 ` Rudolf J Streif
2023-09-20 22:42 ` Richard Purdie
2023-09-21 1:32 ` Khem Raj
2023-09-21 1:53 ` Rudolf J Streif
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.