Date: Mon, 22 Mar 2021 18:32:29 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: TCL and Unicode Message-ID: <829C6E3C-12B3-44FC-8B18-D3F0ACA87B57@FreeBSD.org> In-Reply-To: <20210322134003.hhdmq6ljxun4tsyn@mutt-hbsd> References: <20210322134003.hhdmq6ljxun4tsyn@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_E3C40213-F80A-418E-9C9B-1BA396F3757B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 22 Mar 2021, at 14:40, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: >=20 > I'm tracking down a regression in ports regarding TCL and unicode. The > primary victim of the problem is databases/sqlite3. Note that I use > freebsd-ports on github as my upstream, so I'll be using git commit > hashes from that repo. >=20 > The sqlite3 build failure can be seen at [1]. >=20 > If I revert commit 787aad81fc79d441fb0c9a750e6e33b6c0ea7ac6, sqlite3 > builds fine. I noticed a few key changes from that commit: >=20 > The build of sqlite3 depends on TCL: instead of using the distfile > that has the autoconf artifacts pre-generated, the distfile without > the autoconf artifacts is used (changing from > sqlite-autoconf-3340100.tar.gz to sqlite-src-3340100.zip). This > means that the TCL-based autoconf artifacts must be generated > locally. At least, partially. It seems that the only part of the > build that depends on TCL is the sqlite3_analyzer. >=20 > Admittedly, this change is somewhat confusing to me. I'm having > somewhat of a hard time knowing whether it's TCL or sqlite3 itself > as the main culprit. >=20 > Any guidance is appreciated. >=20 > [1]: = http://ci-08.md.hardenedbsd.org/data/hardenedbsd-current_amd64-local/2021-= 03-21_13h53m43s/logs/errors/sqlite3-3.34.1,1.log Hi Shawn, It builds fine for me locally on 14.0-CURRENT (as of ~2 days ago), and indeed the sqlite3.c file is now dynamically generated by tcl. In your CI failure case, it looks like something is inserting blobs of zero bytes into the resulting file, though? So either the file system is going bad, or tcl is outputting nonsense, for some reason. At least, I think you'll have to do some investigations in that direction... -Dimitry --Apple-Mail=_E3C40213-F80A-418E-9C9B-1BA396F3757B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iFwEARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCYFjUrQAKCRCwXqMKLiCW o32AAJjCwpY3HvoYpHk0hFybBMPdqucUAKDoBNwChFWbSt6uibgyf+xMzgYIwQ== =DMW8 -----END PGP SIGNATURE----- --Apple-Mail=_E3C40213-F80A-418E-9C9B-1BA396F3757B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?829C6E3C-12B3-44FC-8B18-D3F0ACA87B57>