On Sun, Mar 15, 2026 at 08:10:11PM -0700, Mark Millard wrote: > On 3/15/26 19:18, bob prohaska wrote: > > On Sun, Mar 15, 2026 at 09:29:21PM +0100, Miroslav Lachman wrote: > >> On 15/03/2026 18:11, bob prohaska wrote: > >>> On Fri, Mar 13, 2026 at 07:33:46PM +0100, Miroslav Lachman wrote: > >>>>>> > >>>>>> OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS > >>>>> > >>>>> Placed in /usr/local/etc/poudriere.conf ? > >>>> > >>>> It should be in /usr/local/etc/poudriere.d/make.conf or > >>>> <setname>-make.conf > >>>> or <tree>-make.conf or... > >>>> > >>> At the moment I have > >>> # cat /usr/local/etc/poudriere.d/make.conf > >>> > >>> OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS > >>> > >>> but poudriere is reporting > >>> # tail *.log > >>> [10:11:33] [04] [00:00:00] Building x11/libXrender | libXrender-0.9.12 > >>> [10:26:37] [04] [00:15:04] Finished x11/libXrender | libXrender-0.9.12: > >>> Success > >>> [10:27:41] [01] [00:16:08] Finished x11/libXext | libXext-1.3.6,1: Success > >>> [10:38:32] [03] [00:26:59] Finished x11-toolkits/libXt | libXt-1.3.0,1: > >>> Success > >>> [10:38:36] [01] [00:00:00] Building x11-toolkits/libXmu | libXmu-1.1.4,1 > >>> [10:38:36] [03] [00:00:00] Building x11/libXpm | libXpm-3.5.17_1 > >>> [10:54:08] [03] [00:15:32] Finished x11/libXpm | libXpm-3.5.17_1: Success > >>> [10:54:53] [01] [00:16:17] Finished x11-toolkits/libXmu | libXmu-1.1.4,1: > >>> Success > >>> [10:54:56] [01] [00:00:00] Building x11-toolkits/libXaw | libXaw-1.0.16,2 > >>> [11:22:54] [01] [00:27:58] Finished x11-toolkits/libXaw | > >>> libXaw-1.0.16,2: Success > >>> > >>> Could the leading blank be causing poudriere to ignore the directive? > >>> Did I manage to slip in another typo? > >> > >> The blank should be OK. You can take a look in build log of some package > >> what options it has detected. > >> > >> Are you building only bind920 or is it some larger package set? I know > >> there > >> are some packages pulling X11 libraries unconditionally because the are > >> needed / are not optional. And some packages have X11 as a user selectable > >> option, but must be set to ON because consumer of this dependency expect > >> support of X11 from it. > >> > > I'm building bind-tools and bind920, which far as I know are all > > command line only. > > > >> Even with the OPTIONS_UNSET = X11 GUI CUPS DOCS EXAMPLES NLS I still see > >> these libraries being built. > >> > >> libX11-1.8.12,1.pkg > >> libXau-1.0.12.pkg > >> libXdmcp-1.1.5.pkg > >> libXext-1.3.6,1.pkg > >> libXrandr-1.5.4.pkg > >> libXrender-0.9.12.pkg > >> > > > > Trying to look for the above packages served up a surprise. If I do > > # tail bind.log > > [1D:06:09:30] [03] [00:56:39] Finished graphics/jpeg-turbo | > > jpeg-turbo-3.1.3: Success > > [1D:06:09:37] [03] [00:00:00] Building graphics/tiff | tiff-4.7.1 > > [1D:06:13:18] [02] [00:26:01] Finished x11-fonts/fontconfig | > > fontconfig-2.17.1,1: Success > > [1D:06:36:09] [03] [00:26:32] Finished graphics/tiff | tiff-4.7.1: Success > > [1D:06:36:13] [02] [00:00:00] Building graphics/webp | webp-1.6.0 > > [1D:06:42:57] [01] [01:30:06] Finished devel/pcre2 | pcre2-10.47_1: Success > > [1D:06:43:03] [01] [00:00:01] Building devel/glib20@bootstrap | > > glib-bootstrap-2.84.4,2 > > [1D:07:22:17] [02] [00:46:04] Finished graphics/webp | webp-1.6.0: Success > > [1D:07:22:23] [02] [00:00:01] Building graphics/gd | libgd-2.3.3_13,1 > > [1D:07:46:52] [02] [00:24:30] Finished graphics/gd | libgd-2.3.3_13,1: > > Success > > # > > the output makes sense. But if I do > > > > #more bind.log > > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ > > the file looks like it's binary, which I'm reasonably sure it isn't. > > Try?: > > # file bind.log
bob@pelorus:/usr/local/poudriere % file bind.log bind.log: data > # head bind.log bob@pelorus:/usr/local/poudriere % head bind.log [06:43:28] [02] [00:08:20] Finished misc/help2man | help2man-1.49.3_1: Success ^^^^^^^^^^ it looks like the beginning of the file was simply skipped by head It was my fault; I inadvertently started a duplicate poudriere build command that overwrote the beginning of the log file, subsequently killing the separate session after reallizing what I'd done. The first session meanwhile kept running. The result is still a bit odd: The command to poudriere was poudriere bulk -j main dns/bind920 dns/bind-tools > bind.log So, two different PIDs writing to the same file. Isn't there some mechanism to keep that from happening? > (There are other programs for looking at files that have arbitrary byte > values. I'll note try to list them here.) > > tail could be simply skipping past the null characters before finding > the last lines (the ones to be displayed). > That seems to be exactly what happened. > A null character in a file is enough to make it be classified as binary > as I remember. > > Finding how null characters got into what should have been a text file > could lead to FreeBSD OS problems or to program problems (or both). Primarily this was my error. Whether the system should have reported it as an error is less clear to me. > > > Using less explicitly states the file is binary. Maybe this is a bug > > in -current that I hadn't noticed until now..... The greater bug is the bum on the seat, but there might be a lesser weevil in the second PID not noticing it's writing to a file owned by another, older process. Thanks for writing! bob prohaska
