Package: texinfo
Version: 6.5.0.dfsg.1-3
Severity: minor

Dear maintainer,

I noticed that the Perl XS code in this package gets built without
debugging symbols, so they are not in the -dbgsym package. Furthermore,
the XS build doesn't honor DEB_BUILD_OPTIONS=noopt. These glitches make
debugging unnecessarily hard.

Snippet from a build log, note that the default '-g -O2' are missing.

  make[6]: Entering directory '/<<PKGBUILDDIR>>/tp/Texinfo/Convert/XSParagraph'
  /usr/bin/xsubpp -typemap /usr/share/perl/5.26/ExtUtils/typemap XSParagraph.xs 
> XSParagraph.xsc && mv XSParagraph.xsc XSParagraph.c
  /bin/bash ./libtool  --tag=CC   --mode=compile aarch64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I.  -I. -I./lib -I./lib  -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -DVERSION=\"0\" -DXS_VERSION=\"1\" 
"-I/usr/lib/aarch64-linux-gnu/perl/5.26/CORE"  -MT 
XSParagraph_la-XSParagraph.lo -MD -MP -MF .deps/XSParagraph_la-XSParagraph.Tpo 
-c -o XSParagraph_la-XSParagraph.lo `test -f 'XSParagraph.c' || echo 
'./'`XSParagraph.c
  libtool: compile:  aarch64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I./lib 
-I./lib -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DVERSION=\"0\" 
-DXS_VERSION=\"1\" -I/usr/lib/aarch64-linux-gnu/perl/5.26/CORE -MT 
XSParagraph_la-XSParagraph.lo -MD -MP -MF .deps/XSParagraph_la-XSParagraph.Tpo 
-c XSParagraph.c  -fPIC -DPIC -o .libs/XSParagraph_la-XSParagraph.o
  libtool: compile:  aarch64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I./lib 
-I./lib -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DVERSION=\"0\" 
-DXS_VERSION=\"1\" -I/usr/lib/aarch64-linux-gnu/perl/5.26/CORE -MT 
XSParagraph_la-XSParagraph.lo -MD -MP -MF .deps/XSParagraph_la-XSParagraph.Tpo 
-c XSParagraph.c -o XSParagraph_la-XSParagraph.o >/dev/null 2>&1

-- 
Niko Tyni   [email protected]

Reply via email to