On Mon 02 Oct 2023 at 21:38:32 +0100, Jonathan Perkin wrote:
> > Yes. But how would it be used? I see a few packages that have
> > CTF_SUPPORTED=no and some that have CTF_FILES_SKIP+=somefile.
> > That seems to be about pkgsrc doing something with CTF outside of the
> > knowledge of the upstream build system.
>
> CTF support in pkgsrc:
>
> * Adds -gdwarf-2 via the wrappers to all compiler calls
> * runs ctfconvert on all suitable binaries after install
> * runs gstrip to remove non-CTF debug data
>
> This way you get fully debuggable binaries without the bloat of DWARF or
> non-existent debug package support, and I've used it for many years in my
> illumos binary package sets.
It looks like the only change needed for that is
cvs diff: Diffing platform
Index: platform/NetBSD.mk
===================================================================
RCS file: /cvsroot/pkgsrc/mk/platform/NetBSD.mk,v
retrieving revision 1.77
diff -u -r1.77 NetBSD.mk
--- platform/NetBSD.mk 16 Aug 2023 08:07:01 -0000 1.77
+++ platform/NetBSD.mk 3 Oct 2023 13:55:46 -0000
@@ -209,6 +209,7 @@
PKG_DBDIR=/var/db/pkg to /etc/mk.conf.
.endif
+_OPSYS_SUPPORTS_CTF= yes # Compact Type Format conversion.
_OPSYS_SUPPORTS_CWRAPPERS= yes
_OPSYS_SUPPORTS_MKTOOLS= yes
With that (and suppressing the use of ctfconvert in wm/ctwm) I get as
part of the "make install" output
-- Installing: /tmp/pkgsrc/wm/ctwm/default/.destdir/usr/pkg/man/man1/ctwm.1.gz
-- Installing: /tmp/pkgsrc/wm/ctwm/default/.destdir/usr/pkg/share/doc/ctwm/ctwm.1.html
=> Generating CTF data
=> Automatic manual page handling
=> Generating post-install file lists
and .work.log shows an invocation of ctfconvert. That should be it,
right? I'll commit it if it seems ok to you. Or should there be a
version check on NetBSD version before enabling _OPSYS_SUPPORTS_CTF?
-Olaf.
--
___ Olaf 'Rhialto' Seibert <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work. --I. Rose
Attachment:
signature.asc
Description: PGP signature