doas.c:380: error: 'DOAS_CONF' undeclared

[slicer69]

doas.c:380: error: 'DOAS_CONF' undeclared

[prologic]

Hmm trying to build manually by hand leads to:

# make CC=tcc
tcc -Wall -O2 -DUSE_PAM -DDOAS_CONF=\"/usr/local/etc/doas.conf\"  -D_GNU_SOURCE -include compat/compat.h -Icompat  -c -o doas.o doas.c
In file included from doas.c:48:
doas.c:48: error: include file 'security/pam_appl.h' not found
make: *** [<builtin>: doas.o] Error 1
#

This system doesn't have any "PAM" -- It's mostly just a busybox userland more or less with a musl libc and tcc C compiler

[prologic]

Hmmm building with -DUSE_BSD_AUTH isn't going to work either :/

# make CC=tcc
tcc -Wall -O2 -DUSE_BSD_AUTH -DDOAS_CONF=\"/usr/local/etc/doas.conf\"  -D_GNU_SOURCE -include compat/compat.h -Icompat  -c -o doas.o doas.c
In file included from doas.c:43:
doas.c:43: error: include file 'bsd_auth.h' not found
make: *** [<builtin>: doas.o] Error 1
#

What options do we have here on a very non-traditional system?

[slicer69]

To answer your first question, DOAS_CONF is set in the Makefile. It looks like the build process is trying to do things manually rather than run the Makefile or isn't compatible with GNU Make.

As for building doas without doas or BSD Auth, it's not going to work. If the system is so minimal that it doesn't have PAM then it's not going to build/run.

[prologic]

As for building doas without doas or BSD Auth, it's not going to work. If the system is so minimal that it doesn't have PAM then it's not going to build/run.

I take it this pretty much applies to sudo as well? Basically no doas/sudo on busybox-based systems?

[slicer69]

I can't speak for the sudo devs, but I know the sudo package on Debian pulls in PAM as a dependency. FreeBSD's sudo port does too, at least with the default build.

[prologic]

Yeah no worries. I think it would be difficult to get PAM into this very small system. I'll close this issue, but thanks for responding! 🙇‍♂️