Mock Version: 6.5 Mock Version: 6.5 Mock Version: 6.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target riscv64 --nodeps /builddir/build/SPECS/miniz.spec'], chrootPath='/var/lib/mock/f45-build-18983-534/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '2bcb22bcfc7745559ad518c753e90d5a', '-D', '/var/lib/mock/f45-build-18983-534/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target riscv64 --nodeps /builddir/build/SPECS/miniz.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784160000 Wrote: /builddir/build/SRPMS/miniz-3.1.2-2.fc45.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target riscv64 --nodeps /builddir/build/SPECS/miniz.spec'], chrootPath='/var/lib/mock/f45-build-18983-534/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '92281312adbf42f0b023ab334e412c9d', '-D', '/var/lib/mock/f45-build-18983-534/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.8siqju4q:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target riscv64 --nodeps /builddir/build/SPECS/miniz.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784160000 Executing(mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.uXn1ug Creating(rpmbuild.env): /builddir/build/BUILD/miniz-3.1.2-build/rpmbuild.env RPM_SOURCE_DIR="/builddir/build/SOURCES" RPM_BUILD_DIR="/builddir/build/BUILD/miniz-3.1.2-build" RPM_OPT_FLAGS="-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer" RPM_LD_FLAGS="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes " RPM_ARCH="riscv64" RPM_OS="linux" RPM_BUILD_NCPUS="8" RPM_SPECPARTS_DIR="/builddir/build/BUILD/miniz-3.1.2-build/SPECPARTS" export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR RPM_LD_FLAGS RPM_DOC_DIR="/usr/share/doc" export RPM_DOC_DIR RPM_PACKAGE_NAME="miniz" RPM_PACKAGE_VERSION="3.1.2" RPM_PACKAGE_RELEASE="2.fc45" export RPM_PACKAGE_NAME RPM_PACKAGE_VERSION RPM_PACKAGE_RELEASE LANG=C.UTF-8 export LANG unset CDPATH DISPLAY ||: unset DEBUGINFOD_URLS ||: unset RPM_CONFIG_DIR ||: RPM_BUILD_ROOT="/builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT" export RPM_BUILD_ROOT PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/lib64/pkgconfig:/usr/share/pkgconfig" export PKG_CONFIG_PATH CONFIG_SITE=${CONFIG_SITE:-NONE} export CONFIG_SITE Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.EUgFD7 + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + cd /builddir/build/BUILD/miniz-3.1.2-build + rm -rf miniz-3.1.2 + /usr/bin/rpmuncompress -x /builddir/build/SOURCES/miniz-3.1.2.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd miniz-3.1.2 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + echo 'Patch #0 (miniz-2.2.0-Examples-to-include-system-miniz.h.patch):' Patch #0 (miniz-2.2.0-Examples-to-include-system-miniz.h.patch): + /usr/bin/patch --no-backup-if-mismatch -f -p1 --fuzz=0 patching file examples/example1.c patching file examples/example2.c patching file examples/example3.c patching file examples/example4.c patching file examples/example5.c patching file examples/example6.c + dos2unix -k ChangeLog.md LICENSE dos2unix: converting file ChangeLog.md to Unix format... dos2unix: converting file LICENSE to Unix format... + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.7F9aJ6 + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd miniz-3.1.2 + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + /usr/bin/cmake -S . -B redhat-linux-build -G Ninja -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_FULL_SBINDIR:PATH=/usr/bin -DCMAKE_INSTALL_SBINDIR:PATH=bin -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value. Or, use the ... syntax to tell CMake that the project requires at least but has been updated to work with policies introduced by or earlier. -- The C compiler identification is GNU 16.1.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/gcc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Failed -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success -- The CXX compiler identification is GNU 16.1.1 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/g++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done (3.3s) -- Generating done (0.0s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_Fortran_FLAGS_RELEASE CMAKE_INSTALL_DO_STRIP LIB_INSTALL_DIR LIB_SUFFIX SHARE_INSTALL_PREFIX SYSCONF_INSTALL_DIR -- Build files have been written to: /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build + /usr/bin/cmake --build redhat-linux-build -j8 --verbose Change Dir: '/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build' Run Build Command(s): /usr/bin/ninja-build -v -j 8 [1/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example4.dir/examples/example4.c.o -MF CMakeFiles/example4.dir/examples/example4.c.o.d -o CMakeFiles/example4.dir/examples/example4.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example4.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example4.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example4.c - Uses tinfl.c to decompress a zlib stream in memory to an output file | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example4.c:1:1: note: (this will be reported only once per input file) [2/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example1.dir/examples/example1.c.o -MF CMakeFiles/example1.dir/examples/example1.c.o.d -o CMakeFiles/example1.dir/examples/example1.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example1.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example1.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example1.c - Demonstrates miniz.c's compress() and uncompress() functions (same as zlib's). | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example1.c:1:1: note: (this will be reported only once per input file) [3/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example2.dir/examples/example2.c.o -MF CMakeFiles/example2.dir/examples/example2.c.o.d -o CMakeFiles/example2.dir/examples/example2.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example2.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example2.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example2.c - Simple demonstration of miniz.c's ZIP archive API's. | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example2.c:1:1: note: (this will be reported only once per input file) [4/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example3.dir/examples/example3.c.o -MF CMakeFiles/example3.dir/examples/example3.c.o.d -o CMakeFiles/example3.dir/examples/example3.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example3.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example3.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example3.c - Demonstrates how to use miniz.c's deflate() and inflate() functions for simple file compression. | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example3.c:1:1: note: (this will be reported only once per input file) [5/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example6.dir/examples/example6.c.o -MF CMakeFiles/example6.dir/examples/example6.c.o.d -o CMakeFiles/example6.dir/examples/example6.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example6.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example6.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example6.c - Demonstrates how to miniz's PNG writer func | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example6.c:1:1: note: (this will be reported only once per input file) [6/21] /usr/bin/gcc -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -MD -MT CMakeFiles/example5.dir/examples/example5.c.o -MF CMakeFiles/example5.dir/examples/example5.c.o.d -o CMakeFiles/example5.dir/examples/example5.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example5.c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example5.c:1:1: warning: C++ style comments are not allowed in ISO C90 [-Wpedantic] 1 | // example5.c - Demonstrates how to use miniz.c's low-level tdefl_compress() and tinfl_inflate() API's for simple file to file compression/decompression. | ^ /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example5.c:1:1: note: (this will be reported only once per input file) [7/21] /usr/bin/gcc -D_GNU_SOURCE -Dminiz_EXPORTS -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -fPIC -fvisibility=hidden -MD -MT CMakeFiles/miniz.dir/miniz.c.o -MF CMakeFiles/miniz.dir/miniz.c.o.d -o CMakeFiles/miniz.dir/miniz.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/miniz.c [8/21] /usr/bin/gcc -D_GNU_SOURCE -Dminiz_EXPORTS -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -fPIC -fvisibility=hidden -MD -MT CMakeFiles/miniz.dir/miniz_tdef.c.o -MF CMakeFiles/miniz.dir/miniz_tdef.c.o.d -o CMakeFiles/miniz.dir/miniz_tdef.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/miniz_tdef.c [9/21] /usr/bin/gcc -D_GNU_SOURCE -Dminiz_EXPORTS -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -fPIC -fvisibility=hidden -MD -MT CMakeFiles/miniz.dir/miniz_tinfl.c.o -MF CMakeFiles/miniz.dir/miniz_tinfl.c.o.d -o CMakeFiles/miniz.dir/miniz_tinfl.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/miniz_tinfl.c [10/21] /usr/bin/gcc -D_GNU_SOURCE -Dminiz_EXPORTS -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -std=gnu90 -fPIC -fvisibility=hidden -MD -MT CMakeFiles/miniz.dir/miniz_zip.c.o -MF CMakeFiles/miniz.dir/miniz_zip.c.o.d -o CMakeFiles/miniz.dir/miniz_zip.c.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/miniz_zip.c [11/21] : && /usr/bin/gcc -fPIC -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -shared -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/miniz.dir/link.d -Wl,-soname,libminiz.so.3 -o libminiz.so.3.1.2 CMakeFiles/miniz.dir/miniz.c.o CMakeFiles/miniz.dir/miniz_zip.c.o CMakeFiles/miniz.dir/miniz_tinfl.c.o CMakeFiles/miniz.dir/miniz_tdef.c.o && : [12/21] /usr/bin/cmake -E cmake_symlink_library libminiz.so.3.1.2 libminiz.so.3 libminiz.so && : [13/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example1.dir/link.d CMakeFiles/example1.dir/examples/example1.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example1 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : [14/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example5.dir/link.d CMakeFiles/example5.dir/examples/example5.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example5 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : [15/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example4.dir/link.d CMakeFiles/example4.dir/examples/example4.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example4 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : [16/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example6.dir/link.d CMakeFiles/example6.dir/examples/example6.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example6 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 -lm && : [17/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example2.dir/link.d CMakeFiles/example2.dir/examples/example2.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example2 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : [18/21] : && /usr/bin/gcc -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wshadow -Wformat=2 -Wall -Wno-overlength-strings -pedantic -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/example3.dir/link.d CMakeFiles/example3.dir/examples/example3.c.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/example3 -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : [19/21] /usr/bin/g++ -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DNDEBUG -std=gnu++20 -MD -MT CMakeFiles/catch_tests.dir/tests/main.cpp.o -MF CMakeFiles/catch_tests.dir/tests/main.cpp.o.d -o CMakeFiles/catch_tests.dir/tests/main.cpp.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/tests/main.cpp [20/21] /usr/bin/g++ -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 -I/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DNDEBUG -std=gnu++20 -MD -MT CMakeFiles/catch_tests.dir/tests/catch_amalgamated.cpp.o -MF CMakeFiles/catch_tests.dir/tests/catch_amalgamated.cpp.o.d -o CMakeFiles/catch_tests.dir/tests/catch_amalgamated.cpp.o -c /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/tests/catch_amalgamated.cpp [21/21] : && /usr/bin/g++ -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DNDEBUG -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,--dependency-file=CMakeFiles/catch_tests.dir/link.d CMakeFiles/catch_tests.dir/tests/main.cpp.o CMakeFiles/catch_tests.dir/tests/catch_amalgamated.cpp.o -o /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin/catch_tests -Wl,-rpath,/builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/redhat-linux-build libminiz.so.3.1.2 && : + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.tcWLih + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + '[' /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT ++ dirname /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT + mkdir -p /builddir/build/BUILD/miniz-3.1.2-build + mkdir /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd miniz-3.1.2 + DESTDIR=/builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT + /usr/bin/cmake --install redhat-linux-build -- Install configuration: "Release" -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/pkgconfig/miniz.pc -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/libminiz.so.3.1.2 -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/libminiz.so.3 -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/libminiz.so -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/cmake/miniz/minizTargets.cmake -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/cmake/miniz/minizTargets-release.cmake -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/cmake/miniz/minizConfig.cmake -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/lib64/cmake/miniz/minizConfigVersion.cmake -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz.h -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz_common.h -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz_tdef.h -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz_tinfl.h -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz_zip.h -- Installing: /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/include/miniz/miniz_export.h + /usr/bin/find-debuginfo -j8 --strict-build-id -m -i --build-id-seed 3.1.2-2.fc45 --unique-debug-suffix -3.1.2-2.fc45.riscv64 --unique-debug-src-base miniz-3.1.2-2.fc45.riscv64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 --remove-section .gnu.build.attributes -S debugsourcefiles.list /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 find-debuginfo: starting Extracting debug info from 1 files DWARF-compressing 1 files sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. Creating .debug symlinks for symlinks to ELF files Copying sources found by 'debugedit -l' to /usr/src/debug/miniz-3.1.2-2.fc45.riscv64 find-debuginfo: done + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + COMPRESS='gzip -9 -n' + COMPRESS_EXT=.gz + /usr/lib/rpm/brp-compress + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j8 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-det --brp -j8 /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT Scanned 16 directories and 24 files, processed 0 inodes, 0 modified (0 replaced + 0 rewritten), 0 unsupported format, 0 errors + /usr/bin/linkdupes --brp /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr Scanned 15 directories and 24 files, considered 22 files, read 10 files, linked 5 files, 0 errors sum of sizes of linked files: 76989 bytes Reading /builddir/build/BUILD/miniz-3.1.2-build/SPECPARTS/rpm-debuginfo.specpart Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.oYafR8 + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS ~/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/bin ~/build/BUILD/miniz-3.1.2-build/miniz-3.1.2 + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd miniz-3.1.2 + pushd bin + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./catch_tests Randomness seeded to: 4088433479 =============================================================================== All tests passed (80 assertions in 3 test cases) + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example1 miniz.c version: 11.3.2 Compressed from 490 to 81 bytes Decompressed from 81 to 490 bytes Success. + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example2 miniz.c version: 11.3.2 Filename: "49.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "48.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "47.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "46.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "45.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "44.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "43.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "42.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "41.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "40.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "39.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "38.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "37.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "36.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "35.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "34.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "33.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "32.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "31.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "30.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "29.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 567, Is Dir: 0 Filename: "28.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "27.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "26.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "25.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "24.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "23.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "22.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "21.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "20.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 567, Is Dir: 0 Filename: "19.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "18.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "17.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "16.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "15.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "14.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "13.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "12.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "11.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 569, Is Dir: 0 Filename: "10.txt", Comment: "This is a comment", Uncompressed size: 972, Compressed size: 568, Is Dir: 0 Filename: "9.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "8.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "7.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "6.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "5.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "4.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "3.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "2.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "1.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 568, Is Dir: 0 Filename: "0.txt", Comment: "This is a comment", Uncompressed size: 971, Compressed size: 567, Is Dir: 0 Filename: "directory/", Comment: "no comment", Uncompressed size: 0, Compressed size: 0, Is Dir: 1 Successfully extracted file "0.txt", size 971 File data: "49 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 0" Successfully extracted file "1.txt", size 971 File data: "48 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 1" Successfully extracted file "2.txt", size 971 File data: "47 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 2" Successfully extracted file "3.txt", size 971 File data: "46 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 3" Successfully extracted file "4.txt", size 971 File data: "45 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 4" Successfully extracted file "5.txt", size 971 File data: "44 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 5" Successfully extracted file "6.txt", size 971 File data: "43 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 6" Successfully extracted file "7.txt", size 971 File data: "42 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 7" Successfully extracted file "8.txt", size 971 File data: "41 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 8" Successfully extracted file "9.txt", size 971 File data: "40 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 9" Successfully extracted file "10.txt", size 972 File data: "39 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 10" Successfully extracted file "11.txt", size 972 File data: "38 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 11" Successfully extracted file "12.txt", size 972 File data: "37 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 12" Successfully extracted file "13.txt", size 972 File data: "36 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 13" Successfully extracted file "14.txt", size 972 File data: "35 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 14" Successfully extracted file "15.txt", size 972 File data: "34 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 15" Successfully extracted file "16.txt", size 972 File data: "33 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 16" Successfully extracted file "17.txt", size 972 File data: "32 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 17" Successfully extracted file "18.txt", size 972 File data: "31 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 18" Successfully extracted file "19.txt", size 972 File data: "30 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 19" Successfully extracted file "20.txt", size 972 File data: "29 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 20" Successfully extracted file "21.txt", size 972 File data: "28 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 21" Successfully extracted file "22.txt", size 972 File data: "27 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 22" Successfully extracted file "23.txt", size 972 File data: "26 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 23" Successfully extracted file "24.txt", size 972 File data: "25 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 24" Successfully extracted file "25.txt", size 972 File data: "24 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 25" Successfully extracted file "26.txt", size 972 File data: "23 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 26" Successfully extracted file "27.txt", size 972 File data: "22 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 27" Successfully extracted file "28.txt", size 972 File data: "21 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 28" Successfully extracted file "29.txt", size 972 File data: "20 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 29" Successfully extracted file "30.txt", size 972 File data: "19 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 30" Successfully extracted file "31.txt", size 972 File data: "18 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 31" Successfully extracted file "32.txt", size 972 File data: "17 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 32" Successfully extracted file "33.txt", size 972 File data: "16 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 33" Successfully extracted file "34.txt", size 972 File data: "15 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 34" Successfully extracted file "35.txt", size 972 File data: "14 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 35" Successfully extracted file "36.txt", size 972 File data: "13 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 36" Successfully extracted file "37.txt", size 972 File data: "12 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 37" Successfully extracted file "38.txt", size 972 File data: "11 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 38" Successfully extracted file "39.txt", size 972 File data: "10 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 39" Successfully extracted file "40.txt", size 971 File data: "9 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 40" Successfully extracted file "41.txt", size 971 File data: "8 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 41" Successfully extracted file "42.txt", size 971 File data: "7 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 42" Successfully extracted file "43.txt", size 971 File data: "6 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 43" Successfully extracted file "44.txt", size 971 File data: "5 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 44" Successfully extracted file "45.txt", size 971 File data: "4 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 45" Successfully extracted file "46.txt", size 971 File data: "3 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 46" Successfully extracted file "47.txt", size 971 File data: "2 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 47" Successfully extracted file "48.txt", size 971 File data: "1 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 48" Successfully extracted file "49.txt", size 971 File data: "0 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 49" Successfully extracted file "0.txt", size 971 File data: "49 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 0" Successfully extracted file "1.txt", size 971 File data: "48 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 1" Successfully extracted file "2.txt", size 971 File data: "47 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 2" Successfully extracted file "3.txt", size 971 File data: "46 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 3" Successfully extracted file "4.txt", size 971 File data: "45 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 4" Successfully extracted file "5.txt", size 971 File data: "44 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 5" Successfully extracted file "6.txt", size 971 File data: "43 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 6" Successfully extracted file "7.txt", size 971 File data: "42 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 7" Successfully extracted file "8.txt", size 971 File data: "41 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 8" Successfully extracted file "9.txt", size 971 File data: "40 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 9" Successfully extracted file "10.txt", size 972 File data: "39 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 10" Successfully extracted file "11.txt", size 972 File data: "38 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 11" Successfully extracted file "12.txt", size 972 File data: "37 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 12" Successfully extracted file "13.txt", size 972 File data: "36 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 13" Successfully extracted file "14.txt", size 972 File data: "35 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 14" Successfully extracted file "15.txt", size 972 File data: "34 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 15" Successfully extracted file "16.txt", size 972 File data: "33 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 16" Successfully extracted file "17.txt", size 972 File data: "32 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 17" Successfully extracted file "18.txt", size 972 File data: "31 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 18" Successfully extracted file "19.txt", size 972 File data: "30 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 19" Successfully extracted file "20.txt", size 972 File data: "29 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 20" Successfully extracted file "21.txt", size 972 File data: "28 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 21" Successfully extracted file "22.txt", size 972 File data: "27 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 22" Successfully extracted file "23.txt", size 972 File data: "26 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 23" Successfully extracted file "24.txt", size 972 File data: "25 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 24" Successfully extracted file "25.txt", size 972 File data: "24 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 25" Successfully extracted file "26.txt", size 972 File data: "23 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 26" Successfully extracted file "27.txt", size 972 File data: "22 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 27" Successfully extracted file "28.txt", size 972 File data: "21 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 28" Successfully extracted file "29.txt", size 972 File data: "20 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 29" Successfully extracted file "30.txt", size 972 File data: "19 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 30" Successfully extracted file "31.txt", size 972 File data: "18 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 31" Successfully extracted file "32.txt", size 972 File data: "17 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 32" Successfully extracted file "33.txt", size 972 File data: "16 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 33" Successfully extracted file "34.txt", size 972 File data: "15 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 34" Successfully extracted file "35.txt", size 972 File data: "14 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 35" Successfully extracted file "36.txt", size 972 File data: "13 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 36" Successfully extracted file "37.txt", size 972 File data: "12 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 37" Successfully extracted file "38.txt", size 972 File data: "11 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 38" Successfully extracted file "39.txt", size 972 File data: "10 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 39" Successfully extracted file "40.txt", size 971 File data: "9 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 40" Successfully extracted file "41.txt", size 971 File data: "8 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 41" Successfully extracted file "42.txt", size 971 File data: "7 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 42" Successfully extracted file "43.txt", size 971 File data: "6 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 43" Successfully extracted file "44.txt", size 971 File data: "5 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 44" Successfully extracted file "45.txt", size 971 File data: "4 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 45" Successfully extracted file "46.txt", size 971 File data: "3 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 46" Successfully extracted file "47.txt", size 971 File data: "2 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 47" Successfully extracted file "48.txt", size 971 File data: "1 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 48" Successfully extracted file "49.txt", size 971 File data: "0 MISSION CONTROL I wouldn't worry too much about the computer. First of all, there is still a chance that he is right, despite your tests, andif it should happen again, we suggest eliminating this possibility by allowing the unit to remain in place and seeing whether or not itactually fails. If the computer should turn out to be wrong, the situation is still not alarming. The type of obsessional error he may beguilty of is not unknown among the latest generation of HAL 9000 computers. It has almost always revolved around a single detail, such asthe one you have described, and it has never interfered with the integrity or reliability of the computer's performance in other areas.No one is certain of the cause of this kind of malfunctioning. It may be over-programming, but it could also be any number of reasons. In anyevent, it is somewhat analogous to human neurotic behavior. Does this answer your query? Zero-five-three-Zero, MC, transmission concluded. 49" Success. + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example3 c ../readme.md readme.md.z + LD_LIBRARY_PATH=../redhat-linux-build + ./example3 d readme.md.z readme.md + cmp ../readme.md readme.md miniz.c version: 11.3.2 Mode: c, Level: 9 Input File: "../readme.md" Output File: "readme.md.z" Input file size: 4784 Total input bytes: 4784 Total output bytes: 2333 Success. miniz.c version: 11.3.2 Mode: d, Level: 9 Input File: "readme.md.z" Output File: "readme.md" Input file size: 2333 Total input bytes: 2333 Total output bytes: 4784 Success. + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example4 readme.md.z readme.md Input file size: 2333 Total input bytes: 2333 Total output bytes: 4784 Success. + cmp ../readme.md readme.md + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example5 c ../readme.md readme.md.z miniz.c example5 (demonstrates tinfl/tdefl) Mode: c, Level: 9 Input File: "../readme.md" Output File: "readme.md.z" Input file size: 4784 Total input bytes: 4784 Total output bytes: 2333 Success. + LD_LIBRARY_PATH=../redhat-linux-build + ./example5 d readme.md.z readme.md miniz.c example5 (demonstrates tinfl/tdefl) Mode: d, Level: 9 Input File: "readme.md.z" Output File: "readme.md" Input file size: 2333 Total input bytes: 2333 Total output bytes: 4784 Success. + cmp ../readme.md readme.md + for EXAMPLE in * + case "$EXAMPLE" in + LD_LIBRARY_PATH=../redhat-linux-build + ./example6 Wrote mandelbrot.png + RPM_EC=0 ++ jobs -p + exit 0 Processing files: miniz-3.1.2-2.fc45.riscv64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.b1vrSW + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + cd miniz-3.1.2 + DOCDIR=/builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/ChangeLog.md /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/readme.md /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz + RPM_EC=0 ++ jobs -p Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.G6pZn5 + exit 0 + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + cd miniz-3.1.2 + LICENSEDIR=/builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/licenses/miniz + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/licenses/miniz + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/LICENSE /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/licenses/miniz + RPM_EC=0 ++ jobs -p + exit 0 Provides: libminiz.so.3()(64bit) miniz = 3.1.2-2.fc45 miniz(riscv-64) = 3.1.2-2.fc45 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: ld-linux-riscv64-lp64d.so.1()(64bit) ld-linux-riscv64-lp64d.so.1(GLIBC_2.27)(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.27)(64bit) libc.so.6(GLIBC_2.33)(64bit) rtld(GNU_HASH) Processing files: miniz-devel-3.1.2-2.fc45.riscv64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.LfgF28 + umask 022 + cd /builddir/build/BUILD/miniz-3.1.2-build + cd miniz-3.1.2 + DOCDIR=/builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example1.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example2.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example3.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example4.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example5.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + cp -pr /builddir/build/BUILD/miniz-3.1.2-build/miniz-3.1.2/examples/example6.c /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT/usr/share/doc/miniz-devel + RPM_EC=0 ++ jobs -p + exit 0 Provides: cmake(miniz) = 3.1.2 miniz-devel = 3.1.2-2.fc45 miniz-devel(riscv-64) = 3.1.2-2.fc45 pkgconfig(miniz) = 3.1.2 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: /usr/bin/pkg-config cmake-filesystem(riscv-64) libminiz.so.3()(64bit) Processing files: miniz-debugsource-3.1.2-2.fc45.riscv64 Provides: miniz-debugsource = 3.1.2-2.fc45 miniz-debugsource(riscv-64) = 3.1.2-2.fc45 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Processing files: miniz-debuginfo-3.1.2-2.fc45.riscv64 Provides: debuginfo(build-id) = 46164cb1b8f316e4fc67a40736e07496da93dcaf libminiz.so.3.1.2-3.1.2-2.fc45.riscv64.debug()(64bit) miniz-debuginfo = 3.1.2-2.fc45 miniz-debuginfo(riscv-64) = 3.1.2-2.fc45 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Recommends: miniz-debugsource(riscv-64) = 3.1.2-2.fc45 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/miniz-3.1.2-build/BUILDROOT Wrote: /builddir/build/RPMS/miniz-3.1.2-2.fc45.riscv64.rpm Wrote: /builddir/build/RPMS/miniz-devel-3.1.2-2.fc45.riscv64.rpm Wrote: /builddir/build/RPMS/miniz-debuginfo-3.1.2-2.fc45.riscv64.rpm Wrote: /builddir/build/RPMS/miniz-debugsource-3.1.2-2.fc45.riscv64.rpm Child return code was: 0