[Bug 242630] [PowerPC] lang/ruby26 build fails on rb_mjit_min_header-2.6.5.h (FreeBSD 12.1-RELEASE-p1)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Dec 29 22:45:03 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242630

--- Comment #7 from Tibikuera <tibikuera at yahoo.ca> ---
(In reply to Tibikuera from comment #3)

I ended up trying the following (as suggested in the web page
http://www.bitwizard.nl/sig11/) and since after the "dd" command it did stop at
the same place, this is not supposed to be a hardware issue:

"First lets make sure it is the hardware that is causing your trouble. When the
"make" stops, simply type "make" again. If it compiles a few more files before
stopping, it must be hardware that is causing you troubles. If it immediately
stops again (i.e. scans a few directories with "nothing to be done for xxxx"
before bombing at exactly the same place), try

   dd if=/dev/HARD_DISK of=/dev/null bs=1024k count=MEGS

Change HARD_DISK to "hda" to the name of your harddisk (e.g. hda or sda. Or use
"df ."). Change the MEGS to the number of megabytes of main memory that you
have. This will cause the first several megabytes of your harddisk to be read
from disk, forcing the C source files and the gcc binary to be reread from disk
the next time you run it. Now type make again. If it still stops in the same
place I'm starting to wonder if you're reading the right FAQ, as it is starting
to look like a software problem after all.... Take a peek at the "what are the
other possibilities" question..... If without this "dd" command the compiler
keeps on stopping at the same place, but moves to another place after you use
the "dd" you definitely have a disk->ram transfer problem."

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ppc mailing list