Re: [OE-core] [dunfell][PATCH] core: glib-2.0: fix requested libmount/mkostemp/selinux not being linked in

2020-08-20 Thread Ahmad Fatoum
Hello, On 8/3/20 4:32 PM, Steve Sakoman wrote: > On Sun, Aug 2, 2020 at 9:43 PM Ahmad Fatoum wrote: >> >> Hello, >> >> On 7/20/20 12:30 PM, Ahmad Fatoum wrote: >>> Since 010202076760 ("meson.bbclass: avoid unexpected operating-system >>> names"), meson is no longer used with a cross file that

Re: [OE-core] [dunfell][PATCH] core: glib-2.0: fix requested libmount/mkostemp/selinux not being linked in

2020-08-03 Thread Steve Sakoman
On Sun, Aug 2, 2020 at 9:43 PM Ahmad Fatoum wrote: > > Hello, > > On 7/20/20 12:30 PM, Ahmad Fatoum wrote: > > Since 010202076760 ("meson.bbclass: avoid unexpected operating-system > > names"), meson is no longer used with a cross file that appends the used > > libc to the operating system name,

Re: [OE-core] [dunfell][PATCH] core: glib-2.0: fix requested libmount/mkostemp/selinux not being linked in

2020-08-03 Thread Ahmad Fatoum
Hello, On 7/20/20 12:30 PM, Ahmad Fatoum wrote: > Since 010202076760 ("meson.bbclass: avoid unexpected operating-system > names"), meson is no longer used with a cross file that appends the used > libc to the operating system name, e.g. linux-gnueabi. > > Prior to that commit, the host_system ==

[OE-core] [dunfell][PATCH] core: glib-2.0: fix requested libmount/mkostemp/selinux not being linked in

2020-07-20 Thread Ahmad Fatoum
Since 010202076760 ("meson.bbclass: avoid unexpected operating-system names"), meson is no longer used with a cross file that appends the used libc to the operating system name, e.g. linux-gnueabi. Prior to that commit, the host_system == 'linux' checks in glib's meson failed, which led to glib