From nobody Wed Oct 15 15:47:45 2025 X-Original-To: freebsd-pkg@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cmwTb5rpHz6CZSW for ; Wed, 15 Oct 2025 15:48:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-24.consmr.mail.gq1.yahoo.com (sonic311-24.consmr.mail.gq1.yahoo.com [98.137.65.205]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4cmwTb3Mfwz3nLT for ; Wed, 15 Oct 2025 15:48:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760543281; bh=r1/9TRTJ1h8UZs5fpjFnz+5bbZoBlpwp/8JjAU3lQIk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=FQ5mXkd1pqu7vglnZoUwdqA2A7e7e77BJZtMEctEwpl85ANkBd+Li+nVKFXATUszTygwYnMYt3F6rWh5LtfXgh0mmsuJVMB2QkRV0lvKr2cVCPHu80mLHUqRQqlfOP7KBs0UlqiGGNVf21u8Qkmf9ZlEn+pbMXSr7PFO9wLwU9OdNuXF0XfCRI+l3HcjMFnevPtV1dYtf59qgZqAjec1sr1ffmOPWuq9SA3eVUctcakENGS/4UGlEar9PNrqNgY6ImqtdZijSc0GNuNzN22ayylK71p3kESq1EuMADiC274VeRaH1O6NpjlmAZLQqX/Xt26XK9LBpAfwHJOg/Jp8Sg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760543281; bh=C3E5OjWlMFeYKc5Rk8dTR+tD/O3hTaEN9PgTua4Mqkz=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=ovVaEh10OYvtMByzSdw3WlBAw6JvkqslDO3PuCURLnGCRd63u0fHEMqOFMHpg2GrGdTa+kO275xDDqZ9CgLo4kDQ85uGpYAmHYFPiuWHz7RLc6WhcVUHVd/etgwytc6/m85nvPH+YzH2TxCRMoHUHOYObJFiKnTPyO4D2Y8w2J9X+Xpiis3c29ru4Nijr3DYlNvICNcX9IDUvyFQfpbcY+Zp3NcXeHptZAFOExfRLndwn376S8BeuCT3/NMjMtNjJSDRXSygnUPUhEIqRN+20TmftimQoqkmr1og/bqpmRYhJoSdTRi+yzYSbd13TnNAIDiRCqWUtMdz0QW5NtZSmA== X-YMail-OSG: _DPxCwYVM1k8__gj609XLRCJhqUtlPq2IebS33tsYxKVdU3PC66_3X6.v2fkjK. ohVuvgZDW6yT6x_tyLGaChfiQ39EcqvD5KGQ0L4lj0HolVzrSE6bTx1.jR6iEbOkSmGAj_okq_wX IGw046hWZRE6z7wq4VUyKUWcmX2Lx6AQHBzqNFN7Y2WFIUPFoQ55hX4olgXz5qAL4sZF8HXZ83oT Sj_HUZuj4GxWmTw3bzzc9QqTksycmjzOi_HSpKfQ3NzWMB55K83oXqPQE5OeVJFHs0Xr5eSMlFbz nq9Fd.dRZvqkAQMoPZiNx4ineKGVqn.bC3HJmD91ApA9M.Lf6o0ksCQyXkH_qkczjFTArgsx4Mjh 9JtlZQVpPEaDI_8bBZmQTCiKEVmPR2vg.mLkmdDivMqErVR3I10o492stEzlUqWGSy0bAEMtKTtY NrMRVYQPHcoI4DyQPZvjg37ArTvxauFrstJQw88.V0k9dAo913zeydf0w8GS3ox38bxMTGWasD7X 1RPgcuYCul1ovZYy4wdeS_bPlRU8mYiWyKDPsXxOQbOuMMhJmU4GVaBh_WDJu9.F.8MzRQb9UepT rbmy4N7xkYgBkSx3V6NlvW_LJQaYICm9oam.XkN8C2gXckzD9lrDDkvlOsqvZX1KSsQGQLiULMCW mc7.BKsJMa3prekYfW.BOsrOubHfUnF3hb3L0UMG8pVunj9f3ixKmISGPNZntTJHwQlTi5Avv32z NWgLxrbc3tj0puQUkiStOhY86gLy4TItGiB_0hedYKjeklJPPk_HQpiG7SNGL8YxTSTt8ETXCOkL mTvzNYlUYhlR_YUbaEgQIOSsDhST_Wbt3ktGXIgLUHkNFdc6EdjbnuZoAlJsR4YAIDVBkFvGPB36 Vl1jdiDvd1JBrji02eHOzaY2z_ubh2Jm7wYcauICfeUkJBdR3SKzAkOYpoYmg26YjsREgj.eTMmD EmvmuNGjSlkXHcjeHzyq.Au34Gq_THpPt3LJjo7uNMWs.pf4qQVFQewjf8RdgR5KgXYZRsH13yBr 4A.JFPvsC8LB7J99SZ3BwJuQM9YaEJquvb2caf3GS92gzY2hZ.hjMpO044g_hG21nZ094raRJl9B FgavEUpVaLaSZa.R4LM.P6V6EfsoDGpa0_P4byq0dQv3AMeAp6TD7izMv_CyNYUb1wPuuouTYZqe g.VTUcJdJrwPRY37rg2MYvZpNrXrquOVi.wN44BY2vww9uN4txi9Bq5RHprEjtPOh2WIJRfZ7P_7 MCQ3g7wX5gN3gsVMc8keUJEEn229Q3RCf_SkkdymuTIdLHoz8plWaXpa7gT7LhB85.gvJ.ZjyXjU 1eXxcQSQ1477jTzNa.kUD2ZF4Wr9rROfcRUB4FaL3KA1024.Kgns0LzuUkrLEhzr1nx10VEyGveg C7MD_kwvWPhSpWXssMDD2hNWySRSMRK172UOF3KQTM7O48PorBHvEJw6_aSuHfFGYvxemKde.lXS w7uia.L701DtmBrvGnKgljcKFDxdJxQDYTcWyi9d1g..shNuPbiG0jvqByzNWYhqAHDf1Yybev30 _LjsVhGZiyQ_N3i7Dgvbux700DH_hNxtO.mvJHFQOiuB8xRqaGs6y.0i7msFGIsrZjUgaNHTersg nwQeiVkajBGiaxF1QrV60UhBvKlcj5OErZ7jTD0p5lafOgOKyjPQ1PD_h6vHDcXPGr5cgNREHrMZ l8hv0tDeYrE8QDgtgudTcGw7Osr39wkqm0glN5Vb.TC5L3t.xOpjxFmNgYC_OBuZoDrjLx86N.y5 E8b5sJ3QIPUzsv8vuPH_RmsdWmlRqMaoSE7vRgcYYy5xcVjJWBm3baCg3GmuNDd1xxxltdTF0VIw A85S_16ZXXQ11TsU6Hm_MjmSyvPGFU_vpbH29KNiTUcGoqaFG60ColbK0ee28YTqL4UTVh68UcKV v3KZeTayQOQPailBpKsGLD4RoLkBAmDTuQcwu9fRToVGhXoHeT3jKoOjPTV7HgGJEoYgjfGCPy.E aFafCJtbO5v39qWP03exVMcQGoJmgA2YHI9U2UDG5rc_NL61FnumFgqoXqNushOwTvFf9IDQNiNn dk0iwhL9MDn8GOpPlIIOv7nlFpTlMcgAEHgppR2qZ9zuQnWXh4sZGPBq3cx_m2IP.K3dwqOABt_b _vA3D_F2Qd6Nx1kis6NeiKUaoREy4dQjw1tQtzskL8pcsEXXzSLQndEFFg.2RKp9eMPoGgTfw2Cp ClMSrmDn8ljZjXKwS.4qT7YJY9re0TGBQpU6fKOUyYQVXuy0eVzx2JrUeudhVkNpholbhbJphAp5 aIw-- X-Sonic-MF: X-Sonic-ID: affdc5c1-b3d1-4274-80af-251bf5a52854 Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Wed, 15 Oct 2025 15:48:01 +0000 Received: by hermes--production-gq1-6c5b94f9b-q75p2 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 8c6782925b1e3e9fb24c9efeccb291d1; Wed, 15 Oct 2025 15:47:56 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Binary package management and package tools discussion List-Archive: https://lists.freebsd.org/archives/freebsd-pkg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkg@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: Undefined symbol "setgroups@FBSD_1.8" From: Mark Millard In-Reply-To: Date: Wed, 15 Oct 2025 08:47:45 -0700 Cc: freebsd-pkg@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <504EC476-50C6-49EC-85F6-AEB9C104F205@yahoo.com> References: <11DE790B-4E98-4D42-A281-E0B669474C89@yahoo.com> <2EC26A5F-3FEF-4D18-986D-A5106B164C64@yahoo.com> To: void X-Mailer: Apple Mail (2.3826.700.81) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cmwTb3Mfwz3nLT On Oct 15, 2025, at 06:31, void wrote: > On Tue, Oct 14, 2025 at 11:40:26PM -0700, Mark Millard wrote: >> On Oct 14, 2025, at 21:25, void wrote: >=20 >>> So, what you're saying makes sense. >>> But, I cannot install sccache for 13.5 on a stable/15 host. >>=20 >> Yes you can, presuming the usual compat support is included in >> the kernel. >=20 > Both the stable/15 server and the releng/13.5 poudriere builder > use unmodified GENERIC. They both have the compat support. 13.5 does not have compat support for 15 (or 14 or 16). 15 can have the compat support related to 13.5 . As Kyle E. referenced, if a static build of sccache(-overlay) is possible based on the kernel interface from 13.5 (or before), that would avoid the bad dynamic binding being involved at all and would have a kernel interface known to both 13.5 and 15 (15 with compat support). >> stable/15 can use older @FBSD_1.* symbols that it >> was designed to also be compatible with since the old interfaces >> were known at the time 15 was designed and implemented and, so, >> the compatibility code can be there to be referenced. That >> includes supporting 13.5 programs and libraries. >=20 > so it seems the compatibility code isn't being referenced > by sccache(-overlay). A bug in those ports? Or in the compatibility > code? Both? Again: 13.5 does not have compat support for 15 (or 14 or 16). That is a property of 13.5, not of sccache(-overlay). Execution in the 13.5 jail is execution in a 13.5 context as far as the world code goes, not 15. > ccache is also used (ccache4 built with -static), which > is called/copied from the server to be used internally in the builder. -static avoids variability in symbol binding by not having any dynamic binding to libraries involved: no dynamic lookup of FBSD_1.8 symbols (or other such). > ccache does not error like this. It was also built on the stable/15 = host. Because it a -static build, it is only dependent on the kernel interface, not any dynamically bound library code that would vary between 13.5 and 15. >> sccache(-overlay) needs to be built to use the @FBSD_1.0 compatible >> symbol in order to get the old beahvaior that it was designed for. >=20 > This seems to apply to sccache(-overlay) only and I don't understand > why it is only this or how to overcome it. You are not using a -static build of the sccache(-overlay). It is using dynamically bound library code that varies between 13.5 and 15 in an incompatible way. If you build ccache non-static, you could have similar problems with it. (I've no clue if it would use FBSD_1.8 symbols or not.) > Unless it is/are sccache(-overlay) > bug(s). Nope. It is because you built sccache(-overlay) using dynamic binding to FBSD_1.8 code that is 15 specific and 13.5 has no compat code for that but the jail is running a 13.5 world. >> One way to do that is to be built for 13.5 instead of 15.* and >> to run that 13.5 based code on on 15+ . >=20 > I don't know how and can't find any instructions on how to do this. Build the package in a 13.5 poudriere jail. Then use the *.pkg file that results to install that build of the package on 15 instead of using what you now have installed. If you can build that as a -static build, as Kyle suggested, that would be better than building something that uses dynamic binding. > I can guess, maybe. Build it in the releng/13.5 poudriere jail and = install it to stable/15 server? Yes. I suggest what Kyle suggested: building sccache(-overlay) as -static if you can. > I guess I can do this. It seems odd to have to manually do this, = though. > Do I need to revert when the stable/15 builders run? If 14+, 15+, 16+ has the 13.5 related compat code in place and you build a static sccache(-overlay) under 13.5, it likely works for all 13.5, 14+, 15+, and 16+ usage contexts. Use of the older dynamic binding nstead may be somewhat more likely to run into problems. > And why for just these two ports on the host? 2 ports (packages)? You have only reported 1 package with a binding to a 15+ specific symbol. Most programs probably do not use any version of that FBSD_1.8 symbol. Most programs probably do not use any symbols listed in FBSD_1.8 or the like. But your existing sccache(-overlay) build does. The only FBSD_1.8 symbols so far are as shown below (from a main 16 context 14): # cat /usr/src/lib/libsys/Symbol.sys.map /* * It'd be nice to automatically generate the syscall symbols, but we * don't know to what version they will eventually belong to, so for now * it has to be manual. */ . . . FBSD_1.8 { exterrctl; fchroot; getgroups; getrlimitusage; inotify_add_watch_at; inotify_rm_watch; jail_attach_jd; jail_remove_jd; kcmp; setcred; setgroups; }; I'll note that FBSD_1.6 was created at 13.0-CURRENT and FBSD_1.7 was created at 14.0-CURRENT. So using a symbol from FBSD_1.7 would have similar issues relative to 13.5: FBSD_1.7 { fspacectl; kqueuex; membarrier; sched_getcpu; swapoff; timerfd_create; timerfd_gettime; timerfd_settime; }; Again, it is not a large set of symbols and most programs probably do not bind to any of them. =3D=3D=3D Mark Millard marklmi at yahoo.com