Date: Thu, 25 Apr 2024 01:00:01 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 278560] www/chromium 124.0.6367.60 on 13.2-RELEASE-p10 compile failure Message-ID: <bug-278560-28929-aYVzXC0kwh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278560-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-278560-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278560 Tatsuki Makino <tatsuki_makino@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #6 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- I'm running into this problem too :) I am still still :) using 12.4-STABLE and thought it was due to the version being out of support, but it is not. It seems possible that this could also happen in 14.0-RELEASE. #define HAVE_PTHREAD_SET* seems to have added from chromium-124.0.x.x. FreeBSD has pthread_setname_np in <pthread.h>. But it is between #if__BSD_VISIBLE and #endif. <sys/cdefs.h> could cause __BSD_VISIBLE to be 0 if -std=3Dc99 or -std=3Dc11= ? is present. FreeBSD also has pthread_set_name_np in <pthread_np.h>. So the correct answer for FreeBSD is the following. #define HAVE_PTHREAD_SET_NAME_NP 1 #define HAVE_PTHREAD_SETNAME_NP 0 www/chromium creates and uses the following config.h at build time. (ARCH=3Damd64) ${WRKSRC}/third_party/ffmpeg/chromium/config/Chrome/freebsd/x64/config.h The file has them both as 1. HAVE_PTHREAD_SETNAME_NP may need to be set to 0. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278560-28929-aYVzXC0kwh>