Re: c++: error: unknown argument: '-fno-ret-protector' when compiling CURRENT userland
Stuart, thank you so much for the info! > Your compiler is old (from 6.3 at a quick guess based on the date), > you either need to install a snapshot and move from there, or follow > http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/www/faq/current.html?rev=1.918=text/html#r20180606 I've been following this "usual" version of the above document only: https://www.openbsd.org/faq/current.html There, it doesn't say a thing about the change in the compiler. Human error? Thanks again, Stuart! Yours, Jyri
c++: error: unknown argument: '-fno-ret-protector' when compiling CURRENT userland
Hi! Been following CURRENT for quite a while, experiencing zero problems. However, now there's a problem compiling the 64-bit CURRENT on two servers -- one virtual, one full iron. OpenBSD 6.3-current (GENERIC.MP) #19: Thu Jul 5 12:23:55 UTC 2018 ***@***.turvamies.fi:/sys/arch/amd64/compile/GENERIC.MP # cd /usr/src # make obj => everyhing good # make build => results in: ... ===> gnu/usr.bin/clang ===> gnu/usr.bin/clang/include/llvm/Config printf "LLVM_ASM_PARSER(X86)\n#undef LLVM_ASM_PARSER\n" >AsmParsers.def printf "LLVM_ASM_PRINTER(X86)\n#undef LLVM_ASM_PRINTER\n" >AsmPrinters.def printf "LLVM_DISASSEMBLER(X86)\n#undef LLVM_DISASSEMBLER\n" >Disassemblers.def printf "LLVM_TARGET(X86)\n#undef LLVM_TARGET\n" >Targets.def ===> gnu/usr.bin/clang/libLLVMSupport c++ -O2 -pipe -std=c++11 -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wdelete-non-virtual-dtor -Wno-comment -fno-pie -MD -MP -I/usr/src/gnu/usr.bin/clang/libLLVMSupport/../../../llvm/include/llvm/Support -I/usr/src/gnu/usr.bin/clang/libLLVMSupport/../../../llvm/include -I/usr/src/gnu/usr.bin/clang/libLLVMSupport/../include -I/usr/src/gnu/usr.bin/clang/libLLVMSupport/obj -I/usr/src/gnu/usr.bin/clang/libLLVMSupport/obj/../include -DNDEBUG -fno-ret-protector -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE="amd64-unknown-openbsd6.3" -DLLVM_HOST_TRIPLE="amd64-unknown-openbsd6.3" -DLLVM_PREFIX="/usr" -DLLVM_NATIVE_ARCH="X86" -DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser -DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter -DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler -DLLVM_NATIVE_TARGET=LLVMInitializeX86Target -DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo -DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -c /usr/src/gnu/usr.bin/clang/libLLVMSupport/../../../llvm/lib/Support/APFloat.cpp -o APFloat.o c++: error: unknown argument: '-fno-ret-protector' *** Error 1 in gnu/usr.bin/clang/libLLVMSupport (:69 'APFloat.o': @c++ -O2 -pipe -std=c++11 -fvisibility-inlines-hidden -fno-ex...) *** Error 1 in gnu/usr.bin/clang (:48 'all') *** Error 1 in gnu/usr.bin (:48 'all') *** Error 1 in gnu (:48 'all') *** Error 1 in . (:48 'all') *** Error 1 in . (Makefile:95 'do-build') *** Error 1 in /usr/src (Makefile:74 'build') # c++ -v OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0) Target: amd64-unknown-openbsd6.3 Thread model: posix InstalledDir: /usr/bin # ls -la /usr/bin/c++* -r-xr-xr-x 6 root bin 46453496 Apr 25 10:10 /usr/bin/c++ -r-xr-xr-x 1 root bin 10008 Apr 25 10:10 /usr/bin/c++filt # /usr/bin/c++ -v OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0) Target: amd64-unknown-openbsd6.3 Thread model: posix InstalledDir: /usr/bin Can't figure out what's wrong. Do I have an outdated version of c++ in the system for some reason? Yours, Jyri -- jyri.hov...@iki.fi +358-404-177133 (24/7)
Preventing screen capturing in Xenocara?
Dear everyone, the possibility to grab the contents of the screen is one of the many design level security / privacy issues all major operating systems suffer from. The APIs of Windows, Android, iOS etc. allow capturing the screen without informing the user about it in any way. It seems (quite obvious) to me that OpenBSD / Xenocara do not currently have mechanisms to limit which processes / applications can access the contents of the screen. I can already feel the storm brewing but I must ask: have there been any plans regarding such a feature? Yours, Jyri -- jyri.hov...@iki.fi +358-404-177133 (24/7)
