Re: Call for Foundation-supported Project Ideas

On Mon, Nov 29, 2021 at 2:57 AM Jason Bacon <bacon4000@gmail.com> wrote:

> On 11/28/21 16:07, Steve Kargl wrote:
> >
> > %  ps -ww -p 77387
> >    PID TT  STAT     TIME COMMAND
> > 77387  2  R    40:34.67 c++ -target x86_64-unknown-freebsd14.0
> --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -g -O1 -fno-common
> -I/usr/obj/usr/src/amd64.amd64/lib/clang/libclang
> -I/usr/obj/usr/src/amd64.amd64/lib/clang/libllvm
> -I/usr/src/contrib/llvm-project/clang/lib/Basic
> -I/usr/src/contrib/llvm-project/clang/lib/Driver
> -I/usr/src/contrib/llvm-project/clang/include -DCLANG_ENABLE_ARCMT
> -DCLANG_ENABLE_STATIC_ANALYZER -I/usr/src/lib/clang/include
> -I/usr/src/contrib/llvm-project/llvm/include -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -DHAVE_VCS_VERSION_INC
> -DLLVM_DEFAULT_TARGET_TRIPLE="x86_64-unknown-freebsd14.0"
> -DLLVM_HOST_TRIPLE="x86_64-unknown-freebsd14.0" -DDEFAULT_SYSROOT=""
> -DLLVM_TARGET_ENABLE_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 -ffunction-sections
> -fdata-sections -Wno-format-zero-length -fstack-protector-strong
> -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable
> -Wno-error=unused-but-set-variable -Wno-tautological-compare
> -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function
> -Wno-enum-conversion -Wno-unused-local-typedef
> -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum
> -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments
> -fno-exceptions -fno-rtti -std=c++14 -stdlib=libc++ -Wno-c++11-extensions
> -c /usr/src/contrib/llvm-project/clang/lib/Sema/SemaExpr.cpp -o
> Sema/SemaExpr.o
> >
> > 40 minutes for 1 file with many exceeding 30 minutes seems a tad bit
> > excessive.
>
> I would bet you have a hardware issue.  I've never seen a buildworld
> take more than a few hours and that was on some very old hardware.
>
>

I would support the above idea because (1)
sometimes cables of HDD units are becoming corroded and causing delays (
repetitions of disk read tries ) ,
(2) HHD unit is dying and again it is causing a large number of reread
tries
(3) It may be useful to check memory chips by memory test programs

There may be other hardware issues , but I am not able to suggest a good
solution other
than ( if you have another computer , please use it for comparison ) .


Some compilation parameters may cause trouble .

If you are using an NFS server , its parameters for definition of it may
cause very long delays .




Mehmet Erol Sanliturk




> --
> All wars are civil wars, because all men are brothers ... Each one owes
> infinitely more to the human race than to the particular country in
> which he was born.
>                  -- Francois Fenelon
>