On Mon, Dec 05 2022, Richard Purdie wrote:
> On Mon, 2022-12-05 at 11:00 +0100, Ola x Nilsson wrote:
>> On Wed, Nov 30 2022, Richard Purdie wrote:
>>
>> > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
>> > > On 30/11/2022 16:46:17+, Ross Burton wrote:
>> > > > On 30 Nov 2022, a
On Mon, 2022-12-05 at 11:00 +0100, Ola x Nilsson wrote:
> On Wed, Nov 30 2022, Richard Purdie wrote:
>
> > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
> > > On 30/11/2022 16:46:17+, Ross Burton wrote:
> > > > On 30 Nov 2022, at 14:20, Richard Purdie via
> > > > lists.yoctoproje
On Wed, Nov 30 2022, Richard Purdie wrote:
> On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
>> On 30/11/2022 16:46:17+, Ross Burton wrote:
>> > On 30 Nov 2022, at 14:20, Richard Purdie via
>> > lists.yoctoproject.org
>> > wrote:
>> > > > > * Could we optionally disable some of t
On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
> On 30/11/2022 16:46:17+, Ross Burton wrote:
> > On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> > wrote:
> > > > > * Could we optionally disable some of the glibc 32 bit function calls
> > > > > to ensure they
On 30/11/2022 16:46:17+, Ross Burton wrote:
> On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> wrote:
> >>> * Could we optionally disable some of the glibc 32 bit function calls
> >>> to ensure they're not being used?
> >>
> >> Could you be more specific here? Would you
On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
wrote:
>>> * Could we optionally disable some of the glibc 32 bit function calls
>>> to ensure they're not being used?
>>
>> Could you be more specific here? Would you like to disable some
>> syscalls?
>
> I'm meaning disablin
