Re: LFS build of File-5.45 problem stops on compilation of seccomp.c

"Xi Ruoyao" ([email protected] via lfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.support
Message-ID <[email protected]>
On Wed, 2025-02-19 at 18:33 +0000, Dave Kohler wrote:
> Using LFS 12.2 book and build on a current ARCH environment, Everything runs
> smoothly until I reach the steps in chapter 6.7 File 5.45.Please help!
> 
> I purged everything and started again with the same result.  I also tried
> going to the LFS-BOOK-12.3-rc1 with the associated updates to the source
> tarballs. I end up getting the same error. Having search the web, FAQs,
> various troubleshooting sites, I am send this message for assistance. I am new
> and unfamiliar with doing a post by this method and cannot send you the full
> captured terminal session as far as I know. So here is a distillation of what
> I encountered. If there is a way I can send at 500+ line terminal session in a
> zip format, let me know how and I will provide. FWIW, I have set my make to
> use MAKEFLAGS=-j12.
> 
> When in the build subdirectory step , I copy/paste the configure command
> parameters which include 'disable-libseccomp' and the configure output shows
> 'checking for libseccomp support... no', as expected. The next step 'make'
> outputs
> ====
> make  all-recursive
> make[1]: Entering directory '/mnt/lfs/sources/file-5.45/build'
> Making all in src
> make[2]: Entering directory '/mnt/lfs/sources/file-5.45/build/src'
> sed -e "s/X.YY/$(echo 5.45 | tr -d .)/" < ../../src/magic.h.in > magic.h
> make  all-am
> make[3]: Entering directory '/mnt/lfs/sources/file-5.45/build/src'
>   CC       file.o
>   CC       seccomp.o
> ....
> =====
> and this make step completes successfully. whereupon I entered the popd
> command , and see output
> '/mnt/lfs/sources/file-5.45' placing my current pwd back in file-5.45.
> 
> 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.
> 
> The next step fails:
> lfs:/mnt/lfs/sources/file-5.45$ make FILE_COMPILE=$(pwd)/build/src/file
> with this output
> =====
>   CC       file.o
>   CC       seccomp.o
>   CC       buffer.lo
>   CC       magic.lo
>   CC       apprentice.lo
>   CC       softmagic.lo
>   CC       ascmagic.lo
>   CC       encoding.lo
>   CC       compress.lo
>   CC       is_csv.lo
>   CC       is_json.lo
>   CC       is_simh.lo
> seccomp.c:34:10: fatal error: seccomp.h: No such file or directory
>    34 | #include <seccomp.h> /* libseccomp */
>       |          ^~~~~~~~~~~
> compilation terminated.
> make[3]: *** [Makefile:557: seccomp.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[3]: Leaving directory '/mnt/lfs/sources/file-5.45/src'
> make[2]: *** [Makefile:382: all] Error 2
> make[2]: Leaving directory '/mnt/lfs/sources/file-5.45/src'
> make[1]: *** [Makefile:464: all-recursive] Error 1
> make[1]: Leaving directory '/mnt/lfs/sources/file-5.45'
> make: *** [Makefile:373: all] Error 2
> 
> Attempting to redo this last make step with -j1 produces the same outcome.

Please attach config.log from your file build, as we've requested in
section 1.5 "Help."

-- 
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.