Created attachment 8893 [details] Patch to fix issue OpenBSD's nm(1) does not have -D option, and it defaults to equivalent behavior. An alternative also could be using the objdump(1), but I'm not sure if it's more portable.
Created attachment 8900 [details] Patch to fix issue via git format-patch
Comment on attachment 8900 [details] Patch to fix issue via git format-patch like in other places I think it would be better wo test how the "nm" binary behaves instead of just looking at the os version string. Probably it is also possible to use a "nm" on openbsd which has other options and also it is possible to have the openbsd like "nm" on other operatin systems. This is why we should check how "nm" behaves.
nm(1) on OpenBSD grew a -D option on 2015/05/17.
Vadim had introduced a similar patch in the OpenBSD net/samba port. Since our nm(1) supports the -D flag, I have removed this patch. I don't think that keeping this issue opened is worth it, as far as OpenBSD is concerned.
okay, as Samba is becoming slowly more usable on OpenBSD it's not worth fixing this for past releases. We're still waiting for the NGROUPS_MAX limitation on OpenBSD to disappear ...