From owner-freebsd-ppc@freebsd.org Sun Dec 29 22:45:03 2019 Return-Path: Delivered-To: freebsd-ppc@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 871541ED4EA for ; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47mFxq34mCz4DWG for ; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 610EC103DC; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 423D2103DB for ; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47mFxq0GNLz4DW9 for ; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 04272207DE for ; Sun, 29 Dec 2019 22:45:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xBTMj2JH026551 for ; Sun, 29 Dec 2019 22:45:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xBTMj2Um026550 for powerpc@FreeBSD.org; Sun, 29 Dec 2019 22:45:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 242630] [PowerPC] lang/ruby26 build fails on rb_mjit_min_header-2.6.5.h (FreeBSD 12.1-RELEASE-p1) Date: Sun, 29 Dec 2019 22:45:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tibikuera@yahoo.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ruby@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Dec 2019 22:45:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242630 --- Comment #7 from Tibikuera --- (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 sto= p 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 bef= ore stopping, it must be hardware that is causing you troubles. If it immediate= ly 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=3D/dev/HARD_DISK of=3D/dev/null bs=3D1024k count=3DMEGS 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 re= ad 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 star= ting 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 u= se the "dd" you definitely have a disk->ram transfer problem." --=20 You are receiving this mail because: You are on the CC list for the bug.=