tsort: pledge: invalid agument (building -current)

My previous update to -current was December 24th, and after building the release, checkflist told me that I had something different in a man entry somewhere. Just one line of output, and I decided maybe one line was minimal enough output. (The FAQ says it should be "minimal".) First time

Re: tsort: pledge: invalid agument (building -current)

> From a compiler command line that gets its ouput piped to tsort -q, I'm > getting > > tsort: pledge: invalid agument > cc: no input files > *** Error 1 in lib/libcrypto/crypto (:212 > 'libcrypto.so.37.8') > *** Error 1 in lib/libcrypto (:48 'all') > *** Error 1 in lib

Re: tsort: pledge: invalid agument (building -current)

i ran into this myself the other day. you already got good advice, so i will just make one comment. On Sat, 9 Jan 2016 18:54:22 +0900 Joel Rees wrote: > Do I need to backup my data, wipe the OS, and re-install from a snapshot > kernel? > it's unlikely you will ever have

Re: tsort: pledge: invalid agument (building -current)

On Sat, Jan 9, 2016 at 7:09 PM, Theo Buehler wrote: >> From a compiler command line that gets its ouput piped to tsort -q, I'm >> getting >> >> tsort: pledge: invalid agument >> cc: no input files >> *** Error 1 in lib/libcrypto/crypto (:212 >>