On 31/08/20 10:12, Emmanuel Blot wrote:
>
>> This is done by "b_lundef=false". I think it was added for modules, but
>> maybe it's not necessary. Emmanuel, can you try removing it (line 3 of
>> meson.build) and seeing if --enable-modules still works for you?
>
> Removing this option does
On 30 Aug 2020, at 11:35, Paolo Bonzini wrote:
This is done by "b_lundef=false". I think it was added for modules,
but
maybe it's not necessary. Emmanuel, can you try removing it (line 3
of
meson.build) and seeing if --enable-modules still works for you?
Removing this option does restore
On 27/08/20 10:16, Thomas Huth wrote:
> Seems like this is added by meson itself (see
> meson/mesonbuild/linkers.py), not by our meson.build files ... Paolo,
> any idea why this happens?
This is done by "b_lundef=false". I think it was added for modules, but
maybe it's not necessary. Emmanuel,
On 26/08/2020 15.11, Emmanuel Blot wrote:
> Hi,
>
> I’ve noticed that since meson builds have been enabled, on macOS, the
> build outcome with undefined symbols has changed:
>
> - prior to meson introduction (v5.1.0):
> * referencing an undeclared symbol in source code led to a warning at
>
Hi,
I’ve noticed that since meson builds have been enabled, on macOS, the
build outcome with undefined symbols has changed:
- prior to meson introduction (v5.1.0):
* referencing an undeclared symbol in source code led to a warning at
compile stage
* referencing an undeclared symbol at
