On 2026-04-29, vl <[email protected]> wrote:
> I guess there is not much need to document headers if you read them.
> Oh well, I knew that I must have missed something, being a newbie.
indeed, it's the functions that are in the headers where doc is
really wanted.
btw you can search like this:
$ man -k any=varargs.h
va_start, va_arg, va_copy, va_end(3) - variable argument lists
$ man -k any=strings.h
bcmp(3) - compare byte string
bcopy(3) - copy bytes
bzero, explicit_bzero(3) - write zeroes to a byte string
ffs, ffsl, ffsll(3) - find first bit set in a bit string
strcasecmp, strcasecmp_l, strncasecmp, strncasecmp_l(3) - compare strings,
ignoring case
strchr, index(3) - locate first occurrence of a character in a string
strrchr, rindex(3) - locate last occurrence of a character in a string
> On crosscompiling: I know, self-hosting arches and all.
> Might still be useful for some emulators/, vmm experiments, docker.
> It is a blocker for this particular port I try my hands at.
> Currently I use headers extracted from llvm tarball, not ideal.
there might be a sensible way to do it differently, posting your
port might encourage someone to look for a better approach.
without that, rather than extracting from a specific tarball,
you could add MODULES=lang/clang and
BUILD_DEPENDS=${_MODCLANG_BUILD_DEPENDS}:patch and then
point your software at files under ${WRKDIR}/devel/llvm/19/llvm-*/...
--
Please keep replies on the mailing list.
