Date: Mon, 09 Mar 2026 19:29:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 293660] 15.0-RELEASE FTBFS in crypto/krb5 when cross-compiling on x86_64-linux-gnu host Message-ID: <bug-293660-227-w9dHhTDe2n@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-293660-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293660 Ed Maste <emaste@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cy@FreeBSD.org, | |emaste@freebsd.org --- Comment #2 from Ed Maste <emaste@freebsd.org> --- Ah, crypto/krb5/src/util/support/strerror_r.c has this: #elif defined(STRERROR_R_CHAR_P) /* * Implement the POSIX strerror_r API in terms of the GNU strerror_r, which * returns a pointer to either the caller buffer or a constant string. This is * the default version on glibc systems when _GNU_SOURCE is defined. */ int k5_strerror_r(int errnum, char *buf, size_t buflen) { const char *str; str = strerror_r(errnum, buf, buflen); if (str != buf) { if (strlcpy(buf, str, buflen) >= buflen) { errno = ERANGE; return -1; } } return 0; } so I think we just need to figure out how best to set that in the crossbuild environment -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293660-227-w9dHhTDe2n>