On 2018-Jun-18, at 4:08 PM, Bryan Drewery <bdrewery at FreeBSD.org> wrote: > On 6/18/2018 3:27 PM, Li-Wen Hsu wrote: >> ranlib -D libpcap.a >> ranlib: fatal: Failed to open 'libpcap.a' > > Where is this error even coming from? It's not in the usr.bin/ar code > and ranlib does not cause it. > > # ranlib -D uh > ranlib: warning: uh: no such file A more complete sequence is (with some other text mixed in, as in where I got the text from on ci.freebsd.org): --- libvgl.a --- building static vgl library ar -crD libvgl.a `NM='nm' NMFLAGS='' lorder main.o simple.o bitmap.o text.o mouse.o keyboard.o | tsort -q` --- all_subdir_lib/libsysdecode --- ranlib -D libsysdecode.a --- all_subdir_lib/libvgl --- ranlib -D libvgl.a ranlib: fatal: Failed to open 'libvgl.a' --- all_subdir_lib/libsysdecode --- ranlib: fatal: Failed to open 'libsysdecode.a' --- all_subdir_lib/libvgl --- *** [libvgl.a] Error code 70 So, in essence, ar -crD libvgl.a `NM='nm' NMFLAGS='' lorder main.o simple.o bitmap.o text.o mouse.o keyboard.o | tsort -q` ranlib -D libvgl.a ranlib: fatal: Failed to open 'libvgl.a' It is not obvious to me that the "Failed to open" means that there was "no such file". Might there be some other form of "Failed to open" for a file that does exist from the ar at least having created its output .a file? === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)Received on Mon Jun 18 2018 - 23:13:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC