Re: LFS build of File-5.45 problem stops on compilation of seccomp.c
"Ken Moffat" ([email protected] via lfs-support Mailing List) <[email protected]> Thu, 20 Feb 2025 16:40:37 +0000
| Newsgroups | gmane.linux.lfs.support |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Feb 19, 2025 at 06:33:12PM +0000, "Dave Kohler" wrote: This reply is not relevant to your main problems, just explaining a minor detail. > > I follow this with the next step, './configure --prefix=/usr --host=$LFS_TGT > --build=$(./config.guess)'. > In the middle of the output for this step I see the following: > ==== > ... > checking for zlib support... > checking for bzlib support... > checking for xzlib support... > checking for zstdlib support... > checking for lzlib support... > checking for libseccomp support... > checking for file formats in man section 5... no > ... > =================== > This seems surprising to me because I was assuming the libseccomp support was > not desired by LFS. > However configure step appears to complete with success. Perfctly normal. 'configure' scripts vary greatly, many do not report 'yes' or 'no' for *some* of the things they check for. In my ~/vimrc I highlight trailing whitespace in red (something I picked up years ago from an lkml post - ok on a term with a black background, probably horrid if the background is white) and looking at a recent log for this package I see what you have, and each of those lines which end '...' have an space after the '...', i.e. neither yes nor no was written, ĸen -- The three certainties in computing: BGP errors, DNS failures, incorrect time/date functions, and off-by-one errors. -- http://lists.linuxfromscratch.org/sympa/info/lfs-support Unsubscribe: See the above information page