On Wed, Nov 27, 2019 at 08:18:59PM +0100, Antoine Jacoutot wrote: > On Wed, Nov 27, 2019 at 08:16:16PM +0100, Marc Espie wrote: > > I added a warning in build-debug-info that says there's actually no debug > > info. > > > > > > The following ports show it. > > > > databases/evolution-data-server > > devel/atk > > devel/fribidi > > devel/glib2 > > graphics/babl > > graphics/gdk-pixbuf2 > > graphics/gegl04 > > net/gupnp/core > > net/gupnp/tools > > sysutils/deja-dup > > x11/gnome/gvfs,,-goa > > x11/gnome/gvfs > > x11/gnome/nautilus > > x11/gtk+4,-cloudprint > > > > which probably means -g does not get through or stripping occurs anyway. > > > > For instance, in atk, there's a telltale: > > Stripping target 'atk/libatk-1.0.so.21809.3' using strip. > > > > Likewise in glib2: > > Stripping target 'gio/gsettings' using strip. > > > > ... > > > > all those need a bit more love. Compiling with -g is cool, not running > > strip during fake will help. > > This looks like meson ports.
Probably because of this: .if empty(DEBUG) MODMESON_CONFIGURE_ARGS += --buildtype=plain .else MODMESON_CONFIGURE_ARGS += --buildtype=debug .endif I'll try and have a look maybe this week-end. -- Antoine
