Hello GNU cpio Team, I am investigating a compatibility issue with GNU cpio 2.15 on Windows and would like to report the behavior for your review. Environment
- OS: Windows - GNU cpio version: 2.15 - Executable: C:\Program Files (x86)\GnuWin32\bin\cpio.exe - Archive format: crc Command The archive is generated using: cpio -ov -H crc -F test.cpio < list.txt Input files The working directory contains the following files: DatasetHeader.pbuf ProfileVP_001_TestProfileSTP.pbuf input1.pbuf The contents of list.txt are: DatasetHeader.pbuf ProfileVP_001_TestProfileSTP.pbuf input1.pbuf All of these files exist in the current working directory and can be accessed normally from Windows CMD. Actual behavior with GNU cpio 2.15 Running: cpio -ov -H crc -F test.cpio < list.txt produces: Cannot stat: No such file or directory Cannot stat: No such file or directory input1.pbuf 1 block The behavior is reproducible. Comparison with GNU cpio 2.6.2 The same command, using the existing GNU cpio 2.6.2 Windows executable and the same type of multi-file input list, successfully creates the CPIO archive. Therefore, we are observing different behavior between the two versions when processing filenames supplied through standard input. Additional testing We also tested the behavior with a simple filename rather than the dataset files. For example: echo a.txt > list.txt where a.txt exists in the current directory, followed by: cpio -ov -H crc -F test.cpio < list.txt The GNU cpio 2.15 executable still reports: Cannot stat: No such file or directory We also tested absolute paths and --absolute-filenames, but the issue remained. Expected behavior For an input list such as: DatasetHeader.pbuf ProfileVP_001_TestProfileSTP.pbuf input1.pbuf all existing files should be resolved and included in the output CPIO archive. Request If this is not a CPIO 2.15 issue and the command/invocation is incorrect, could you please provide the exact Windows CMD command that should be used to create a CRC-format CPIO archive containing multiple files from an input list? Regards, Swapnil Thitame
