https://llvm.org/bugs/show_bug.cgi?id=31389
Bug ID: 31389
Summary: llvm-ar xo fails when setting file modification
timestamp when running on a FAT32 filesystem
Product: tools
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: llvm-ar
Assignee: unassignedb...@nondot.org
Reporter: juj...@gmail.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Created attachment 17758
--> https://llvm.org/bugs/attachment.cgi?id=17758&action=edit
test case
Testing on a Windows 10 system:
STR:
1. Download and copy the attached libz.a to a directory on a FAT32 filesystem.
2. Run 'llvm-ar xo libz.a adler32.c.o' on the file.
Observed:
The tool fails with the error message:
llvm-ar: The parameter is incorrect.
but curiously, file adler32.c.o does appear in the directory, just its file
modification timestamp was not set.
However, if one copies the file over to a NTFS partition and reissues the
command, it succeeds and the file adler32.c.o does get the original timestamp.
Also, if one issues the command 'llvm-ar x libz.a adler32.c.o' instead (i.e.
'x' instead of 'xo'), the error is avoided (but timestamp is not set)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
