Created attachment 547760 [details] build.log llvm-7.0.0 falls over with the above error as well as a segmentation fault. As this is a new system,mobo abm350-m with a ryzen5-2200g cpu,I suspect the segmentation fault is due to ninja, having said that I have increased the ram from 8g to 16G,but the problem persists.
Created attachment 547762 [details] emerge info ryzen5
Comment on attachment 547760 [details] build.log Perhaps you should upload the file instead of the local path to the file.
(In reply to Jeroen Roovers from comment #2) > Comment on attachment 547760 [details] > build.log > > Perhaps you should upload the file instead of the local path to the file. Yeah that would be nice,but that particular machine is offline,pending diagnosis & I don't have a copy available on a usb stik.
Created attachment 547956 [details] build.log for ryzen5 It is possible I have a faulty cpu,which is being checked tomorrow (thurs)
(In reply to Geoff Madden from comment #4) > It is possible I have a faulty cpu,which is being checked tomorrow (thurs) Were you able to test your CPU and memory?
(In reply to Mike Gilbert from comment #5) > (In reply to Geoff Madden from comment #4) > > It is possible I have a faulty cpu,which is being checked tomorrow (thurs) > > Were you able to test your CPU and memory? Yep, though I'm not all that impressed with the ryzen's performance in some areas it turned out to be a misinstalled mem card with that fixed and a proper designation for the cpu (I had it set at athlon64,changed to native)and compiling is much simpler. The hassle with the mem slots is that there is only one locking bar,& with the movement of the case it came loose.
Ah, thanks for confirming; that saves me a lot of head-scratching!
