From owner-freebsd-arm@freebsd.org Sun Oct 8 00:27:46 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41E1BE45E68 for ; Sun, 8 Oct 2017 00:27:46 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-18.reflexion.net [208.70.210.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89ACB1C49 for ; Sun, 8 Oct 2017 00:27:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 31093 invoked from network); 8 Oct 2017 00:27:43 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 8 Oct 2017 00:27:43 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 07 Oct 2017 20:27:43 -0400 (EDT) Received: (qmail 15106 invoked from network); 8 Oct 2017 00:27:43 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Oct 2017 00:27:43 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id C1A9CEC8936; Sat, 7 Oct 2017 17:27:42 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: armv7, building p7zip and -fPIC From: Mark Millard In-Reply-To: <20171007214849.GB22150@lonesome.com> Date: Sat, 7 Oct 2017 17:27:42 -0700 Cc: Ian Lepore , freebsd-arm Content-Transfer-Encoding: 7bit Message-Id: <29DA467B-BD24-4E1A-B3CC-E1F4BD107DA4@dsl-only.net> References: <1507403387.86205.286.camel@freebsd.org> <20171007214849.GB22150@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 00:27:46 -0000 On 2017-Oct-7, at 2:48 PM, Mark Linimon wrote: > On Sat, Oct 07, 2017 at 01:09:47PM -0600, Ian Lepore wrote: >> This is really not just an armv7-only thing, the -fPIC flag should >> always be used. > > OK, I'm going to admit some ignorance and prepare to take my beating. > > The last time I tried to pepper some -fPIC flags around without knowing > what I was doing, I was told (in no uncertain terms) that I didn't know > what I was doing. While this was true I wasn't happy with the way I was > told :-) > > So can you please provide a "-fPIC for dummies" summary? I'll add it to > the wiki. > > (In my old embedded systems days, we didn't need all this fancy stuff; > you just stuffed your statically-linked result in the 64KB EPROM and you > were done.) Here is my understanding of a recent exchange for this subject area: If any architecture needs -fPIC then then target all of them doing so. In order of priority: A) If the original materials have a defined way to cause -fPIC use that instead of explicitly using CFLAGS+= -fPIC style. B) Otherwise use CFLAGS+= -fPIC style. An example of (A) was audio/liba52 that uses (an internal?) libtool and had used libtool's -prefer-non-pic . Such is now removed via: post-patch: @${REINPLACE_CMD} '/-prefer-non-pic/d' ${WRKSRC}/configure instead of separately using CFLAGS+= -fPIC . (There was the possibility of using -prefer-pic instead. I'm unsure of the tradeoffs/distinctions vs. what was done.) The above wording does not deal with -fpic vs. -fPIC or possibly other distinctions that might sometimes be involved. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Oct 8 06:38:10 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A83D2E29AA3 for ; Sun, 8 Oct 2017 06:38:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A4F76F6AA for ; Sun, 8 Oct 2017 06:38:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22d.google.com with SMTP id k70so2688925itk.0 for ; Sat, 07 Oct 2017 23:38:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2Y35SxkP/RuCvQxCqAbjHvgvYsy25gVHPD7LsOMQrKI=; b=X1WIzXC41eG2r1+y1KAb20eIkUysGLwGxR9ntJSYVTjR2FjYa08ERhmEyW/GGQLbkz dj6/v6A3U5OKHtUmnh2EnlIKeBc+PcGn9pVgTfm/u8wd87WZBKvyTYSkAh+CwaqafdYY MMQL0LupRWZSYxuyjkISYYaQsl2Qzo2CscKP3/wp3efopUlhFmiYrRnbqy673cvHUA89 z4GTPOpivrQptlPl78dWylq6TIZdLnEnbyxUDqagqdTKDrVTijtDlAHiQ6Y5Y9dqHLTx tQ8NLpiK6xJE5LAfLg9KrjYU5RsTzR7aOM4+UKl/n7GU/xCamJPruLMZDcjhAq8EI6kk pf0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2Y35SxkP/RuCvQxCqAbjHvgvYsy25gVHPD7LsOMQrKI=; b=WlzRzLkOWBrNSVfH9Xa+WCYEy1fg/PWX6Yfo0WsSscXme2VUBLV4DQaGTpjiqkkn6m YlSsSaknsZF1tr4hGI7nR0XGPtbRl3y12QOLN+f/bhpbtATdoqqrElh8ItPiUZg3bEM/ Ugs9ar/uupC+0d9VAM+yl1rit2vcaI2TLiMVf1d294PKoU57JY1qE0wTlNHhmI3cL5C2 7ODXJSqiIZ6Ja4e+zGlmsX3f8LMX5G/9rbLYce+TQO4YHm0JuZM1U0E+KM+sfcZLbwNy MMcFaYWBGyQLO3tMtwoEmZbMPsz1XlW2YMxPJSlSOrddgPhBXo9iz5gmYZWLki3ZTM54 CCoA== X-Gm-Message-State: AMCzsaUg+69EfRIuAH5pj46B32HX6YOsyz/sMnlZQRwbaDnxKE89KqLx HRulFPMuTD/tfOQA+plnkcy5RYbFsef+9gGAlvVp1A== X-Google-Smtp-Source: AOwi7QDRk+t1S4G4NwueS9/moOgRxMsxE0LXU4ApVnkwMCAonIapkptROfdD9ekAoD95TJbcxPnYA3FmlprQGPTs+hI= X-Received: by 10.36.190.138 with SMTP id i132mr9846546itf.15.1507444688785; Sat, 07 Oct 2017 23:38:08 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Sat, 7 Oct 2017 23:38:07 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:43b:1393:6fda:6aaa] In-Reply-To: <20171008053812.GA23271@lonesome.com> References: <1507403387.86205.286.camel@freebsd.org> <20171007214326.GA22150@lonesome.com> <1507416341.86205.291.camel@freebsd.org> <20171008053812.GA23271@lonesome.com> From: Warner Losh Date: Sat, 7 Oct 2017 23:38:07 -0700 X-Google-Sender-Auth: nmkCniO3eurT86IH_PCuIu8x008 Message-ID: Subject: Re: armv7, building p7zip and -fPIC To: Mark Linimon Cc: Ian Lepore , freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 06:38:10 -0000 On Sat, Oct 7, 2017 at 10:38 PM, Mark Linimon wrote: > On Sat, Oct 07, 2017 at 04:45:41PM -0600, Ian Lepore wrote: > > Not necessarily. There probably aren't too many people building ports > > for arm (v4/v5) > > Well, I had been told that the string "arm" had no meaning, so had > been ripping them out of ports. > > So now I need to undo a great deal of work. > Correct. The string 'arm' does have meaning. And always has since we got an arm port. Warner From owner-freebsd-arm@freebsd.org Sun Oct 8 05:38:15 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3BE1E27EBD for ; Sun, 8 Oct 2017 05:38:15 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A11822A1F; Sun, 8 Oct 2017 05:38:15 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 1C9AAAF1; Sun, 8 Oct 2017 00:38:14 -0500 (CDT) Date: Sun, 8 Oct 2017 00:38:13 -0500 From: Mark Linimon To: Ian Lepore Cc: Warner Losh , freebsd-arm Subject: Re: armv7, building p7zip and -fPIC Message-ID: <20171008053812.GA23271@lonesome.com> References: <1507403387.86205.286.camel@freebsd.org> <20171007214326.GA22150@lonesome.com> <1507416341.86205.291.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1507416341.86205.291.camel@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 05:38:16 -0000 On Sat, Oct 07, 2017 at 04:45:41PM -0600, Ian Lepore wrote: > Not necessarily. There probably aren't too many people building ports > for arm (v4/v5) Well, I had been told that the string "arm" had no meaning, so had been ripping them out of ports. So now I need to undo a great deal of work. mcl From owner-freebsd-arm@freebsd.org Sun Oct 8 06:26:33 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C35F6E293FA for ; Sun, 8 Oct 2017 06:26:33 +0000 (UTC) (envelope-from noname.esst@yahoo.com) Received: from sonic310-20.consmr.mail.gq1.yahoo.com (sonic310-20.consmr.mail.gq1.yahoo.com [98.137.69.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 710666CFD2 for ; Sun, 8 Oct 2017 06:26:32 +0000 (UTC) (envelope-from noname.esst@yahoo.com) X-YMail-OSG: KaclTk4VM1nBzcKImlSXvNG5IkMUo0IJaXrABxVDO5uCGww.wLdw07invjhikWc mVrqpRGzwmmph_vYeYMHJTgxTzwXUfoWOF6pPhaCs395dm0qknRxn8QeIdOpxpoWfMFJyvNCUCgt cNpxeQt37fnmpRJXP38nkCrzPV4KCtzfwlycuiXYZW5T2ZvJ6rZqJ9F8QZwwLzBgUqeyGwqSC.gZ 9w0zUtbiI8YpJ0J7YEXKl4NC791fZRKIlP55RtaLFUabL4Rd0gZ8Mv6GOuTGWY5U6PA5c8671VkE qGDxWuQIsCS93gni26kdv.67jCAm8Q8K42hyt2kodF1sMXl.Y8TgNFDihSuZ4dN7uRWMGYx95.XE FVS8WI6R9Pn4PteZ13yvkKG.8hfM3FkbVgqfoenMBi_da1PV27.U6o8pMW9e1tLafAbhbYIJcw7X FISNIrGnPpccLrx8axEqYgEMie2QINEW9iIuPpTcymV0h5kqxFPuAcg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Sun, 8 Oct 2017 06:26:26 +0000 Date: Sun, 8 Oct 2017 06:26:22 +0000 (UTC) From: Nomad Esst Reply-To: Nomad Esst To: Freebsd-arm Message-ID: <1564758201.3362939.1507443982550@mail.yahoo.com> Subject: BPi M3 awg interface soft reset timed out MIME-Version: 1.0 References: <1564758201.3362939.1507443982550.ref@mail.yahoo.com> X-Mailer: WebService/1.1.10668 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 06:26:33 -0000 I'm facing with this problem that after each "reboot", I get this error fro= m awg driver and the interface is not created!=C2=A0 awg0: mem 0x1c30000-0x1c300ff irq 27 on simple= bus0awg0: soft reset timed outdevice_attach: awg0 attach returned 60 When I unplug the board, and plug it again, there is no problem at all. Jus= t after "reboot"s I face this problem. I've tested with FBSD 11 and FBSD 12= . Thanks in advance. From owner-freebsd-arm@freebsd.org Sun Oct 8 13:51:09 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DA43E3688E for ; Sun, 8 Oct 2017 13:51:09 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA286D462 for ; Sun, 8 Oct 2017 13:51:08 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [10.0.0.68] (unknown [81.149.102.120]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id E14B54EC94; Sun, 8 Oct 2017 13:51:01 +0000 (UTC) From: Andrew Turner Message-Id: <2D2A9368-489D-44AC-9CAA-2292025EA8F1@fubar.geek.nz> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: bhyve on ARMv8 - initarm() and struct arm64_bootparams Date: Sun, 8 Oct 2017 14:50:54 +0100 In-Reply-To: Cc: freebsd-arm@freebsd.org To: Alexandru Elisei References: X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 13:51:09 -0000 > On 7 Oct 2017, at 07:50, Alexandru Elisei = wrote: >=20 > Hello, >=20 > I am currently working on porting bhyve to ARMv8 and I've managed to > start a guest kernel inside bhyve. >=20 > I am having trouble getting past the initarm() function in the guest > and I think the problem is the fact that I am not sending the correct > boot parameter arm64_bootparams->modulep to the guest (the other > struct variables are computed in locore.S before calling initarm()). >=20 > As far as I can I can tell modulep is a pointer to the mapped kernel > image virtual address where module information is stored, but I don't > know how to get that information from the guest kernel when creating > the virtual machine. >=20 > Can anyone provide some help with this issue? It should be the virtual address the module data has been loaded into. = In loader.efi we handle this by searching for the virtual address of the = last module, and add on its size, then add on space for the environment = and dtb. I would strongly suggest you use UEFI boot. It would fix this, and allow = non-FreeBSD operating systems to also boot. There is an existing port of = EDK2 to bhyve, however it=E2=80=99s based on an old code base. = Alternatively u-boot now supports the required EFI parts. There are a = few extra patches for FreeBSD in the repo at [1]. Andrew [1] https://github.com/freebsd/u-boot/ = From owner-freebsd-arm@freebsd.org Sun Oct 8 14:10:14 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4388BE36BA5 for ; Sun, 8 Oct 2017 14:10:14 +0000 (UTC) (envelope-from mihai.carabas@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69417719D4 for ; Sun, 8 Oct 2017 14:10:13 +0000 (UTC) (envelope-from mihai.carabas@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id u138so16481733wmu.5 for ; Sun, 08 Oct 2017 07:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=M+1HosQSdbIul3ITjQul23R3RE6+nHABjEjizODx4qs=; b=XmkwQwhvFHMQOVRonYWE6jiqz65Y2yiv4mr0RJ5AfBSHl6PXAkayJPYMk8h6oyc+ha eEoqqw/jQnMs58RQGsRRu9F+fFbzaZDFXI925BdRbRMlamPcU5vHKt0B36JDfl2CrUK/ dfT2AZttz7xno1GM/8bA53etUp72+3d2iYSdJBzcRd2yv8IPUrPXSEOU+YgRJ28tkcWg UAE9k3x6ikdrA97h7XgqeYwaEj0gaqlNiSNIC2rUNPvHe74wlSucB7FA8m1mgzOABLQc 2/s/KeV8zCRSXEX4JDym0TARLJDAlZt37weTKtTn7Qv592F7UvFLlNFu7CgPmR2bGosz uTPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=M+1HosQSdbIul3ITjQul23R3RE6+nHABjEjizODx4qs=; b=Tt2xyX+TzQmgqLIW7R2aZDEgAiuFWeF+q3HCjsfWUvKB19V5y0XLumbjTRtZwOcw18 SZyVQt5ZeSZxSkBRf7rywUqRU5fpGWz8dfKQG8wOJE4NBGUqg5afxCkd/3wocWPRlGf9 rKe2eDhbQNbTzA7LxRyKV3jgiLgvABrI1cGfpwyCK/oM+EuoAfFYrBcWfnsLAhrrm4TR URTuuSEXRz/u7fJF5SsNaL9/frSgBSrl4Nv5FVuUkafwzm0LnosYjIBkaLzpuFZyHmtn K1QojK/Lbcq+w23qd+O/dKldFdEUWxWt9GHhvzo+n4cG+a0Vsj4cVfi+tlsWUvcfqSlZ Hc9w== X-Gm-Message-State: AMCzsaWfNRy/oaJfb9LFyHiz4qE/F8eL+UnOtBcvsbDm2t1HwQGFTyjg UzXc9QcnuHLt3LKg0SfRtD2gV8dek16WJvHGZDE= X-Google-Smtp-Source: AOwi7QBkx1K22XrDGmtXo1bDOAgbacrhn8dLqzb9R3chrxzbd/mcUbqz3WvU9jweLmCSUT2LepQ7Jo6WiLbC2JGsOM0= X-Received: by 10.223.171.69 with SMTP id r5mr6903069wrc.112.1507471811739; Sun, 08 Oct 2017 07:10:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.228.132 with HTTP; Sun, 8 Oct 2017 07:10:10 -0700 (PDT) In-Reply-To: <2D2A9368-489D-44AC-9CAA-2292025EA8F1@fubar.geek.nz> References: <2D2A9368-489D-44AC-9CAA-2292025EA8F1@fubar.geek.nz> From: Mihai Carabas Date: Sun, 8 Oct 2017 17:10:10 +0300 Message-ID: Subject: Re: bhyve on ARMv8 - initarm() and struct arm64_bootparams To: Andrew Turner Cc: Alexandru Elisei , freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 14:10:14 -0000 On Sun, Oct 8, 2017 at 4:50 PM, Andrew Turner wrote: > > > On 7 Oct 2017, at 07:50, Alexandru Elisei > wrote: > > > > Hello, > > > > I am currently working on porting bhyve to ARMv8 and I've managed to > > start a guest kernel inside bhyve. > > > > I am having trouble getting past the initarm() function in the guest > > and I think the problem is the fact that I am not sending the correct > > boot parameter arm64_bootparams->modulep to the guest (the other > > struct variables are computed in locore.S before calling initarm()). > > > > As far as I can I can tell modulep is a pointer to the mapped kernel > > image virtual address where module information is stored, but I don't > > know how to get that information from the guest kernel when creating > > the virtual machine. > > > > Can anyone provide some help with this issue? > > It should be the virtual address the module data has been loaded into. In > loader.efi we handle this by searching for the virtual address of the las= t > module, and add on its size, then add on space for the environment and dt= b. > > I would strongly suggest you use UEFI boot. It would fix this, and allow > non-FreeBSD operating systems to also boot. There is an existing port of > EDK2 to bhyve, however it=E2=80=99s based on an old code base. Alternativ= ely u-boot > now supports the required EFI parts. There are a few extra patches for > FreeBSD in the repo at [1]. > > At this point we use old bhyveload executable to load the guest into memory. For booting with EFI a VM requires additional work. May be we can dump bhyveload and use UEFI from x86: https://wiki.freebsd.org/bhyve/UEFI ? It is much different from ARM? Mihai > Andrew > > [1] https://github.com/freebsd/u-boot/ > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Sun Oct 8 15:17:50 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFC7BE384AA for ; Sun, 8 Oct 2017 15:17:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BED6B847CE; Sun, 8 Oct 2017 15:17:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id CB332738; Sun, 8 Oct 2017 10:17:48 -0500 (CDT) Date: Sun, 8 Oct 2017 10:17:47 -0500 From: Mark Linimon To: Warner Losh Cc: Ian Lepore , freebsd-arm Subject: Re: armv7, building p7zip and -fPIC Message-ID: <20171008151747.GA24554@lonesome.com> References: <1507403387.86205.286.camel@freebsd.org> <20171007214326.GA22150@lonesome.com> <1507416341.86205.291.camel@freebsd.org> <20171008053812.GA23271@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 15:17:51 -0000 On Sat, Oct 07, 2017 at 11:38:07PM -0700, Warner Losh wrote: > Well, I had been told that the string "arm" had no meaning, so had > been ripping them out of ports. er, "had no meaning" w/rt the ports infrastructure, e.g., that ARCH could never be merely "arm". What am I missing? mcl From owner-freebsd-arm@freebsd.org Sun Oct 8 15:33:37 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 393EAE388E0 for ; Sun, 8 Oct 2017 15:33:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BF743756 for ; Sun, 8 Oct 2017 15:33:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id j17so4288924iod.5 for ; Sun, 08 Oct 2017 08:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hYVbzZ+kCVj6xjmKvMtkqVmmuB57KHXBpLvaR80+zYA=; b=jM7Shm8LEDMcWBwBWFuXaIZNDek5uGhx37Y1KNi4mBVcZKxYoMDWige1i8TDWbRJPz KVVqSVKnZvrajGgrWa3muM/kk0iZicqpVUKrdxjFTZisjyypUOGtFlxPc+vh2GrQlUWq iduhvOHICdXrb4uRk7ZjksAUVyEwpMY2C/NIM8408oVZ0WukpBG50M8vCCM/OkxZUT/G Pyf55OREVi+tNW4y5FNKNfRwvNAeDfiUbKuV7MNi4vyI4VjccY8nceu0jdxdfDK48u7B yzrRlaxUR9CiJhU8znPzM07J4PWRmq6JW5RRsfojF7p4q7950NxvVDnxEh9JoJOUsgrB GrHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hYVbzZ+kCVj6xjmKvMtkqVmmuB57KHXBpLvaR80+zYA=; b=L5V1B0Ly/XK9n4Noq3Rs+kcaiabMhMMbxOaqziST6koUfA+Tpe48YBlVStrnNFN+Rq HhvXrMoqy5V2JGv5OirpZJ7Dr5676JBE2Fx7Ow/c2pudAGiNs5GC6Z+AGu7lLBbaQVKi INXDcybdn8U2rrY6lEVcmyC+L/jKUhHzyGLhlRcT/Js/O4VBJUutjxDV/eqqEr5LNQkp iPTzSqY8ZyU21f2a+wllvl4Q+hxk1tNCi1A2P1PR8K11VF38lxzpn1E7UDuJGbR9WGKD 7McXGRPWtH2Zls+f/lyOlZIG/nJ0YmGqWw3yW39GuKmSMn7Vd3VSuZh85Wmeh538RxUY ZJ8Q== X-Gm-Message-State: AMCzsaXAZa8h38PC2c8E2gRkUKapuOR4252F6LO83LckHgHtjUfbTBdY eXQbMrNaISTMuZ8aHzHRYKZZqI5mELQJ8Jus0cvW4g== X-Google-Smtp-Source: AOwi7QA2gGwcpQH4Bps7pDiivyioxTZe8IbLS9qZlJIOFCIRqpzcY4lkD6oJ0/ZiUAI5Os5XkIYkj8Wdk9VNBLy8AOI= X-Received: by 10.107.135.202 with SMTP id r71mr1955695ioi.26.1507476815580; Sun, 08 Oct 2017 08:33:35 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Sun, 8 Oct 2017 08:33:34 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:957c:6527:31a6:8e54] In-Reply-To: <20171008151747.GA24554@lonesome.com> References: <1507403387.86205.286.camel@freebsd.org> <20171007214326.GA22150@lonesome.com> <1507416341.86205.291.camel@freebsd.org> <20171008053812.GA23271@lonesome.com> <20171008151747.GA24554@lonesome.com> From: Warner Losh Date: Sun, 8 Oct 2017 15:33:34 +0000 X-Google-Sender-Auth: Aj5xIFGYI-J3PlBmUAmIgSn4Qh8 Message-ID: Subject: Re: armv7, building p7zip and -fPIC To: Mark Linimon Cc: Ian Lepore , freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 15:33:37 -0000 On Sun, Oct 8, 2017 at 3:17 PM, Mark Linimon wrote: > On Sat, Oct 07, 2017 at 11:38:07PM -0700, Warner Losh wrote: > > Well, I had been told that the string "arm" had no meaning, so had > > been ripping them out of ports. > > er, "had no meaning" w/rt the ports infrastructure, e.g., that ARCH > could never be merely "arm". What am I missing? > ARCH can be merely arm, like Ian says. It's that way for all the armv4 and armv5 boards we still support... Warner From owner-freebsd-arm@freebsd.org Sun Oct 8 16:07:17 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90EE3E39512 for ; Sun, 8 Oct 2017 16:07:17 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 853486A4B7 for ; Sun, 8 Oct 2017 16:07:16 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: ad0b87b9-ac42-11e7-b50b-53dc5ecda239 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id ad0b87b9-ac42-11e7-b50b-53dc5ecda239; Sun, 08 Oct 2017 16:06:43 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v98G7D9s001406; Sun, 8 Oct 2017 10:07:13 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507478833.86205.307.camel@freebsd.org> Subject: Re: armv7, building p7zip and -fPIC From: Ian Lepore To: Mark Linimon Cc: freebsd-arm Date: Sun, 08 Oct 2017 10:07:13 -0600 In-Reply-To: <20171008053812.GA23271@lonesome.com> References: <1507403387.86205.286.camel@freebsd.org> <20171007214326.GA22150@lonesome.com> <1507416341.86205.291.camel@freebsd.org> <20171008053812.GA23271@lonesome.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 16:07:17 -0000 On Sun, 2017-10-08 at 00:38 -0500, Mark Linimon wrote: > On Sat, Oct 07, 2017 at 04:45:41PM -0600, Ian Lepore wrote: > > > > Not necessarily. There probably aren't too many people building ports > > for arm (v4/v5) > Well, I had been told that the string "arm" had no meaning, so had > been ripping them out of ports. > > So now I need to undo a great deal of work. > > mcl I suspect that if any ${ARCH} == "arm" type stuff exists in ports it may need evaluation to see if the intent, and thus the fix, was really somthing like ${ARCH:Marm*}. I suspect there are relatively few occurances of bare "arm" that don't really need to apply to all arm arches, except in places where the other arm arches are also handled nearby. -- Ian From owner-freebsd-arm@freebsd.org Mon Oct 9 03:55:46 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EC65E46ECB for ; Mon, 9 Oct 2017 03:55:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B256D28EA for ; Mon, 9 Oct 2017 03:55:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id B838C10A87D; Sun, 8 Oct 2017 23:55:44 -0400 (EDT) From: John Baldwin To: freebsd-arm@freebsd.org Cc: Monty Chaney-Geib Subject: Re: RPi3 Kernel Fails to Build Date: Sat, 07 Oct 2017 09:47:02 -0700 Message-ID: <1628757.voU4eBV2gm@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Sun, 08 Oct 2017 23:55:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 03:55:46 -0000 On Thursday, October 05, 2017 10:24:03 PM Monty Chaney-Geib wrote: > I'm getting an error trying to build the kernel on hardware. What do you > guys recommend I do? There is the error: > > MAKE="make" sh /usr/src/sys/conf/newvers.sh GENERIC > cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp > -B/usr/obj/usr/src/tmp/usr/bin -c -O -pipe -g -nostdinc -I. > -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 > -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs > -fdiagnostics-show-option -Wno-unknown-pragmas > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -Wno-error-unused-function > -Wno-error-pointer-sign -Wno-error-shift-negative-value > -std=iso9899:1999 -Werror vers.c > ctfconvert -L VERSION -g vers.o > linking kernel.full > unknown emulation: aarch64elf > line 19: : expected, but got ( > PROVIDE (etext = .); > ^ > *** Error code 1 > > Stop. > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src Do you have the aarch64-binutils package installed? -- John Baldwin From owner-freebsd-arm@freebsd.org Mon Oct 9 03:58:54 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B490E46F9C for ; Mon, 9 Oct 2017 03:58:54 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA1293505; Mon, 9 Oct 2017 03:58:53 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id m72so18928149wmc.1; Sun, 08 Oct 2017 20:58:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5sTnhZPj7tbYquS9islXyP70dDrt8oauXqgysz46MKk=; b=MkGbpk22lM3TwJsauhwG5irrNoUa0YPDBheKB2nul/h9Pu2lC8AyZsMrNRX4Xb3sOB 8rJl6rYV0/FI+8XRjm8qPWSNr1oymGwc7+vRUE9uJFKs8xjD+9ops06G7/WozxVbF8Q1 0hwK5q4P+298iOYxQu+sfXn4LXwVoQVhMQgjObMv93KZUCL6KjCfP380lpxlZjAvJeh/ qRU1F+x0VDn0xIii+6ZGu2BzKlW32T8md90puLxa3P6MDd3swogpKGz+uWvfGFucAM7Z lV7Z9wnb1xg5pb6Wyu/GZYPO0CvUOg4jScsxynxbJk8ehWBp/upZE7NQ8aMLBq+gdksJ GHAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5sTnhZPj7tbYquS9islXyP70dDrt8oauXqgysz46MKk=; b=oUIyq3yqJD5toefxnSuN5vZWuiED0/nObuoqLyyut+vcsyPuPCWEeiuZfK4xC/cUmB fHy612cZ27gBFrkMpkzfDoUMathZeTa7tF+HuW48j9RssgjJFm4b8eIQFWqFHOjfEnte BnoR9GQpDvUg3hoSwdvcxebNlt+J4lqdnx5GpOvISEEpmKzUAbN3qeT5OJXeCr5Ippqt OpRjc9jbNW3Nk8DV+j7rqrEo7/0j4FBeLqogQfJi4CHiwrOR2NV+4D3yQSGbg2hMvKR5 lDQmTcyBc4/0IC83smd6nXIjF040PtlBn3+f8VSirhHfg2OLp0ypNNMlhY3/V9hPdIuK eRZQ== X-Gm-Message-State: AMCzsaWIpJF01Nwhv0p4R2CJVs65RvOUUBrzcuH/YaFNWpYv02vcSFrp 4ICiSJaVzSBNC8wsRemcQIZ5eo/Q+VGCRp9xOEsJmQ== X-Google-Smtp-Source: AOwi7QD4AE87Xg4l7D3ZI6eGOr28Mxi4vUAVV/8iBWrFBkUcnvfrJRRGrdbFCRGW7/9E7TQ/rWOLsr2tLK63h5AJqCE= X-Received: by 10.80.147.14 with SMTP id m14mr12475494eda.33.1507521531465; Sun, 08 Oct 2017 20:58:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.129.226 with HTTP; Sun, 8 Oct 2017 20:58:50 -0700 (PDT) In-Reply-To: <1628757.voU4eBV2gm@ralph.baldwin.cx> References: <1628757.voU4eBV2gm@ralph.baldwin.cx> From: Monty Chaney-Geib Date: Sun, 8 Oct 2017 23:58:50 -0400 Message-ID: Subject: Re: RPi3 Kernel Fails to Build To: John Baldwin Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 03:58:54 -0000 Yes I have version 2.28 installed. On Sat, Oct 7, 2017 at 12:47 PM, John Baldwin wrote: > On Thursday, October 05, 2017 10:24:03 PM Monty Chaney-Geib wrote: > > I'm getting an error trying to build the kernel on hardware. What do you > > guys recommend I do? There is the error: > > > > MAKE="make" sh /usr/src/sys/conf/newvers.sh GENERIC > > cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp > > -B/usr/obj/usr/src/tmp/usr/bin -c -O -pipe -g -nostdinc -I. > > -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL > > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h > -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 > > -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall > -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wcast-qual -Wundef -Wno-pointer-sign > > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs > > -fdiagnostics-show-option -Wno-unknown-pragmas > > -Wno-error-tautological-compare -Wno-error-empty-body > > -Wno-error-parentheses-equality -Wno-error-unused-function > > -Wno-error-pointer-sign -Wno-error-shift-negative-value > > -std=iso9899:1999 -Werror vers.c > > ctfconvert -L VERSION -g vers.o > > linking kernel.full > > unknown emulation: aarch64elf > > line 19: : expected, but got ( > > PROVIDE (etext = .); > > ^ > > *** Error code 1 > > > > Stop. > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /usr/src > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/src > > Do you have the aarch64-binutils package installed? > > -- > John Baldwin > From owner-freebsd-arm@freebsd.org Mon Oct 9 05:40:38 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 917B3E25ED1 for ; Mon, 9 Oct 2017 05:40:38 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-18.reflexion.net [208.70.210.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C76E27D1B9 for ; Mon, 9 Oct 2017 05:40:36 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19495 invoked from network); 9 Oct 2017 05:40:35 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 9 Oct 2017 05:40:35 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Mon, 09 Oct 2017 01:40:35 -0400 (EDT) Received: (qmail 3386 invoked from network); 9 Oct 2017 05:40:35 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 9 Oct 2017 05:40:35 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 704B9EC8559; Sun, 8 Oct 2017 22:40:34 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: RPi3 Kernel Fails to Build From: Mark Millard In-Reply-To: Date: Sun, 8 Oct 2017 22:40:33 -0700 Cc: John Baldwin , freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <8ED4F645-8F3A-4D45-BE2F-0491D73DC9F5@dsl-only.net> References: <1628757.voU4eBV2gm@ralph.baldwin.cx> To: Monty Chaney-Geib X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 05:40:38 -0000 On 2017-Oct-8, at 8:58 PM, Monty Chaney-Geib wrote: > Yes I have version 2.28 installed. But the commands you show have: cc . . . -B/usr/obj/usr/src/tmp/usr/bin . . . which leads to use of the system binutils built in that area, not the ones from ports, at least for that command. If such also applies to the link of the kernel.full then. . . What version of the system is running and what version of the system is being built? Is this a context where ld is lld from the system llvm/clang tool set? Or is ld from a build of the old system binutils? > On Sat, Oct 7, 2017 at 12:47 PM, John Baldwin wrote: > >> On Thursday, October 05, 2017 10:24:03 PM Monty Chaney-Geib wrote: >>> I'm getting an error trying to build the kernel on hardware. What do you >>> guys recommend I do? There is the error: >>> >>> MAKE="make" sh /usr/src/sys/conf/newvers.sh GENERIC >>> cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp >>> -B/usr/obj/usr/src/tmp/usr/bin -c -O -pipe -g -nostdinc -I. >>> -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL >>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h >> -fno-omit-frame-pointer >>> -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 >>> -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall >> -Wredundant-decls >>> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >>> -Winline -Wcast-qual -Wundef -Wno-pointer-sign >>> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs >>> -fdiagnostics-show-option -Wno-unknown-pragmas >>> -Wno-error-tautological-compare -Wno-error-empty-body >>> -Wno-error-parentheses-equality -Wno-error-unused-function >>> -Wno-error-pointer-sign -Wno-error-shift-negative-value >>> -std=iso9899:1999 -Werror vers.c >>> ctfconvert -L VERSION -g vers.o >>> linking kernel.full >>> unknown emulation: aarch64elf >>> line 19: : expected, but got ( >>> PROVIDE (etext = .); >>> ^ >>> *** Error code 1 >>> >>> Stop. >>> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC >>> *** Error code 1 >>> >>> Stop. >>> make[1]: stopped in /usr/src >>> *** Error code 1 >>> >>> Stop. >>> make: stopped in /usr/src >> >> Do you have the aarch64-binutils package installed? === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Oct 9 08:51:36 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1488E29DAB for ; Mon, 9 Oct 2017 08:51:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EE4B2177 for ; Mon, 9 Oct 2017 08:51:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v998paFJ072692 for ; Mon, 9 Oct 2017 08:51:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 222876] growfs messes with ufs filesystem size and checkums Date: Mon, 09 Oct 2017 08:51:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sylvain@sylvaingarrigues.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 08:51:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222876 Bug ID: 222876 Summary: growfs messes with ufs filesystem size and checkums Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: sylvain@sylvaingarrigues.com I just created an arm image with the usual steps found in https://github.com/freebsd/freebsd/blob/master/release/tools/arm.subr (cf arm_create_disk routine). After first boot, growfs does its trick and df reports the partition is tak= ing up the full space (32 GB in my case), but still my filesystem becomes full after a few package (original arm img size was 1.5 GB). Additionally, I get hundreds of: checksum failed: cg 19, cgp: 0x0 !=3D bp: 0x61de29e7 on every boot now. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Mon Oct 9 15:02:40 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15D54E32A2D for ; Mon, 9 Oct 2017 15:02:40 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0017E72A44; Mon, 9 Oct 2017 15:02:38 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id q124so21283839wmb.5; Mon, 09 Oct 2017 08:02:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vHVVVmvcM3PWss6m9A57Jm8tQNl9mhnjKEd2VYyibS8=; b=Dd9+E7h6eYrD7+P4o1O8cCX7xpyQopHU7DzSGmI8kUB66SazvWcOKbegPUmBcTS5V0 fQdOgWDjXyw4rq5whkZmyKh1y9JPUR9FVbu2GMp06iS+DdTRZjPK/ZFtNbNmtQXAlRrB KGeju5XPpjYGIap4OF+rtzcWuOlOQFMEE6NYIe+XhAv2NfSdMf2YEyRggPPSv0V3mv6Q tRuuAePs04+eXPPMNZSXtfTrrkMfFRwyHlIDKjxgjEjAcxYfDJhJHnjpUQcZt3dDVRbn qOQiCr8g6rsXFkXsx2dQGrAcsNxiRdy0n96+2/SI6ZvuabxnhNvAiK8UMBlyLZIt+R9f qISw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vHVVVmvcM3PWss6m9A57Jm8tQNl9mhnjKEd2VYyibS8=; b=LQulIgk8wdZPXbmbIMmqpOQXRl1RqZGievoBX/nJ12wJ26L6CMJMR1SDYH4497ah7l +kjh30NYMCjsuvOPYWrm1Ivyt/0NW4p3koGuO4Esk5Q6wuThC7SVMEGbBkBJnEFndTCv 7KKOUWKlYWFa61FzPU9vqdfZtP68nrIRcZbCJINxrohPn4F1R+bNUi8I6Q33eLSfd7Ua ZrZo9oeqVFEiqXO2A6fIYXu2A+xAP8XQ9uGI8PjYPF3vmh+26OLHTbXWgE9TjmrRAq4h ZdEHMDxF2P6obPb0hfCUFiSaNxnzdnT2NC2Kgfv5VMYMZbuyF8SsnwCxe36JMOyJZerq Wbpg== X-Gm-Message-State: AMCzsaUgSrMoDTOFDaS05B9c6o5aPpzXxQTrUdxcpwyUgkXYcP3SZuH+ XCSwmwgYxboDWd81UnxaF+VdvclgpMms0d2x6XOdGQ== X-Google-Smtp-Source: AOwi7QBTIf9PM0ejVe+lpBXKeffDggH+eYqlvjcoJL8fR9EX2rMU9gRsPD/RcXrkESAo+adPuceoJCqURfm467iyZ88= X-Received: by 10.80.181.27 with SMTP id y27mr1934748edd.297.1507561357190; Mon, 09 Oct 2017 08:02:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.129.226 with HTTP; Mon, 9 Oct 2017 08:02:36 -0700 (PDT) In-Reply-To: <8ED4F645-8F3A-4D45-BE2F-0491D73DC9F5@dsl-only.net> References: <1628757.voU4eBV2gm@ralph.baldwin.cx> <8ED4F645-8F3A-4D45-BE2F-0491D73DC9F5@dsl-only.net> From: Monty Chaney-Geib Date: Mon, 9 Oct 2017 11:02:36 -0400 Message-ID: Subject: Re: RPi3 Kernel Fails to Build To: Mark Millard Cc: John Baldwin , freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 15:02:40 -0000 I'm trying to build a more up to date 12.0 system. I am currently running the raspbsd.org 12.0 version on my Pi 3 from February. On Mon, Oct 9, 2017 at 1:40 AM, Mark Millard wrote: > > On 2017-Oct-8, at 8:58 PM, Monty Chaney-Geib > wrote: > > > Yes I have version 2.28 installed. > > But the commands you show have: > > cc . . . -B/usr/obj/usr/src/tmp/usr/bin . . . > > which leads to use of the system binutils > built in that area, not the ones from ports, > at least for that command. > > If such also applies to the link of the > kernel.full then. . . > > What version of the system is running and what > version of the system is being built? Is this > a context where ld is lld from the system > llvm/clang tool set? Or is ld from a build of > the old system binutils? > > > On Sat, Oct 7, 2017 at 12:47 PM, John Baldwin > wrote: > > > >> On Thursday, October 05, 2017 10:24:03 PM Monty Chaney-Geib wrote: > >>> I'm getting an error trying to build the kernel on hardware. What do > you > >>> guys recommend I do? There is the error: > >>> > >>> MAKE="make" sh /usr/src/sys/conf/newvers.sh GENERIC > >>> cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp > >>> -B/usr/obj/usr/src/tmp/usr/bin -c -O -pipe -g -nostdinc -I. > >>> -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL > >>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h > >> -fno-omit-frame-pointer > >>> -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 > >>> -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall > >> -Wredundant-decls > >>> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith > >>> -Winline -Wcast-qual -Wundef -Wno-pointer-sign > >>> -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs > >>> -fdiagnostics-show-option -Wno-unknown-pragmas > >>> -Wno-error-tautological-compare -Wno-error-empty-body > >>> -Wno-error-parentheses-equality -Wno-error-unused-function > >>> -Wno-error-pointer-sign -Wno-error-shift-negative-value > >>> -std=iso9899:1999 -Werror vers.c > >>> ctfconvert -L VERSION -g vers.o > >>> linking kernel.full > >>> unknown emulation: aarch64elf > >>> line 19: : expected, but got ( > >>> PROVIDE (etext = .); > >>> ^ > >>> *** Error code 1 > >>> > >>> Stop. > >>> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > >>> *** Error code 1 > >>> > >>> Stop. > >>> make[1]: stopped in /usr/src > >>> *** Error code 1 > >>> > >>> Stop. > >>> make: stopped in /usr/src > >> > >> Do you have the aarch64-binutils package installed? > > > > === > Mark Millard > markmi at dsl-only.net > > From owner-freebsd-arm@freebsd.org Mon Oct 9 17:33:17 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E52B1E374EB for ; Mon, 9 Oct 2017 17:33:17 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-18.reflexion.net [208.70.210.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8669073C7B for ; Mon, 9 Oct 2017 17:33:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 9459 invoked from network); 9 Oct 2017 17:33:10 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 9 Oct 2017 17:33:10 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Mon, 09 Oct 2017 13:33:10 -0400 (EDT) Received: (qmail 16727 invoked from network); 9 Oct 2017 17:33:10 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 9 Oct 2017 17:33:10 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 8143EEC952C; Mon, 9 Oct 2017 10:33:09 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: RPi3 Kernel Fails to Build From: Mark Millard In-Reply-To: Date: Mon, 9 Oct 2017 10:33:08 -0700 Cc: John Baldwin , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <26DEBB20-12FC-4773-8F80-6F6ABC5E1D54@dsl-only.net> References: <1628757.voU4eBV2gm@ralph.baldwin.cx> <8ED4F645-8F3A-4D45-BE2F-0491D73DC9F5@dsl-only.net> To: Monty Chaney-Geib X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 17:33:18 -0000 On 2017-Oct-9, at 8:02 AM, Monty Chaney-Geib = wrote: > I'm trying to build a more up to date 12.0 system. I am currently = running the raspbsd.org 12.0 version on my Pi 3 from February.=20 Unfortunately WITH_LLD_BOOTSTRAP was not added until head -r316647 on 2017-Apr-9. It looks like as of now http://www.raspbsd.org/raspberrypi.html has a build based on head -r320146 and so might avoid the need for a specially handled ld for going forward from there. > On Mon, Oct 9, 2017 at 1:40 AM, Mark Millard = wrote: >=20 > On 2017-Oct-8, at 8:58 PM, Monty Chaney-Geib = wrote: >=20 > > Yes I have version 2.28 installed. >=20 > But the commands you show have: >=20 > cc . . . -B/usr/obj/usr/src/tmp/usr/bin . . . >=20 > which leads to use of the system binutils > built in that area, not the ones from ports, > at least for that command. >=20 > If such also applies to the link of the > kernel.full then. . . >=20 > What version of the system is running and what > version of the system is being built? Is this > a context where ld is lld from the system > llvm/clang tool set? Or is ld from a build of > the old system binutils? >=20 > > On Sat, Oct 7, 2017 at 12:47 PM, John Baldwin = wrote: > > > >> On Thursday, October 05, 2017 10:24:03 PM Monty Chaney-Geib wrote: > >>> I'm getting an error trying to build the kernel on hardware. What = do you > >>> guys recommend I do? There is the error: > >>> > >>> MAKE=3D"make" sh /usr/src/sys/conf/newvers.sh GENERIC > >>> cc -target aarch64-unknown-freebsd12.0 = --sysroot=3D/usr/obj/usr/src/tmp > >>> -B/usr/obj/usr/src/tmp/usr/bin -c -O -pipe -g -nostdinc -I. > >>> -I/usr/src/sys -I/usr/src/sys/contrib/libfdt -D_KERNEL > >>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h > >> -fno-omit-frame-pointer > >>> -mno-omit-leaf-frame-pointer -mgeneral-regs-only -ffixed-x18 > >>> -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall > >> -Wredundant-decls > >>> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith > >>> -Winline -Wcast-qual -Wundef -Wno-pointer-sign > >>> -D__printf__=3D__freebsd_kprintf__ -Wmissing-include-dirs > >>> -fdiagnostics-show-option -Wno-unknown-pragmas > >>> -Wno-error-tautological-compare -Wno-error-empty-body > >>> -Wno-error-parentheses-equality -Wno-error-unused-function > >>> -Wno-error-pointer-sign -Wno-error-shift-negative-value > >>> -std=3Diso9899:1999 -Werror vers.c > >>> ctfconvert -L VERSION -g vers.o > >>> linking kernel.full > >>> unknown emulation: aarch64elf > >>> line 19: : expected, but got ( > >>> PROVIDE (etext =3D .); > >>> ^ > >>> *** Error code 1 > >>> > >>> Stop. > >>> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > >>> *** Error code 1 > >>> > >>> Stop. > >>> make[1]: stopped in /usr/src > >>> *** Error code 1 > >>> > >>> Stop. > >>> make: stopped in /usr/src > >> > >> Do you have the aarch64-binutils package installed? =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Oct 9 17:52:15 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45D77E37AE6 for ; Mon, 9 Oct 2017 17:52:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F212746F3 for ; Mon, 9 Oct 2017 17:52:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v99HqHoS052722 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Oct 2017 10:52:17 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v99HqG7O052721; Mon, 9 Oct 2017 10:52:16 -0700 (PDT) (envelope-from fbsd) Date: Mon, 9 Oct 2017 10:52:16 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Difficulty with armv6 to v7 transition. Message-ID: <20171009175216.GA52497@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 17:52:15 -0000 On an RPI2 model B, invoking make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log (after a cleandir) the log promptly reports make[1]: "/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. *** [buildworld] Error code 1 make: stopped in /usr/src The kernel is r322520, sources are at 324424. Kernel r324342 does likewise. Thanks for reading, and any suggestions. bob prohaska From owner-freebsd-arm@freebsd.org Mon Oct 9 18:19:44 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2E90E3830F for ; Mon, 9 Oct 2017 18:19:44 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4158D7540C for ; Mon, 9 Oct 2017 18:19:43 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 66a24089-ad1e-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 66a24089-ad1e-11e7-a893-25625093991c; Mon, 09 Oct 2017 18:19:35 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v99IJVx8001751; Mon, 9 Oct 2017 12:19:31 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507573171.84167.9.camel@freebsd.org> Subject: Re: Difficulty with armv6 to v7 transition. From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Mon, 09 Oct 2017 12:19:31 -0600 In-Reply-To: <20171009175216.GA52497@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 18:19:44 -0000 On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > On an RPI2 model B, invoking  > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log Never set MACHINE_ARCH when building, use TARGET_ARCH.  Be sure to set TARGET_ARCH when installing as well. -- Ian > (after a cleandir) > the log promptly reports > make[1]: "/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER: > Determined that CC=cc matches the source tree.  Not bootstrapping a > cross-compiler. > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > TARGET_ARCH. > *** [buildworld] Error code 1 > > make: stopped in /usr/src > > The kernel is r322520, sources are at 324424. Kernel r324342 does > likewise. > > Thanks for reading, and any suggestions. > > bob prohaska > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > " From owner-freebsd-arm@freebsd.org Mon Oct 9 18:37:28 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A78FE38AC4 for ; Mon, 9 Oct 2017 18:37:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3F7F763D4 for ; Mon, 9 Oct 2017 18:37:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id b186so2087957iof.8 for ; Mon, 09 Oct 2017 11:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=t3eWdNsA8d3op9iR92kj0mb3rmgR00mcmj4tv8Dzjog=; b=MSDFhcrXXRzphgOZS1lUhwiAX2K/sOVNs18+qnp4hTCoC89UT0M8ZL96NVum/9fflC 5CXdOGMm9bXmVr5bTKLJEDKLIStp93YA2acej+6ZR7scFM3JXEyZR2+n2ziG20dJCCWG xgDbbnLoHiv+Wtoy20usDj7QUWkO1wkI2LU9Fum8W6O5qucIQVeY+cdXZB2BewpqCdN5 BPWx1vsc61IEk6w9tjd3aogpGBvJUhGIKkMUTjpYWXA93uNU3Nu8SwRpngj1TDuN49+e 9Q3J8brMsFgdkJ/UpYw5D9oCsgcihM9fWWCym7cm88lF8awDjf9goW56+0h3kq+JXKCp HcCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=t3eWdNsA8d3op9iR92kj0mb3rmgR00mcmj4tv8Dzjog=; b=UnzYYIvRd4HPlMNWP4mYDK3eLRdrMUxMGuGLRnDWUtsPZdIZogVcDGDeyYi3GnZC4S eOFa8Qq2QpN5Pwt7s19c1Pq13mWLbAXdi8X3q0OZ/PdCy4E7w1qJq7OCfortnc3my9xV uC2N7wB1FBH9nzYk570gMlqGGaWwAkm975scxBNazeZ/MawU/HSKfXP7YZPDkz6fvBvz TjMGuHnODNZ9v44Y6ZC4cOckfG63UdECXtx4IqVRAfs7rd/WpuKYeijM1AJnezI5mxB4 1moNxfVSqcTXWou/12bfID6gYCurgBDakhuOlVZG0nvO5nYrocw+nKEoY/E/hrAHqaDo rpyw== X-Gm-Message-State: AMCzsaXVsVGgvOA4DKa6EW+e9vEOPBhLoogUUSbym2/ye3eeF4Ef5aeg J29cYSaRTwHunPfNekB8iGJCyvspOgChlNT2An+N4A== X-Google-Smtp-Source: AOwi7QADC6q1687qnHhDmn2qw8U5f4k/1djKr0hVBwhFfRqLoOFyFp2lSEX2LE3Xd4YBERGq0RX1cVdI6JzGVfp1YSY= X-Received: by 10.107.185.6 with SMTP id j6mr9837913iof.221.1507574247135; Mon, 09 Oct 2017 11:37:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Mon, 9 Oct 2017 11:37:26 -0700 (PDT) X-Originating-IP: [65.151.16.249] Received: by 10.79.94.130 with HTTP; Mon, 9 Oct 2017 11:37:26 -0700 (PDT) In-Reply-To: <1507573171.84167.9.camel@freebsd.org> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> From: Warner Losh Date: Mon, 9 Oct 2017 12:37:26 -0600 X-Google-Sender-Auth: cdds3bJ-sGD7RSRFSLeCG63a8Oo Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: Ian Lepore Cc: bob prohaska , freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 18:37:28 -0000 On Oct 9, 2017 12:19 PM, "Ian Lepore" wrote: On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > On an RPI2 model B, invoking > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log Never set MACHINE_ARCH when building, use TARGET_ARCH. Be sure to set TARGET_ARCH when installing as well. That was a specific work around... But the real issue is the system compiler does need to be rebuilt.. Warner -- Ian > (after a cleandir) > the log promptly reports > make[1]: "/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER: > Determined that CC=cc matches the source tree. Not bootstrapping a > cross-compiler. > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > TARGET_ARCH. > *** [buildworld] Error code 1 > > make: stopped in /usr/src > > The kernel is r322520, sources are at 324424. Kernel r324342 does > likewise. > > Thanks for reading, and any suggestions. > > bob prohaska > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > " _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Mon Oct 9 19:14:53 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE91EE39882 for ; Mon, 9 Oct 2017 19:14:53 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A94C77C43 for ; Mon, 9 Oct 2017 19:14:52 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 1c6773ef-ad26-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 1c6773ef-ad26-11e7-a893-25625093991c; Mon, 09 Oct 2017 19:14:46 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v99JEgKS001883; Mon, 9 Oct 2017 13:14:42 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507576482.84167.20.camel@freebsd.org> Subject: Re: Difficulty with armv6 to v7 transition. From: Ian Lepore To: Warner Losh Cc: freebsd-arm@freebsd.org Date: Mon, 09 Oct 2017 13:14:42 -0600 In-Reply-To: References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 19:14:53 -0000 On Mon, 2017-10-09 at 12:37 -0600, Warner Losh wrote: > On Oct 9, 2017 12:19 PM, "Ian Lepore" wrote: > > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > > > On an RPI2 model B, invoking > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > Never set MACHINE_ARCH when building, use TARGET_ARCH.  Be sure to > set > TARGET_ARCH when installing as well. > > > > That was a specific work around... > > But the real issue is the system compiler does need to be rebuilt.. > > Warner > > Which means when upgrading from self-hosted armv6 to armv7, you're really doing a full crossbuild (just like when we did the armv6hf->v6 dance), so TARGET_ARCH= actually is the right answer? > -- Ian > > > > > (after a cleandir) > > the log promptly reports > > make[1]: "/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER: > > Determined that CC=cc matches the source tree.  Not bootstrapping a > > cross-compiler. > > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > > TARGET_ARCH. > > *** [buildworld] Error code 1 > > > > make: stopped in /usr/src > > > > The kernel is r322520, sources are at 324424. Kernel r324342 does > > likewise. > > > > Thanks for reading, and any suggestions. > > > > bob prohaska > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.o > > rg > > " > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > " > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > " From owner-freebsd-arm@freebsd.org Mon Oct 9 19:15:58 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA781E39910 for ; Mon, 9 Oct 2017 19:15:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE71A77CCD for ; Mon, 9 Oct 2017 19:15:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x232.google.com with SMTP id f187so8454669itb.1 for ; Mon, 09 Oct 2017 12:15:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/XWn3Ew/o6uHGMqsn41nehufZ6LCROrVXorikMrAecU=; b=FLL7slpypJtYjeMqd2aro8PR86QCtGjrC5p5AXi3jJHJuB9hsb4RtpJDbnyyO8YzFt xAExSpEUHG/PdjqvSIxb/WqAFDfW/LsGGVTY4A35Fs/Eh0ghtpBj+gV670mA4F1OLxs2 iPQCBbXRvsVjZAMqN6pyB7IVvXQ9pdjjdJ1W7JsOliEz2B1uz+SkeuKUE6q5M+yXzGef fK+Zvak0Kf9mPEIQVuS3L/mIMq+IKBJV5v8o3SgaVLqarMCWiRt/xf9U/xo3TdwL1yyA Qk/NKy9+3HA8R4ZLTYNF7w8oqs4bEqR290nNfmVcIF9M/TZuu17erOfF1gBfaWoFPQbx xmUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/XWn3Ew/o6uHGMqsn41nehufZ6LCROrVXorikMrAecU=; b=cqhH8t6au96mWrDGo1rofe1tKJVG7rpE9Y925SP1g6jokD+RdhZaOixZAIDKGKRAm+ 5OUW7fYC8VUWkVc9V6WzMFdIVxrVMgewTxiBZgS968IHa60xjfM3BtPGmaMBolJ2Jv2h Oi1JE0hBCyWx+AeBwrwLq5Wu7ie9ZGuEVrlG0gR4OUli1tKW47qDKYCHNGzD020vd21f +USBFpKkaZJZAfhZ0GO5YyMfVUPCy/Ol0vVue5PJeZpJhW+8WYwpsYFFntQgQSOAW8Pb /bx0Ctj2TEuWCuFXMFr+Z0pg2Ly7JLrOXHT6a4CK6wChXLqKMIf1iONxWBWLxsXNpu/r jN/w== X-Gm-Message-State: AMCzsaXS4QC0Ey9Sl/VathAjnT2UMCqUpupmlHBqqUL9jkbMdTFSaevW VFZI4k1oPbeabFRKtCyfwxRXyqR1HhLknVLnXfGfHw== X-Google-Smtp-Source: AOwi7QCXLzbZ9jVpbUBmgu8ON1vtS3t1h2PB6vWf4PVV1AR/ZPLRQgN3zHbgg7xhjoARtIPNsiMbA1zAUFoGMO8tymM= X-Received: by 10.36.203.3 with SMTP id u3mr13918573itg.136.1507576558016; Mon, 09 Oct 2017 12:15:58 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Mon, 9 Oct 2017 12:15:57 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:8936:338a:89de:d5ea] In-Reply-To: <1507576482.84167.20.camel@freebsd.org> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <1507576482.84167.20.camel@freebsd.org> From: Warner Losh Date: Mon, 9 Oct 2017 13:15:57 -0600 X-Google-Sender-Auth: DnxJjd0NWQG3e_CgykLjHojVWNc Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: Ian Lepore Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 19:15:59 -0000 On Mon, Oct 9, 2017 at 1:14 PM, Ian Lepore wrote: > On Mon, 2017-10-09 at 12:37 -0600, Warner Losh wrote: > > On Oct 9, 2017 12:19 PM, "Ian Lepore" wrote: > > > > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > > > > > On an RPI2 model B, invoking > > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > Never set MACHINE_ARCH when building, use TARGET_ARCH. Be sure to > > set > > TARGET_ARCH when installing as well. > > > > > > > > That was a specific work around... > > > > But the real issue is the system compiler does need to be rebuilt.. > > > > Warner > > > > > > Which means when upgrading from self-hosted armv6 to armv7, you're > really doing a full crossbuild (just like when we did the armv6hf->v6 > dance), so TARGET_ARCH= actually is the right answer? It should be the right answer. This was a specific workaround for a specific bug that I think we're past... Warner > > -- Ian > > > > > > > > (after a cleandir) > > > the log promptly reports > > > make[1]: "/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER: > > > Determined that CC=cc matches the source tree. Not bootstrapping a > > > cross-compiler. > > > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > > > TARGET_ARCH. > > > *** [buildworld] Error code 1 > > > > > > make: stopped in /usr/src > > > > > > The kernel is r322520, sources are at 324424. Kernel r324342 does > > > likewise. > > > > > > Thanks for reading, and any suggestions. > > > > > > bob prohaska > > > > > > _______________________________________________ > > > freebsd-arm@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.o > > > rg > > > " > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > > " > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > > " > From owner-freebsd-arm@freebsd.org Tue Oct 10 14:02:05 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00196E328B9 for ; Tue, 10 Oct 2017 14:02:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1A9B83663; Tue, 10 Oct 2017 14:02:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 5AF8810A8BA; Tue, 10 Oct 2017 10:02:02 -0400 (EDT) From: John Baldwin To: freebsd-arm@freebsd.org Cc: Warner Losh , Ian Lepore Subject: Re: Difficulty with armv6 to v7 transition. Date: Tue, 10 Oct 2017 06:52:22 -0700 Message-ID: <7865090.pGrJhPWvLa@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Tue, 10 Oct 2017 10:02:02 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2017 14:02:05 -0000 On Monday, October 09, 2017 12:37:26 PM Warner Losh wrote: > On Oct 9, 2017 12:19 PM, "Ian Lepore" wrote: > > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > On an RPI2 model B, invoking > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > Never set MACHINE_ARCH when building, use TARGET_ARCH. Be sure to set > TARGET_ARCH when installing as well. > > > > That was a specific work around... > > But the real issue is the system compiler does need to be rebuilt.. So the workaround needs to be updated to include WITHOUT_SYSTEM_COMPILER=yes then? -- John Baldwin From owner-freebsd-arm@freebsd.org Wed Oct 11 02:33:57 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C988E43CC1 for ; Wed, 11 Oct 2017 02:33:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 06FAA757B9; Wed, 11 Oct 2017 02:33:56 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9B2XvGq057624 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 10 Oct 2017 19:33:58 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9B2XvJA057623; Tue, 10 Oct 2017 19:33:57 -0700 (PDT) (envelope-from fbsd) Date: Tue, 10 Oct 2017 19:33:56 -0700 From: bob prohaska To: Ian Lepore Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171011023356.GA57571@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1507573171.84167.9.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 02:33:57 -0000 On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > On an RPI2 model B, invoking? > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > TARGET_ARCH when installing as well. Tried it, like so: root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > buildworld.log & [1] 1006 root@www:/usr/src # 1 error [1] Exit 2 make -j4 buildworld TARGET_ARCH=armv7 > buildworld.log root@www:/usr/src # more *.log --- buildworld --- make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. *** [buildworld] Error code 1 make: stopped in /usr/src I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various iterations. Should the variables be set somewhere else, in a config file? At this point the kernel is at r324499, along with the sources. Userland dates from late June (operator error). Kernels build, but could that make the trouble I'm seeing? Clang -v reports FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) Target: armv6-unknown-freebsd12.0-gnueabihf Thread model: posix InstalledDir: /usr/bin Thanks again! bob prohaska From owner-freebsd-arm@freebsd.org Wed Oct 11 02:39:17 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34260E43EB6 for ; Wed, 11 Oct 2017 02:39:17 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED43275A97 for ; Wed, 11 Oct 2017 02:39:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id l196so1065834itl.4 for ; Tue, 10 Oct 2017 19:39:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wuEQEEqRsB1cdAUX0azoUQqz7vwHUud6LzB9ZIWq90Q=; b=qev0VJX/YFcYQLmXKjsGYYUjlFPA14OgJi6sRhWx7IYI7LBHacGbZOCVVNXuwmO+i6 X+rcWO65eyZtLBr+KRos5FtuXbhWaV76XI+rXo3B71aW6+QCCyF95eCnmMF0YR7sqJm8 osrqVq1A8bSi79cyRKUEDf2rB1Q3gJafhIaguEJpfAdyfVNvfZLdfnkwYK87yKM65fHx i7PKg7qShHBM5k0gmeHDNXf0mKL6gzru4wsXOrXrhVTVRJj+SYQeI5hmdqw3FkckB6W4 eM6F50aDbLQ1E0q3Nsvc8m9IBd1z4tW/k0UWCwVxgpxusx1ETN23cjOjQE3PWcVDeZa5 v1TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=wuEQEEqRsB1cdAUX0azoUQqz7vwHUud6LzB9ZIWq90Q=; b=CWZZCe14KhnnXE4VwqjWIg6dU5yr4UpRaYrSf7yxB2wruimZ2CRGhaGr8g+6G5aeCi m2pxF0JRD5JtpfN+dPRhPlMckGgC7y5LANTWZzvYjJKhM8qBQth1Lf+E6YHHSDfaZfOL XTsvpVFIy8ncu4dxIi0A1ySiydGySXtx/ANNrsKZaxqNvREp19Zf3NUGSsJ/GKPayvZD LJcfXQilCKWzf9eh1CIVkzdM8ngqV6ncKGjRXotZJq3sCuZXxrWiFqr8H8HMcATATmm0 uq7W+1WgwdsGPgPSXqdUSCZVIUX2BmiDe4hBaOX0E+lzhAfW0FqDSvFcMpt91aTJK4gT vatw== X-Gm-Message-State: AMCzsaXfsjbOXiS3p1rNY1/+cu9bwKG1mHw5TNs75PAAIqzXIGD0CvzR GiJTRELaCO51tGnIw6LQ7Xb2tjfyokvZAPa/y3wZxw== X-Google-Smtp-Source: AOwi7QAxvUhh4lvamFle5Hib+F9xxB+YBV3TDLcml14XBj9/Ucs1qQS9k9lA1KbhVbd+n9eIcz9qf6UumLluFT4EjkM= X-Received: by 10.36.19.207 with SMTP id 198mr20180523itz.130.1507689556256; Tue, 10 Oct 2017 19:39:16 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Tue, 10 Oct 2017 19:39:15 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:8936:338a:89de:d5ea] In-Reply-To: <20171011023356.GA57571@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> From: Warner Losh Date: Tue, 10 Oct 2017 20:39:15 -0600 X-Google-Sender-Auth: zMg-djZFNzbXz4txpZOxRnwrMz4 Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: bob prohaska Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 02:39:17 -0000 On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > > On an RPI2 model B, invoking? > > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > > > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > > TARGET_ARCH when installing as well. > > Tried it, like so: > root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > > buildworld.log & [1] 1006 > root@www:/usr/src # 1 error > > [1] Exit 2 make -j4 buildworld TARGET_ARCH=armv7 > > buildworld.log > root@www:/usr/src # more *.log > --- buildworld --- > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > TARGET_ARCH. > *** [buildworld] Error code 1 > > make: stopped in /usr/src > > I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various > iterations. Should the variables be set somewhere else, in a config file? > > At this point the kernel is at r324499, along with the sources. Userland > dates from late June (operator error). Kernels build, but could that make > the trouble I'm seeing? Clang -v reports > > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM > 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > Thanks again! uname -a says what? Warner From owner-freebsd-arm@freebsd.org Wed Oct 11 02:41:19 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 832CDE4407F for ; Wed, 11 Oct 2017 02:41:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46EC575F3E for ; Wed, 11 Oct 2017 02:41:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x232.google.com with SMTP id h66so709541ioh.11 for ; Tue, 10 Oct 2017 19:41:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2bG2QlkYsbqALhMeypB4i5mkTnPDWRYZAjaISZMBTVQ=; b=bfsTaO3Bx0gdu6RBE3hGqVfUsrSRuoycYexPU7suiIaPbl8IY2H/K27woRMlRL/jgN A3zfzLCibsnHsip3YGnBcUqiY5ySdKMMWCh0HlT0N8SZRCRHcbS0Wnc/0Dj4wNygpU5f pSaKEt3v59hqvsjmkZLS0qwdRqzK6TgLrinoh/2H6qoNFxTzb1sonpabFdEnLhUTTjE5 uY8mDRSDq+TLT6bSU44NtqY+kRLfhS9IQrpLJ8c2ekiaqEFMMJQOvf+wQaV1cHcsCgef kt9BFbmd7YCBLyT25/m66ebCWmoedHYRxnSlGRUpVPg0gpzih+Ib8ERLmCn43fnSd5mT cpBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2bG2QlkYsbqALhMeypB4i5mkTnPDWRYZAjaISZMBTVQ=; b=i/30eNnnDP71rOQlDufc62W8bOqr/xvfJ7D7oPyZPvrHKHSZE5zeFUM/DKrEtE0pDO M2+7zQpJ/LOU1FnznVfR/a4nebZFtixtc91vAhcV8Rd9X9nYCPuxdgQ1fYUZsidiOl7y HYqosZxFu5TdecjHc/2PzZLq+hVVfYcvVLVMXErWFC0dK2FI4TisKk9opTHCGHIoy0gj lnkdutxpU0nq6IP2/HXg+dMsA3+zJ8Mb9WaNgmwfBojJ/7YbowbcONGwCVOBhwvj2bO9 nnkczvrszt2qMh3+z9aMxY2waTe77XJl2weh9VHEJyTHLFLqVh7d8IihdZ61z7KzzLht /47w== X-Gm-Message-State: AMCzsaU6g28NlP0Cv+w2POQNVAaysKfgpMJ7rsG0v4L/zrgVOwE7k/Bv 386vh2JdzD6OXBsgeyU4VvqXunnBC7BOArvgHIxqmw== X-Google-Smtp-Source: AOwi7QCyA0Deo1H8GFuw9THI0SJ8kNb157q3HYDhkoaMX627+TpjJRVtJxjR47ir4aHAX9tS3n39r610MfyiM1ZUbNs= X-Received: by 10.107.68.6 with SMTP id r6mr21599070ioa.282.1507689678515; Tue, 10 Oct 2017 19:41:18 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Tue, 10 Oct 2017 19:41:17 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:8936:338a:89de:d5ea] In-Reply-To: References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> From: Warner Losh Date: Tue, 10 Oct 2017 20:41:17 -0600 X-Google-Sender-Auth: AYX_kZsbZb04k7LmR0wEq13aM3Y Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: bob prohaska Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 02:41:19 -0000 On Tue, Oct 10, 2017 at 8:39 PM, Warner Losh wrote: > > > On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > >> On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: >> > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: >> > > On an RPI2 model B, invoking? >> > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log >> > >> > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set >> > TARGET_ARCH when installing as well. >> >> Tried it, like so: >> root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > >> buildworld.log & [1] 1006 >> root@www:/usr/src # 1 error >> >> [1] Exit 2 make -j4 buildworld >> TARGET_ARCH=armv7 > buildworld.log >> root@www:/usr/src # more *.log >> --- buildworld --- >> make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set >> TARGET_ARCH. >> *** [buildworld] Error code 1 >> >> make: stopped in /usr/src >> >> I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various >> iterations. Should the variables be set somewhere else, in a config file? >> >> At this point the kernel is at r324499, along with the sources. Userland >> dates from late June (operator error). Kernels build, but could that make >> the trouble I'm seeing? Clang -v reports >> >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on >> LLVM 4.0.0) >> Target: armv6-unknown-freebsd12.0-gnueabihf >> Thread model: posix >> InstalledDir: /usr/bin >> >> Thanks again! > > > uname -a says what? > What happens if you do a build with TARGET_ARCH=armv7? Warner From owner-freebsd-arm@freebsd.org Wed Oct 11 03:00:19 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50B4CE44613 for ; Wed, 11 Oct 2017 03:00:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 078C076778; Wed, 11 Oct 2017 03:00:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9B30Ns0057698 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 10 Oct 2017 20:00:23 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9B30Lx4057697; Tue, 10 Oct 2017 20:00:21 -0700 (PDT) (envelope-from fbsd) Date: Tue, 10 Oct 2017 20:00:21 -0700 From: bob prohaska To: Warner Losh Cc: Ian Lepore , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171011030021.GB57571@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 03:00:19 -0000 On Tue, Oct 10, 2017 at 08:41:17PM -0600, Warner Losh wrote: > On Tue, Oct 10, 2017 at 8:39 PM, Warner Losh wrote: > > > > > > > On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > > > >> On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > >> > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > >> > > On an RPI2 model B, invoking? > >> > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > >> > > >> > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > >> > TARGET_ARCH when installing as well. > >> > >> Tried it, like so: > >> root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > > >> buildworld.log & [1] 1006 > >> root@www:/usr/src # 1 error > >> > >> [1] Exit 2 make -j4 buildworld > >> TARGET_ARCH=armv7 > buildworld.log > >> root@www:/usr/src # more *.log > >> --- buildworld --- > >> make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > >> TARGET_ARCH. > >> *** [buildworld] Error code 1 > >> > >> make: stopped in /usr/src > >> > >> I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various > >> iterations. Should the variables be set somewhere else, in a config file? > >> > >> At this point the kernel is at r324499, along with the sources. Userland > >> dates from late June (operator error). Kernels build, but could that make > >> the trouble I'm seeing? Clang -v reports > >> > >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > >> LLVM 4.0.0) > >> Target: armv6-unknown-freebsd12.0-gnueabihf > >> Thread model: posix > >> InstalledDir: /usr/bin > >> > >> Thanks again! > > > > > > uname -a says what? > > > root@www:/usr/src # root@www:/usr/src # uname -a FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r324499: Tue Oct 10 18:06:39 PDT 2017 root@www.zefox.com:/usr/obj/usr/src/sys/RPI2 arm > What happens if you do a build with TARGET_ARCH=armv7? > root@www:/usr/src # make TARGET_ARCH=armv7 buildworld > buildworld.log make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. root@www:/usr/src # FWIW, /etc/make.conf does not exist. Seemingly the variable isn't recognized. Maybe a config error someplace? Thanks again, bob prohaska From owner-freebsd-arm@freebsd.org Wed Oct 11 05:00:40 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 870D0E46537 for ; Wed, 11 Oct 2017 05:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 754C67D78F for ; Wed, 11 Oct 2017 05:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9B50eg5098157 for ; Wed, 11 Oct 2017 05:00:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 222923] usr.bin/clang/lld fails to compile with arm:armeb and Date: Wed, 11 Oct 2017 05:00:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 05:00:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222923 Bug ID: 222923 Summary: usr.bin/clang/lld fails to compile with arm:armeb and Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: ngie@FreeBSD.org Spotted the following when trying to run "make tinderbox" on universe12a.freebsd.org: /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/tmp/usr/lib/libgcc.a(f= loatundidf.o): In function `__floatundidf':=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/tmp/usr/lib/libgcc.a(f= loatdidf.o): In function `__floatdidf':=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_i2d@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dmul@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_i2d@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dmul@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.armeb/scratch/tmp/ngie/svn/lib/clang/libllvm/libl= lvm.a(regexec.o)=20 /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: additional relocation overflows omitted from the output=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 c++: error: linker command failed with exit code 1 (use -v to see invocatio= n)=20=20=20 --- ld.lld.full ---=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 *** [ld.lld.full] Error code 1=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 make[7]: stopped in /scratch/tmp/ngie/svn/usr.bin/clang/lld=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 1 error=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 make[7]: stopped in /scratch/tmp/ngie/svn/usr.bin/clang/lld=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --- all_subdir_usr.bin/clang/lld ---=20=20=20=20=20=20=20=20=20=20=20=20=20= =20 *** [all_subdir_usr.bin/clang/lld] Error code 2=20 /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/tmp/usr/lib/libgcc.a(flo= atundidf.o): In function `__floatundidf': /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatundidf.c:43: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/tmp/usr/lib/libgcc.a(flo= atdidf.o): In function `__floatdidf': /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_i2d@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dmul@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dadd@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_i2d@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:38: relocation truncated to fit: R_ARM_CALL against symbol `__aeabi_dmul@@FBSDprivate_1.0' defined in .plt section in /scratch/tmp/ngie/obj/arm.arm/scratch/tmp/ngie/svn/lib/clang/libllvm/libllv= m.a(regexec.o) /scratch/tmp/ngie/svn/contrib/compiler-rt/lib/builtins/floatdidf.c:41: additional relocation overflows omitted from the output c++: error: linker command failed with exit code 1 (use -v to see invocatio= n) --- ld.lld.full --- *** [ld.lld.full] Error code 1 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Oct 11 05:15:07 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8399BE46BB7 for ; Wed, 11 Oct 2017 05:15:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 723C57E3F2 for ; Wed, 11 Oct 2017 05:15:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9B5F7dr038058 for ; Wed, 11 Oct 2017 05:15:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 222924] vfork.S doesn't compile with -g --coverage Date: Wed, 11 Oct 2017 05:15:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 05:15:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222924 Bug ID: 222924 Summary: vfork.S doesn't compile with -g --coverage Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: ngie@FreeBSD.org Spotted when running make tinderbox on universe12a.freebsd.org: =3D=3D=3D> lib/libc (obj,all,install) /scratch/tmp/ngie/obj/arm64.aarch64/scratch/tmp/ngie/svn/tmp/usr/bin/ld: er= ror: /scratch/tmp/ngie/svn/lib/libc/aarch64/sys/vfork.S:37: relocation R_AARCH64_CONDBR19 out of range cc: error: linker command failed with exit code 1 (use -v to see invocation) --- libc.so.7.full --- *** [libc.so.7.full] Error code 1 make[6]: stopped in /scratch/tmp/ngie/svn/lib/libc 1 error make[6]: stopped in /scratch/tmp/ngie/svn/lib/libc --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Oct 11 05:22:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C88D9E46F0A for ; Wed, 11 Oct 2017 05:22:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3B7C7E761 for ; Wed, 11 Oct 2017 05:22:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9B5M0Kv052281 for ; Wed, 11 Oct 2017 05:22:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 222925] clang --coverage doesn't work with arm:armv6 and arm:armv7; lib/libclang_rt is installing to the wrong spot Date: Wed, 11 Oct 2017 05:22:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 05:22:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222925 Bug ID: 222925 Summary: clang --coverage doesn't work with arm:armv6 and arm:armv7; lib/libclang_rt is installing to the wrong spot Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: ngie@FreeBSD.org Saw this error with both arm:armv6 and arm:armv7: 9224 /scratch/tmp/ngie/obj/arm.armv6/scratch/tmp/ngie/svn/tmp/usr/bin/ld: /scratch/tmp/ngie/obj/arm.armv6/scratch/tmp/ngie/svn/tmp/usr/lib/clang/5.0.= 0/lib/freebsd/libclang_rt.profile-armhf.a: No such file: No such file or directory 9225 cc: error: linker command failed with exit code 1 (use -v to see invocation) 9226 --- libc.so.7.full --- 9227 *** [libc.so.7.full] Error code 1 Both architectures are being treated like hard float architectures, based o= n a quick peek at contrib/llvm/tools/clang/lib/Driver/ToolChain.cpp : 303 if (TC.getArch() =3D=3D llvm::Triple::arm || TC.getArch() =3D=3D llvm::Triple::armeb) 304 return (arm::getARMFloatABI(TC, Args) =3D=3D arm::FloatABI::Hard && !IsWindows) 305 ? "armhf" 306 : "arm"; --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Oct 11 18:47:38 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47A90E338A8 for ; Wed, 11 Oct 2017 18:47:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2BC57261B for ; Wed, 11 Oct 2017 18:47:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.241.85]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LabZr-1dYUDH0uz9-00mLGy for ; Wed, 11 Oct 2017 20:47:28 +0200 Date: Wed, 11 Oct 2017 20:47:22 +0200 From: "O. Hartmann" To: freebsd-arm@FreeBSD.org Subject: NanoBSD: Cuurent/NANO_ARCH=aarch64: chroot: : No such file or directory Message-ID: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/0KYTMoem+iYcrZV4Rz9nBxK"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ypZfnfxN9OtSXzOPBF0IHYsxWG/+16gwiCQhTtVj4310mpAA4h1 Vdn2z5qR7ss1G+sjClGh//SAvZmNWiV1TtQZYa4UXoFUBVBsi6fPIHp7M6EdiqpQgf3xMmP lf6On4E2MFKy+AuEzE+kkNsbVgcPALdFOMcnk/6Eps5XtH2wMJojhPS3HZIlsmWawm8EXbj VCJUjK91g7xWC3wi/a/dg== X-UI-Out-Filterresults: notjunk:1;V01:K0:9g0YN8wfuko=:aTP0touBEuB8TZjjIXH7mu E7B8KoLZ4VTmKEapoijx3JBKo6d9pbYaUaZzITQhWb+21jxxP7fG//vXaq8Aty1jzHOhv1erA 3cwjOJQ1AHJlQzqpt2LTMw/zJJv3txwlj/qI1U3xSgW7lvze8hxxlS7whi+MgyH2yBq6e/7Qo +7FRJDhO5XItDEoYpIv4z9uW4VDG0s2Q9trMDfLY0S0HYxkzbylSncaG9G9zy+KJYn4en1i0O hZcfA80VJEoxler4t1senOSpBOARWRD27frgv9TcnSQYfAztf3NLBeZZfYJNNA84eUXqwlYQj iPm04ng3rx+mSz2TIcBDfkuQvwFmtBYR95liWQtxzeJucnYeqeZA/rVSxunNVTbnYIANZz4h0 5X+QLxfKCmiFWtbTgQ3KLh5batmxsNvTC9DaYgED6VBpiDQwEPRAd7XkJKXrKu+S1lKgQQ4bP obqRM62j84FmX2ME+E/I9H9lQJG7R3qlCYQSKcUtKlFNLrPh+490J2/RAnA97+O3dBt2/2PuP RMVYanCx4Md3CUd2K75MuWhTPgJ2Ye+5IuSTBsVzXOGoJ4IVytDgdfcy3xysQfIXD6V6WqIOf 50gzIOvP26OjOAzBz2Iy2DN4wr4/oKU3OtJhdVpTGrgmcYgAPAsKL1OJ6UAXUSW8AeGKfyqU4 z6R6kINI18gD0k17cEaNHSZf7L2FpD9aF6bAeEo2/vFeTlLjdJmNOVq5tuZNLLGXF0DrsPf/l R36goJpRiurQN8UsM7q8uEFYarEowi0Go1dmWZiHmqUEpxco4yCiAqClfVivfdmE20r7M9sBL WqKskWNPKo6JQDk0KaP1D5L1FYPkQ== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 18:47:38 -0000 --Sig_/0KYTMoem+iYcrZV4Rz9nBxK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Trying to install a successfully cross compiled FreeBSD (TARGET=3Darm64) as= NanoBSD. NanoBSD is configure using NANO_ARCH=3D"aarch64". Port emulators/qemu-user-static is installed and loaded: 8 1 0xffffffff8243f000 1564 imgact_binmisc.ko When installing NanoBSD's world and then running mtree, the nanobsd script = runs into this error: /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local 283 blocks + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ -f /home/user/Projects/router/nanobsd/mtree/Files.mtree ] + CR 'mtree -eiU -p /' + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc 'mtree -eiU= -p /' chroot: : No such file or directory Is there anything I miss here with the QEMU emulator catching up? Thanks in advance, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/0KYTMoem+iYcrZV4Rz9nBxK Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWd5nOgAKCRDS528fyFhY lJfTAfsEDWK0VYURC747biYxAVq8I2icvWVq3seoggpHY49Kn7f2NyihRBW3YKY3 u7qNL4ivaUAxUsujx59zqPcUumvmAf9etE2mZ66BVlDntWquXFQJJ/tNNKQJJ3d8 qhjZ9A20zCtyMmwnGFg+WMI/gO+qGvLjTJ7cPipQtSt4CkZKdpY8 =LN9s -----END PGP SIGNATURE----- --Sig_/0KYTMoem+iYcrZV4Rz9nBxK-- From owner-freebsd-arm@freebsd.org Wed Oct 11 22:54:55 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DC18E39733 for ; Wed, 11 Oct 2017 22:54:55 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 32143809A9 for ; Wed, 11 Oct 2017 22:54:54 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 114302ba-aed7-11e7-a938-4f970e858fdb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 114302ba-aed7-11e7-a938-4f970e858fdb; Wed, 11 Oct 2017 22:53:59 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9BMrkRp002110; Wed, 11 Oct 2017 16:53:46 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507762426.8386.24.camel@freebsd.org> Subject: Re: NanoBSD: Cuurent/NANO_ARCH=aarch64: chroot: : No such file or directory From: Ian Lepore To: "O. Hartmann" , freebsd-arm@FreeBSD.org Date: Wed, 11 Oct 2017 16:53:46 -0600 In-Reply-To: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> References: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 22:54:55 -0000 On Wed, 2017-10-11 at 20:47 +0200, O. Hartmann wrote: > Trying to install a successfully cross compiled FreeBSD (TARGET=arm64) as NanoBSD. > NanoBSD is configure using NANO_ARCH="aarch64". > > Port emulators/qemu-user-static is installed and loaded: > >  8    1 0xffffffff8243f000 1564     imgact_binmisc.ko > > When installing NanoBSD's world and then running mtree, the nanobsd script runs into this > error: > > /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local > 283 blocks > + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ > -f /home/user/Projects/router/nanobsd/mtree/Files.mtree ] > + CR 'mtree -eiU -p /' > + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc 'mtree -eiU -p /' > chroot: : No such file or directory > I'm not sure how or why it's happening (I've never used nanobsd), but the complaint is about those empty quotes ('') between the pathname and the /bin/sh in the chroot command.  It's trying to run a program named '' and chroot is complaining that it can't find anything named that. -- Ian > Is there anything I miss here with the QEMU emulator catching up? > > Thanks in advance, > > Oliver > From owner-freebsd-arm@freebsd.org Thu Oct 12 13:39:36 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AFA0E29EBA for ; Thu, 12 Oct 2017 13:39:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F13B87767C; Thu, 12 Oct 2017 13:39:35 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([141.89.153.2]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MKKaI-1e0zoP3eIY-001kKE; Thu, 12 Oct 2017 15:39:28 +0200 Date: Thu, 12 Oct 2017 15:39:26 +0200 From: "Hartmann, O." To: Ian Lepore Cc: "O. Hartmann" , freebsd-arm@FreeBSD.org Subject: Re: NanoBSD: Current/NANO_ARCH=aarch64: chroot: : No such file or directory Message-ID: <20171012153922.6e747356@hermann> In-Reply-To: <1507762426.8386.24.camel@freebsd.org> References: <20171011204722.3622d73c@thor.intern.walstatt.dynvpn.de> <1507762426.8386.24.camel@freebsd.org> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:dzes6rBgadw8ie6W8GvZPURrm+8Peh8OqeIG9KKnx8L0/q4bxnm HLuxiOf5dQ+UEJm+sR9W4uVdZetvcPQ2X2ar1FbL7E60Y/dxnLg1ViuC+LQTpX9jn3rHClb +shU4wQ5nDUmUg1YKT0e2icth/gjodGTle4EuHIlR7zMZxhJsLKqPfaNnnUcGmGU53jCSho yid4yCskifAb3anATTNWw== X-UI-Out-Filterresults: notjunk:1;V01:K0:8Y9IukyYNk0=:ZDDNW4SwMKTmfWjohqy1iJ J7aS8JzuoQpAbTSBTYeCtQwtNJQXSpjmv5IYKUt60+eEwiWZcIdfPF6lI30cYzztmkLzzDFdT icklWH+vDQWD4OT4VCi9qzmM1X7cHO2Na4hM6l+dgVZuqnOGnQavVi4g2WuuCDPkIFFu18Mpb 4zb8siO0Ns0VEG2uZA+RXlEZF0lrNBlFct6SWJ52pCi9FQ6gOxTEiN+TRdIPG9RL9XlEDCJmV gztJzJJaInOyDYJBLxQ3fJEG/Cq1I9XIUN2vOEWpnKglWNTc7qo/zuwEEgxIqcAF5PZu2d8J7 E4YKkxv6amN3fg5ZZ91M9+WwIFqEnXaqwRP/YTu0IgS6m0pDpWebKoyX3O/DKFaGGg4YzSoo1 y6238XQr8TcW2lRepNY1g0xVTAT7cUU/o3yg8tdwpwb3urFdqT8cc24xXOGpdhdoqWJ1UMpND GZnDGxybvK4EKeiWa46EJA8ttH1N5nzbbia19Iuw3AInSqm48h40HoZ8B7mqta14eVYA6qsRr zUFA6Ig435GzSF2MsSnZKMhDTvCkpGvxQSsPfk12r6kuy/Dy6G4Lbqg0QfIkfI+ZN6jVzuIzK 8qZbtHEsMJ0/JvhrWAiaBb9dRlIPZhYWvyK2NPdd94JDhD4bostuTXbBCcLEtLqvIuhVStgST ihQWE6l1CWGegiPEi2A4mkO3bS4FfgrOX9JRDnw2heC5WZ/RSmEnViRU4WdBp/glDHZHob1Bl UVinG9ohwDviKPKyHsGTyIUabbD39reFhnXCgpZS3d3SuVpPVDLGr065fuX27omXu+mYT19iX mz5+3vlB9DRdESYzHHhki9o3aOyb094tsvEG38uMyXKEjk0QEW5ymhFoeejxjEkvlsAj/iWPj PD2cC4yMGJ/TI0X3n3IsIroGGSR60R+NAvXb0PNMRngk1L7lE91mMG5oYWWtqh X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2017 13:39:36 -0000 On Wed, 11 Oct 2017 16:53:46 -0600 Ian Lepore wrote: > On Wed, 2017-10-11 at 20:47 +0200, O. Hartmann wrote: > > Trying to install a successfully cross compiled FreeBSD > > (TARGET=3Darm64) as NanoBSD. NanoBSD is configure using > > NANO_ARCH=3D"aarch64". > >=20 > > Port emulators/qemu-user-static is installed and loaded: > >=20 > > =A08=A0=A0=A0=A01 0xffffffff8243f000 1564=A0=A0=A0=A0=A0imgact_binmisc.= ko > >=20 > > When installing NanoBSD's world and then running mtree, the nanobsd > > script runs into this error: > >=20 > > /pool/nanobsd/aarch64/NANO_aarch64/_.w/./boot/loader.conf.local > > 283 blocks > > + [ -n /home/user/Projects/router/nanobsd/mtree/Files.mtree -a \ > > -f /home/user/Projects/router/nanobsd/mtree/Files.mtree > > ] > > + CR 'mtree -eiU -p /' > > + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w '' /bin/sh -exc > > 'mtree -eiU -p /' chroot: : No such file or directory Oops, I confused the output. The correct one is: [ from _.cust.cust_install_files ] ... + chroot /pool/nanobsd/aarch64/NANO_aarch64/_.w /bin/sh -exc 'mtree -eiU -p /' chroot: /bin/sh: No such file or directory The empty '' is due to my (hopeless helpless) attempt to fit-in another variable which was set to an empty string. The error looks to me as chroot does't find the proper shell, /bin/sh, but it has been properly installed: # file _.w/bin/sh _.w/bin/sh: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 12.0 (1200051), FreeBSD-style, stripped # ll _.w/bin/sh 839832 -r-xr-xr-x 1 root wheel uarch 261K 12 Okt. 15:32 _.w/bin/sh NanoBSD works on the native host when building on host arch amd64 for host arch amd64 and I guess it is due to the properly installed OS of the host. I do not get the problem here. qemu_user_static should catch up with the alien binary here - I suppose it does. The absolute path should ensure the use of the right binary ... Regards, Oliver > > =20 >=20 > I'm not sure how or why it's happening (I've never used nanobsd), but > the complaint is about those empty quotes ('') between the pathname > and the /bin/sh in the chroot command. =A0It's trying to run a program > named '' and chroot is complaining that it can't find anything named > that. >=20 > -- Ian >=20 > > Is there anything I miss here with the QEMU emulator catching up? > >=20 > > Thanks in advance, > >=20 > > Oliver > > =20 From owner-freebsd-arm@freebsd.org Fri Oct 13 02:06:04 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59BD5E3A5F6 for ; Fri, 13 Oct 2017 02:06:04 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 221FC6FD1C for ; Fri, 13 Oct 2017 02:06:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9D264oX070927 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 Oct 2017 19:06:05 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9D264Ov070926; Thu, 12 Oct 2017 19:06:04 -0700 (PDT) (envelope-from fbsd) Date: Thu, 12 Oct 2017 19:06:04 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171013020604.GA70845@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171011030021.GB57571@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 02:06:04 -0000 It's starting to look as if the trouble might have little or nothing to do with the armv6-armv7 transition and instead has some other cause. At this point /etc/make.conf contains KERNCONF=RPI2 TARGET=arm TARGET_ARCH=armv7 DESTDIR=/ Buildkernel works, installkernel demanded a DESTDIR and worked once it was added, so /etc/make.conf is being read and acted upon. If make buildworld is invoked, using the make.conf file above, make reports make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. *** [buildworld] Error code 1 I had to reconstruct all of /usr after mistakenly deleting it during an attempted housecleaning. The restored /usr seems to boot normally and builds kernels just fine, but does not allow su to root, so permissions (or something) are not entirely correct. Might this be related to the failure to recognize or act upon the TARGET_ARCH=armv7 setting? /usr/src is at 324562, along with the kernel. Userland dates from late June. Thanks for reading, and any ideas. bob prohaska On Tue, Oct 10, 2017 at 08:00:21PM -0700, bob prohaska wrote: > On Tue, Oct 10, 2017 at 08:41:17PM -0600, Warner Losh wrote: > > On Tue, Oct 10, 2017 at 8:39 PM, Warner Losh wrote: > > > > > > > > > > > On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > > > > > >> On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > > >> > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > >> > > On an RPI2 model B, invoking? > > >> > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > >> > > > >> > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > > >> > TARGET_ARCH when installing as well. > > >> > > >> Tried it, like so: > > >> root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > > > >> buildworld.log & [1] 1006 > > >> root@www:/usr/src # 1 error > > >> > > >> [1] Exit 2 make -j4 buildworld > > >> TARGET_ARCH=armv7 > buildworld.log > > >> root@www:/usr/src # more *.log > > >> --- buildworld --- > > >> make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > > >> TARGET_ARCH. > > >> *** [buildworld] Error code 1 > > >> > > >> make: stopped in /usr/src > > >> > > >> I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various > > >> iterations. Should the variables be set somewhere else, in a config file? > > >> > > >> At this point the kernel is at r324499, along with the sources. Userland > > >> dates from late June (operator error). Kernels build, but could that make > > >> the trouble I'm seeing? Clang -v reports > > >> > > >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > > >> LLVM 4.0.0) > > >> Target: armv6-unknown-freebsd12.0-gnueabihf > > >> Thread model: posix > > >> InstalledDir: /usr/bin > > >> > > >> Thanks again! > > > > > > > > > uname -a says what? > > > > > > root@www:/usr/src # > root@www:/usr/src # uname -a > FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r324499: Tue Oct 10 18:06:39 PDT 2017 root@www.zefox.com:/usr/obj/usr/src/sys/RPI2 arm > > > What happens if you do a build with TARGET_ARCH=armv7? > > > > root@www:/usr/src # make TARGET_ARCH=armv7 buildworld > buildworld.log > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. > root@www:/usr/src # > > FWIW, /etc/make.conf does not exist. Seemingly the variable isn't recognized. > Maybe a config error someplace? > > Thanks again, > > bob prohaska > From owner-freebsd-arm@freebsd.org Fri Oct 13 17:59:36 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 076A2E28AB3 for ; Fri, 13 Oct 2017 17:59:36 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C43406F14B for ; Fri, 13 Oct 2017 17:59:35 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9DHxiQM074258 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 10:59:44 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9DHxheV074257; Fri, 13 Oct 2017 10:59:43 -0700 (PDT) (envelope-from fbsd) Date: Fri, 13 Oct 2017 10:59:43 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171013175943.GA74121@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171013020604.GA70845@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 17:59:36 -0000 It turns out that simply commenting out lines 447-452 in /usr/src/Makefile.inc1 allows buildworld to run, even with no /etc/make.conf in place. This seems like a fairly reckless experiment, but having no better ideas, would anybody hazard a guess as to odds that the resulting userland might be expected to run? Are there any pre-install tests to be tried? At this point the kernel is at r324562, /usr/src is at r324599. Uname -p reports armv7. Thanks for reading, bob prohaska On Thu, Oct 12, 2017 at 07:06:04PM -0700, bob prohaska wrote: > It's starting to look as if the trouble might have little or nothing > to do with the armv6-armv7 transition and instead has some other cause. > > At this point /etc/make.conf contains > KERNCONF=RPI2 > TARGET=arm > TARGET_ARCH=armv7 > DESTDIR=/ > > Buildkernel works, installkernel demanded a DESTDIR and worked once it > was added, so /etc/make.conf is being read and acted upon. > > If make buildworld is invoked, using the make.conf file above, make reports > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. > *** [buildworld] Error code 1 > > I had to reconstruct all of /usr after mistakenly deleting it during an > attempted housecleaning. The restored /usr seems to boot normally and > builds kernels just fine, but does not allow su to root, so permissions > (or something) are not entirely correct. > > Might this be related to the failure to recognize or act upon the > TARGET_ARCH=armv7 setting? /usr/src is at 324562, along with the > kernel. Userland dates from late June. > > Thanks for reading, and any ideas. > > bob prohaska > > On Tue, Oct 10, 2017 at 08:00:21PM -0700, bob prohaska wrote: > > On Tue, Oct 10, 2017 at 08:41:17PM -0600, Warner Losh wrote: > > > On Tue, Oct 10, 2017 at 8:39 PM, Warner Losh wrote: > > > > > > > > > > > > > > > On Tue, Oct 10, 2017 at 8:33 PM, bob prohaska wrote: > > > > > > > >> On Mon, Oct 09, 2017 at 12:19:31PM -0600, Ian Lepore wrote: > > > >> > On Mon, 2017-10-09 at 10:52 -0700, bob prohaska wrote: > > > >> > > On an RPI2 model B, invoking? > > > >> > > make -j4 -DNO_CLEAN MACHINE_ARCH=armv7 buildworld > buildworld.log > > > >> > > > > >> > Never set MACHINE_ARCH when building, use TARGET_ARCH. ?Be sure to set > > > >> > TARGET_ARCH when installing as well. > > > >> > > > >> Tried it, like so: > > > >> root@www:/usr/src # make -j4 buildworld TARGET_ARCH=armv7 > > > > >> buildworld.log & [1] 1006 > > > >> root@www:/usr/src # 1 error > > > >> > > > >> [1] Exit 2 make -j4 buildworld > > > >> TARGET_ARCH=armv7 > buildworld.log > > > >> root@www:/usr/src # more *.log > > > >> --- buildworld --- > > > >> make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set > > > >> TARGET_ARCH. > > > >> *** [buildworld] Error code 1 > > > >> > > > >> make: stopped in /usr/src > > > >> > > > >> I also tried setting TARGET=arm and WITHOUT_SYSTEM_COMPILER=yes in various > > > >> iterations. Should the variables be set somewhere else, in a config file? > > > >> > > > >> At this point the kernel is at r324499, along with the sources. Userland > > > >> dates from late June (operator error). Kernels build, but could that make > > > >> the trouble I'm seeing? Clang -v reports > > > >> > > > >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on > > > >> LLVM 4.0.0) > > > >> Target: armv6-unknown-freebsd12.0-gnueabihf > > > >> Thread model: posix > > > >> InstalledDir: /usr/bin > > > >> > > > >> Thanks again! > > > > > > > > > > > > uname -a says what? > > > > > > > > > root@www:/usr/src # > > root@www:/usr/src # uname -a > > FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r324499: Tue Oct 10 18:06:39 PDT 2017 root@www.zefox.com:/usr/obj/usr/src/sys/RPI2 arm > > > > > What happens if you do a build with TARGET_ARCH=armv7? > > > > > > > root@www:/usr/src # make TARGET_ARCH=armv7 buildworld > buildworld.log > > make[1]: "/usr/src/Makefile.inc1" line 450: To cross-build, set TARGET_ARCH. > > root@www:/usr/src # > > > > FWIW, /etc/make.conf does not exist. Seemingly the variable isn't recognized. > > Maybe a config error someplace? > > > > Thanks again, > > > > bob prohaska > > From owner-freebsd-arm@freebsd.org Fri Oct 13 18:43:30 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41A21E29F06 for ; Fri, 13 Oct 2017 18:43:30 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E631670BE1 for ; Fri, 13 Oct 2017 18:43:28 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6456 invoked from network); 13 Oct 2017 18:36:47 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 13 Oct 2017 18:36:47 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 13 Oct 2017 14:36:47 -0400 (EDT) Received: (qmail 31723 invoked from network); 13 Oct 2017 18:36:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Oct 2017 18:36:47 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 057E5EC807E; Fri, 13 Oct 2017 11:36:46 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Difficulty with armv6 to v7 transition. From: Mark Millard In-Reply-To: <20171013175943.GA74121@www.zefox.net> Date: Fri, 13 Oct 2017 11:36:46 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 18:43:30 -0000 On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > It turns out that simply commenting out lines 447-452 in > /usr/src/Makefile.inc1 allows buildworld to run, even with > no /etc/make.conf in place. For reference: 447 .if make(buildworld) 448 BUILD_ARCH!= uname -p 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} 450 .error To cross-build, set TARGET_ARCH. 451 .endif 452 .endif (I suggest that the .error message include the MACHINE_ARCH text and the BUILD_ARCH text, probably with ""s around each so that empty is easy to see.) I've had problems with Makefiles using != and uname ending up with the MACRO assigned being an empty string despite a command-line uname returning the expected text. For example I've applied the below local work arounds to my /usr/ports/Mk/bsd.port.mk copy as part of setting up to do amd64 -> aarch64 or amd64 -> armv6 cross builds of ports via poudriere (I've not updated to a armv7-targeting vintage sources yet): # Get the operating system type .if !defined(OPSYS) -OPSYS!= ${UNAME} -s +OPSYS!= echo FreeBSD .endif _EXPORTED_VARS+= OPSYS .if !defined(_OSRELEASE) -_OSRELEASE!= ${UNAME} -r +_OSRELEASE!= echo 12.0-CURRENT .endif _EXPORTED_VARS+= _OSRELEASE I was specifically ending up with _OSRELEASE being empty as seen in poudriere prior to the workaround and that was messing up poudriere such that it stopped with an associated message. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Fri Oct 13 18:57:07 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43072E2A1F8 for ; Fri, 13 Oct 2017 18:57:07 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F397F70FF1 for ; Fri, 13 Oct 2017 18:57:06 +0000 (UTC) (envelope-from jim@netgate.com) Received: by mail-ua0-x230.google.com with SMTP id l40so5942617uah.2 for ; Fri, 13 Oct 2017 11:57:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KZJe56yfJHQRoPbdVcQxupMC6AbDtcSm4+A0Rq+7gsE=; b=ncZyJM7GDG4oN7TwAtCxz3hknX6dreSw9kxPAUol2E3qspkZaZZCt1Vaa/nrykrVvi qfHUaPpfQfB51R2Dl+IurmFJyeVJnT02KpVd7hDV6QyjqSqqVRAwK2ueZgkqAvDwWDNL mnhwUljyYYkkt3jrSY9YFLAGGRIisn6EXFAxc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KZJe56yfJHQRoPbdVcQxupMC6AbDtcSm4+A0Rq+7gsE=; b=R5j5wMv3+LZX4ZtXmFb0XCjdChTKLkBTp6KLZVQZo4NfMSgqB2OwRe/vCO4t/jiIZb DahI8GGaLlnCWZnNUb8TvG353CTsB2TvDm1C16lW3Baorvb9iLAWrACeqTKZ11Vzq0At FBqQ3QJ3mJnPKWX9Bf6GPBnVzXMFMHYZXbX44eGMyC2GAC/KwJmOSXotENKRXqsG0EuT h0i3aqJ7X0YnuqeiomSeZVeUnTcbrcwPOyd2mWEd0SQDFnX8KlVYTR3VXmyc4kwmB1e6 BKqDkNDeiATXGqLGK7euBClbozXzGP1P5HE/7T1mB31B/xCjCTfeec2tLaKdS/8jo6Qv muGA== X-Gm-Message-State: AMCzsaVMR1rNRn958eJALldNMYEHmsgi8rtM2kHH4Jupni2v0xmdBHyi uWhmNtxEazrTmCmVlM97eXDp6M83PfoKm3K67R5k2Q== X-Google-Smtp-Source: AOwi7QAhcltrq/BOGb9asGANVMGKzg/KGdSxHkTQiL2cJAJB16agWlNwkvcRJnvQdTTKG3PoUEP2YJncyCu0HwPjevw= X-Received: by 10.159.56.9 with SMTP id p9mr1999731uad.50.1507921025834; Fri, 13 Oct 2017 11:57:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.141.2 with HTTP; Fri, 13 Oct 2017 11:57:04 -0700 (PDT) In-Reply-To: <201709242207.QAA05638@mail.lariat.net> References: <201709222206.QAA21968@mail.lariat.net> <07D27DD7-2434-4A2E-91CE-A05D12BBAC2A@netgate.com> <201709230004.SAA22590@mail.lariat.net> <4E771B56-D588-468E-AB60-35DB4DB31318@netgate.com> <201709242207.QAA05638@mail.lariat.net> From: Jim Thompson Date: Fri, 13 Oct 2017 13:57:04 -0500 Message-ID: Subject: Re: ARM board recommendations with true GigE ports To: Brett Glass Cc: Marcin Wojtas , Russell Haley , freebsd-arm , Glen Barber Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 18:57:07 -0000 On Sun, Sep 24, 2017 at 5:06 PM, Brett Glass wrote: > So, how would I obtain an image for the Solidrun "ClearFog" board (whose > specs say it uses the Marvell ARMADA 88F628 SoC)? Is it supported by > any of the snapshots of 11.1-RELEASE or 12.0-CURRENT? Or would I have to > set up > a development system to cross-compile? If there's no SD/MMC driver (as > suggested > by some of the messages earlier in the thread), what media would I use to > boot > the system and as mass storage? Is there better support for the > "Macchiatobin" > board, whose specs say it uses a "Marvell AMADA 8040"? > > --Brett Glass =E2=80=8BI don't see where anyone has responded to Brett, (I was in Europe = starting with EuroBSDcon for two weeks, so I didn't notice that the thread had gone stale without answering Brett's question.) Apologies if I missed someone else answering. =E2=80=8BSolid-Run has some documentation specific to FreeBSD on the ClearF= og, including build instructions for FreeBSD=E2=80=8B https://wiki.solid-run.com/doku.php?id=3Dproducts:a38x:software:os:freebsd =E2=80=8B That URL above has a link to pre-built images that Solid-Run has made if that's what you're after.=E2=80=8B http://images.solid-build.xyz/A38X/freebsd/ =E2=80=8BI booted pfSense 2.4.1 (not released, but based on FreeBSD 11.1) f= rom USB on a ClearFog Base (with eMMC) yesterday. =E2=80=8BClearFog Pro works as w= ell. =E2=80=8BWe use a customized toolchain that started off as crochet, but the instructions on that page should serve to get you to freebsd -HEAD running from microSD. Getting from there to FreeBSD 11.1-RELEASE is simple. Since arm32 isn't a tier-1 architecture in FreeBSD, I don't know what it takes to have RE make images for these boards. I know I've given Glen Barber a selection of boards (arm and non-arm) to use in his efforts to make FreeBSD images for various boards, and if it's as simple as sending him a ClearFog, he only needs to hold his hand up. I have about 20 of them sitting in my office. Since Brett mentioned "mass storage", I haven't tried the m-sata on ClearFog, but the m.2 SATA ports on our product based on the Armada 385 work, so presumably the m-sata on the ClearFog also works. The Marvell 8040 stuff is further behind. It boots, but no interfaces, etc= . I'll be trying the espresso.bin board (Armada 3700) next. Jim From owner-freebsd-arm@freebsd.org Fri Oct 13 19:11:12 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F67EE2A691 for ; Fri, 13 Oct 2017 19:11:12 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D603B715FC; Fri, 13 Oct 2017 19:11:11 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id F1044122B3; Fri, 13 Oct 2017 19:11:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 13 Oct 2017 19:11:09 +0000 From: Glen Barber To: Jim Thompson Cc: Brett Glass , Marcin Wojtas , Russell Haley , freebsd-arm Subject: Re: ARM board recommendations with true GigE ports Message-ID: <20171013191109.GP55623@FreeBSD.org> References: <07D27DD7-2434-4A2E-91CE-A05D12BBAC2A@netgate.com> <201709230004.SAA22590@mail.lariat.net> <4E771B56-D588-468E-AB60-35DB4DB31318@netgate.com> <201709242207.QAA05638@mail.lariat.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sy9WyBOsCRoUO165" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 19:11:12 -0000 --sy9WyBOsCRoUO165 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 13, 2017 at 01:57:04PM -0500, Jim Thompson wrote: > On Sun, Sep 24, 2017 at 5:06 PM, Brett Glass wrote: >=20 > > So, how would I obtain an image for the Solidrun "ClearFog" board (whose > > specs say it uses the Marvell ARMADA 88F628 SoC)? Is it supported by > > any of the snapshots of 11.1-RELEASE or 12.0-CURRENT? Or would I have to > > set up > > a development system to cross-compile? If there's no SD/MMC driver (as > > suggested > > by some of the messages earlier in the thread), what media would I use = to > > boot > > the system and as mass storage? Is there better support for the > > "Macchiatobin" > > board, whose specs say it uses a "Marvell AMADA 8040"? > > >=20 >=20 > I don't see where anyone has responded to Brett, (I was in Europe starting > with EuroBSDcon for two weeks, so I didn't notice that the thread had gone > stale without answering Brett's question.) > Apologies if I missed someone else answering. >=20 > Solid-Run has some documentation specific to FreeBSD on the ClearFog, > including build instructions for FreeBSD > https://wiki.solid-run.com/doku.php?id=3Dproducts:a38x:software:os:freebsd >=20 > That URL above has a link to pre-built images that Solid-Run has made if > that's what you're after. > http://images.solid-build.xyz/A38X/freebsd/ >=20 > I booted pfSense 2.4.1 (not released, but based on FreeBSD 11.1) from USB > on a ClearFog Base (with eMMC) yesterday. ClearFog Pro works as well. > We use a customized toolchain that started off as crochet, but the > instructions on that page should serve to get you to freebsd -HEAD running > from microSD. Getting from there to FreeBSD 11.1-RELEASE > is simple. Since arm32 isn't a tier-1 architecture in FreeBSD, I don't > know what it takes to have RE make images for these boards. I know I've > given Glen Barber a selection of boards (arm and non-arm) to > use in his efforts to make FreeBSD images for various boards, and if it's > as simple as sending him a ClearFog, he only needs to hold his hand up. I > have about 20 of them sitting in my office. >=20 > Since Brett mentioned "mass storage", I haven't tried the m-sata on > ClearFog, but the m.2 SATA ports on our product based on the Armada 385 > work, so presumably the m-sata on the ClearFog also works. >=20 > The Marvell 8040 stuff is further behind. It boots, but no interfaces, e= tc. >=20 > I'll be trying the espresso.bin board (Armada 3700) next. >=20 I can look into this early next week. Glen --sy9WyBOsCRoUO165 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEVVuz/A7vpH93hEhKuWzd6q+LXtAFAlnhD8gACgkQuWzd6q+L XtArRBAAxqas6VVISdc4RYD/zuN4zeDGfXFObmC+pT4RYGEV36GzZfB82QAAxCcH Qz+SWBRdfJyAA/04NjJdEoyn1StzjU2OXSr7FcRi5CvQwrOQum5VcZD3knTnO3E7 8NsxP1qAsaBnPO55y7zdfhwzxpnIcnKbB6lBOrlbIqcd3KAO9KieB26+GJ37z9H8 jp6WsWYC7jk4KhbCVWNtCqHE2WD4JaP9bGcEdN67Cf+6AjyrSS4Ddamu4NSlYCBz d2eMDGnXL4jYUvRCGOECW0AJfdO52aePIKN9zD9oJ1u0mXnjRUR0aNi2AUiAZMz2 Zdu2AF1k7JIaaMRJYTd0yPqMge+ycs/I/JBYA32nbGytjBRz99VvRcrKVLe+QK7S MCc17wQEtct2vbSyoZ2tN82zKOIigO/DtWIZEYGQazef2/Z++7T8TRkMuro4ZREb 7kTbf6iLolaQZp5geN50jlmy3gmBsEGNW8Xk8wf5SAbCuRY+IOPmzEs0hJTJJNUg ZWg8U+ZaT2NsANZXeVZN1vD8rQQf0H4vhFijmJG7Vh+W6fFHrysH09LOAADg1l7U NJ5mwmRTaqGEQ6akkqydKjlzwUQlESgGXd6gwNVm5fIZsSTMbDvHNStTmiV6lKx5 7LAr8N5PduxjZPTuH1PSud9DZflwPQvZhVYrhZTxVJY5VpjSKC4= =3+Pf -----END PGP SIGNATURE----- --sy9WyBOsCRoUO165-- From owner-freebsd-arm@freebsd.org Sat Oct 14 01:07:07 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7D88E32202 for ; Sat, 14 Oct 2017 01:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 816958009E for ; Sat, 14 Oct 2017 01:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9E17ETu075402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 18:07:15 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9E17DDt075401; Fri, 13 Oct 2017 18:07:13 -0700 (PDT) (envelope-from fbsd) Date: Fri, 13 Oct 2017 18:07:13 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171014010713.GA75288@www.zefox.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 01:07:07 -0000 Seems it would have been better to replace BUILD_ARCH!= uname -p with BUILD_ARCH!= echo armv7 for present purposes. I'll stop the buildworld in progress and try it. Thank you! bob prohaska On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > > > It turns out that simply commenting out lines 447-452 in > > /usr/src/Makefile.inc1 allows buildworld to run, even with > > no /etc/make.conf in place. > > For reference: > > 447 .if make(buildworld) > 448 BUILD_ARCH!= uname -p > 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} > 450 .error To cross-build, set TARGET_ARCH. > 451 .endif > 452 .endif > > (I suggest that the .error message include the > MACHINE_ARCH text and the BUILD_ARCH text, probably > with ""s around each so that empty is easy to see.) > > > I've had problems with Makefiles using != and uname > ending up with the MACRO assigned being an empty string > despite a command-line uname returning the expected > text. > > For example I've applied the below local work arounds > to my /usr/ports/Mk/bsd.port.mk copy as part of setting > up to do amd64 -> aarch64 or amd64 -> armv6 cross > builds of ports via poudriere (I've not updated to a > armv7-targeting vintage sources yet): > > > # Get the operating system type > .if !defined(OPSYS) > -OPSYS!= ${UNAME} -s > +OPSYS!= echo FreeBSD > .endif > _EXPORTED_VARS+= OPSYS > > .if !defined(_OSRELEASE) > -_OSRELEASE!= ${UNAME} -r > +_OSRELEASE!= echo 12.0-CURRENT > .endif > _EXPORTED_VARS+= _OSRELEASE > > > I was specifically ending up with _OSRELEASE > being empty as seen in poudriere prior to the > workaround and that was messing up poudriere > such that it stopped with an associated > message. > > > === > Mark Millard > markmi at dsl-only.net > From owner-freebsd-arm@freebsd.org Sat Oct 14 01:27:26 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8606E3350E for ; Sat, 14 Oct 2017 01:27:26 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B1E980DFD for ; Sat, 14 Oct 2017 01:27:26 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19555 invoked from network); 14 Oct 2017 01:27:24 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 14 Oct 2017 01:27:24 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 13 Oct 2017 21:27:24 -0400 (EDT) Received: (qmail 23512 invoked from network); 14 Oct 2017 01:27:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 14 Oct 2017 01:27:24 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id C45F7EC9296; Fri, 13 Oct 2017 18:27:23 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Difficulty with armv6 to v7 transition. From: Mark Millard In-Reply-To: <20171014010713.GA75288@www.zefox.net> Date: Fri, 13 Oct 2017 18:27:22 -0700 Cc: freebsd-arm@freebsd.org, bob prohaska Content-Transfer-Encoding: 7bit Message-Id: <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 01:27:27 -0000 On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: > Seems it would have been better to replace > BUILD_ARCH!= uname -p > with > BUILD_ARCH!= echo armv7 > for present purposes. Are you starting under armv6 ? armv7 ? BUILD_ARCH should end up matching what you start under, not the end target as I understand things. If I tried a cross build on a host other than armv7 that BUILD_ARCH result would be wrong. (I use amd64 for cross building aarch64 and arm6 . I'm not up to an armv7 capable context yet and may not be for some time.) That change is a local workaround that is specific to the environment you are using for a build. This is like my 12.0-CURRENT change being specific to my not building on 11.x or 10.x . It is just a local workaround that applies just to a more limited context. I've not figured out what is going on (how/why) for the != uname behavior that I observed. But echoing the expected result instead did work. None of this is appropriate to check-in. > I'll stop the buildworld in progress and try it. Please report if echo of the host type of context appears to make your local environment work vs. not. If it does work then it suggests that != uname -p did not get the expected text for some reason. Older material: On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > >> It turns out that simply commenting out lines 447-452 in >> /usr/src/Makefile.inc1 allows buildworld to run, even with >> no /etc/make.conf in place. > > For reference: > > 447 .if make(buildworld) > 448 BUILD_ARCH!= uname -p > 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} > 450 .error To cross-build, set TARGET_ARCH. > 451 .endif > 452 .endif > > (I suggest that the .error message include the > MACHINE_ARCH text and the BUILD_ARCH text, probably > with ""s around each so that empty is easy to see.) > > > I've had problems with Makefiles using != and uname > ending up with the MACRO assigned being an empty string > despite a command-line uname returning the expected > text. > > For example I've applied the below local work arounds > to my /usr/ports/Mk/bsd.port.mk copy as part of setting > up to do amd64 -> aarch64 or amd64 -> armv6 cross > builds of ports via poudriere (I've not updated to a > armv7-targeting vintage sources yet): > > > # Get the operating system type > .if !defined(OPSYS) > -OPSYS!= ${UNAME} -s > +OPSYS!= echo FreeBSD > .endif > _EXPORTED_VARS+= OPSYS > > .if !defined(_OSRELEASE) > -_OSRELEASE!= ${UNAME} -r > +_OSRELEASE!= echo 12.0-CURRENT > .endif > _EXPORTED_VARS+= _OSRELEASE > > > I was specifically ending up with _OSRELEASE > being empty as seen in poudriere prior to the > workaround and that was messing up poudriere > such that it stopped with an associated > message. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 14 01:53:59 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80F66E34BA4 for ; Sat, 14 Oct 2017 01:53:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-20.reflexion.net [208.70.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40CEE81F57 for ; Sat, 14 Oct 2017 01:53:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 27380 invoked from network); 14 Oct 2017 01:53:58 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 14 Oct 2017 01:53:58 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 13 Oct 2017 21:53:58 -0400 (EDT) Received: (qmail 7667 invoked from network); 14 Oct 2017 01:53:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 14 Oct 2017 01:53:57 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 25943EC8E8B; Fri, 13 Oct 2017 18:53:57 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Difficulty with armv6 to v7 transition. From: Mark Millard In-Reply-To: <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> Date: Fri, 13 Oct 2017 18:53:56 -0700 Cc: freebsd-arm , bob prohaska Content-Transfer-Encoding: quoted-printable Message-Id: <5BD31011-03B0-47F6-B14B-82BDAB9E6B06@dsl-only.net> References: <20171009175216.GA52497@www.zefox.net> <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 01:53:59 -0000 On 2017-Oct-13, at 6:27 PM, Mark Millard wrote: > On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >=20 >> Seems it would have been better to replace >> BUILD_ARCH!=3D uname -p >> with >> BUILD_ARCH!=3D echo armv7 >> for present purposes. Hmm. . . I looked at the history of those lines in this form and they go back to -r84136 (2001-Sep-29). That is the only usage of BUILD_ARCH in the file (at least currently). I doubt that these lines are wrong or were getting the problem that I observed: Otherwise other builds I've done would have failed. My failure context may be specific to poudriere based builds (or poudriere based cross builds). That would leave me guessing that ${MACHINE_ARCH} was not as expected for some reason. Again: I hope that the error message is changed to report the two (or three) strings as well (if possible). You might want to try something like: .error To cross-build, set TARGET_ARCH (MACHINE_ARCH=3D"${MACHINE_ARCH}" = BUILD_ARCH=3D"${BUILD_ARCH}" TARGET_ARCH=3D"${TARGET_ARCH}") with the uname -p in place. The values reported could be useful. (Sorry that I do not currently have a build environment that is appropriate to me to test my own ideas on this.) > Are you starting under armv6 ? armv7 ? > BUILD_ARCH should end up matching what > you start under, not the end target as > I understand things. >=20 > If I tried a cross build on a host > other than armv7 that BUILD_ARCH result > would be wrong. (I use amd64 for cross > building aarch64 and arm6 . I'm not up to > an armv7 capable context yet and may not > be for some time.) >=20 > That change is a local workaround that is > specific to the environment you are using > for a build. >=20 > This is like my 12.0-CURRENT change being > specific to my not building on 11.x or 10.x . > It is just a local workaround that applies > just to a more limited context. >=20 > I've not figured out what is going on (how/why) > for the !=3D uname behavior that I observed. But > echoing the expected result instead did work. >=20 > None of this is appropriate to check-in. >=20 > I'll stop the buildworld in progress and try it. Please report if echo of the host type of context appears to make your local environment work vs. not. If it does work then it suggests that !=3D uname -p did not get the expected text for some reason. Older material: On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > On 2017-Oct-13, at 10:59 AM, bob prohaska = wrote: >=20 >> It turns out that simply commenting out lines 447-452 in=20 >> /usr/src/Makefile.inc1 allows buildworld to run, even with >> no /etc/make.conf in place.=20 >=20 > For reference: >=20 > 447 .if make(buildworld) > 448 BUILD_ARCH!=3D uname -p > 449 .if ${MACHINE_ARCH} !=3D ${BUILD_ARCH} > 450 .error To cross-build, set TARGET_ARCH. > 451 .endif > 452 .endif >=20 > (I suggest that the .error message include the > MACHINE_ARCH text and the BUILD_ARCH text, probably > with ""s around each so that empty is easy to see.) >=20 >=20 > I've had problems with Makefiles using !=3D and uname > ending up with the MACRO assigned being an empty string > despite a command-line uname returning the expected > text. >=20 > For example I've applied the below local work arounds > to my /usr/ports/Mk/bsd.port.mk copy as part of setting > up to do amd64 -> aarch64 or amd64 -> armv6 cross > builds of ports via poudriere (I've not updated to a > armv7-targeting vintage sources yet): >=20 >=20 > # Get the operating system type > .if !defined(OPSYS) > -OPSYS!=3D ${UNAME} -s > +OPSYS!=3D echo FreeBSD > .endif > _EXPORTED_VARS+=3D OPSYS >=20 > .if !defined(_OSRELEASE) > -_OSRELEASE!=3D ${UNAME} -r > +_OSRELEASE!=3D echo 12.0-CURRENT > .endif > _EXPORTED_VARS+=3D _OSRELEASE >=20 >=20 > I was specifically ending up with _OSRELEASE > being empty as seen in poudriere prior to the > workaround and that was messing up poudriere > such that it stopped with an associated > message. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Oct 14 02:11:33 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38BC6E35773 for ; Sat, 14 Oct 2017 02:11:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 026E0826B4 for ; Sat, 14 Oct 2017 02:11:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9E2BYbT075561 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 19:11:34 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9E2BXTA075560; Fri, 13 Oct 2017 19:11:33 -0700 (PDT) (envelope-from fbsd) Date: Fri, 13 Oct 2017 19:11:33 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171014021133.GB75288@www.zefox.net> References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 02:11:33 -0000 On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: > On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: > > > Seems it would have been better to replace > > BUILD_ARCH!= uname -p > > with > > BUILD_ARCH!= echo armv7 > > for present purposes. > > Are you starting under armv6 ? armv7 ? I'm afraid it's a mix, due to some untimely foot-shooting. Uname - p reports armv7, but clang -v reports FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) Target: armv6-unknown-freebsd12.0-gnueabihf Thread model: posix InstalledDir: /usr/bin I'll keep trying to unscramble the mess I've made until an armv7 RPI2 snapshot is released, then start over if necessary. Thanks for reading! bob prohaska > BUILD_ARCH should end up matching what > you start under, not the end target as > I understand things. > > If I tried a cross build on a host > other than armv7 that BUILD_ARCH result > would be wrong. (I use amd64 for cross > building aarch64 and arm6 . I'm not up to > an armv7 capable context yet and may not > be for some time.) > > That change is a local workaround that is > specific to the environment you are using > for a build. > > This is like my 12.0-CURRENT change being > specific to my not building on 11.x or 10.x . > It is just a local workaround that applies > just to a more limited context. > > I've not figured out what is going on (how/why) > for the != uname behavior that I observed. But > echoing the expected result instead did work. > > None of this is appropriate to check-in. > > > I'll stop the buildworld in progress and try it. > > Please report if echo of the host type of context > appears to make your local environment work vs. > not. If it does work then it suggests that > != uname -p did not get the expected text for > some reason. > > Older material: > > On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > > On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > > > >> It turns out that simply commenting out lines 447-452 in > >> /usr/src/Makefile.inc1 allows buildworld to run, even with > >> no /etc/make.conf in place. > > > > For reference: > > > > 447 .if make(buildworld) > > 448 BUILD_ARCH!= uname -p > > 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} > > 450 .error To cross-build, set TARGET_ARCH. > > 451 .endif > > 452 .endif > > > > (I suggest that the .error message include the > > MACHINE_ARCH text and the BUILD_ARCH text, probably > > with ""s around each so that empty is easy to see.) > > > > > > I've had problems with Makefiles using != and uname > > ending up with the MACRO assigned being an empty string > > despite a command-line uname returning the expected > > text. > > > > For example I've applied the below local work arounds > > to my /usr/ports/Mk/bsd.port.mk copy as part of setting > > up to do amd64 -> aarch64 or amd64 -> armv6 cross > > builds of ports via poudriere (I've not updated to a > > armv7-targeting vintage sources yet): > > > > > > # Get the operating system type > > .if !defined(OPSYS) > > -OPSYS!= ${UNAME} -s > > +OPSYS!= echo FreeBSD > > .endif > > _EXPORTED_VARS+= OPSYS > > > > .if !defined(_OSRELEASE) > > -_OSRELEASE!= ${UNAME} -r > > +_OSRELEASE!= echo 12.0-CURRENT > > .endif > > _EXPORTED_VARS+= _OSRELEASE > > > > > > I was specifically ending up with _OSRELEASE > > being empty as seen in poudriere prior to the > > workaround and that was messing up poudriere > > such that it stopped with an associated > > message. > > > === > Mark Millard > markmi at dsl-only.net > From owner-freebsd-arm@freebsd.org Sat Oct 14 04:28:14 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABC49E3C182 for ; Sat, 14 Oct 2017 04:28:14 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47F6730AA for ; Sat, 14 Oct 2017 04:28:14 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id q124so24587333wmb.0 for ; Fri, 13 Oct 2017 21:28:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:reply-to:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=JYeVL+3n5tU8Ys1KymmOUgngulwz4w1/i/qavglOvys=; b=V9RaqLQmukC1EC77Xwvd2j376VsaBtVMHtAgw7jWfDRiaWWakJ+mjFTe5ULSMDmKa5 uAT/3yNfxliBjok8Kq70vqi6/M3tBYPnFsXpfKbYfBCRqAILOZofqDw+XHF9jBruDp2f 82gNSRkXAYnB2dhfHHB4h+U8IFEFDHi6NzN6T29ghWuEHcqSvSJkhoV7dOQxU4LtqoHr pmALfyyOhzj1PLKkHUg0i37m5rmJADPTGXocxMK997gvUOi+3S9bC4JUAUFHm+gkHB3b xbGue7mjhMQyXSUZCVYrtgTnRbkUqV8Jgzu8lSN8tZ4gxiZ5G6pDQDcrqdnAeHcD7ihO K7TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:reply-to:subject:to:cc:references :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=JYeVL+3n5tU8Ys1KymmOUgngulwz4w1/i/qavglOvys=; b=Q5E2hWHIagYv9SPk8fhx+fE0NnsffYds/71egTphnxaIZKDC/Obl13LxwBX6Dn8KDF VZAD5TBYRL1B9b6Tw7ICiZ4X91wud4Y6HC13P1WFQ9AD1ELH2YluGwqA6BI+LP92fmHY 5BtpBnGi6Z4Ms1Doq5kBmKImThgCAkoc5TDcNr2sY0vhfOuyTc+VGx8pmvEpnnm66HO1 jHOex4xhZvjq2uLJCA0bd0ETT5mboF6ZJT+VSo89xo314Gyw+mHdJQ8jGjy+WqW0r0Ff Hq9b4KQ6hq7ZihkyaLX5mzw50u/Id1zqllnKBt1UqNz2Av9u/wyEYJmgY/+iqjH3YWvP 9pNQ== X-Gm-Message-State: AMCzsaWe//QbZ9QSnC0BWatPC8X/HwXZFSFxEzKUSOYO+dsA2Y77Qa1l nDpKlBoT/FQRYQ9MWZvWaddhs+jG5Iw= X-Google-Smtp-Source: ABhQp+SjUpHTxkpKgKF3dmKVWygRXZaIPAtkKY5qNygVC2XvR+Cb/6fYLTbV6shY06BhmYNRa3rSag== X-Received: by 10.28.212.210 with SMTP id l201mr2618598wmg.98.1507955292857; Fri, 13 Oct 2017 21:28:12 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id b15sm1767468wrh.35.2017.10.13.21.28.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Oct 2017 21:28:12 -0700 (PDT) From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: mmel@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. To: bob prohaska , Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> Message-ID: <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> Date: Sat, 14 Oct 2017 06:28:13 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171014021133.GB75288@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 04:28:14 -0000 On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!= uname -p >>> with >>> BUILD_ARCH!= echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=arm TARGET_ARCH=armv7 Michal > >> BUILD_ARCH should end up matching what >> you start under, not the end target as >> I understand things. >> >> If I tried a cross build on a host >> other than armv7 that BUILD_ARCH result >> would be wrong. (I use amd64 for cross >> building aarch64 and arm6 . I'm not up to >> an armv7 capable context yet and may not >> be for some time.) >> >> That change is a local workaround that is >> specific to the environment you are using >> for a build. >> >> This is like my 12.0-CURRENT change being >> specific to my not building on 11.x or 10.x . >> It is just a local workaround that applies >> just to a more limited context. >> >> I've not figured out what is going on (how/why) >> for the != uname behavior that I observed. But >> echoing the expected result instead did work. >> >> None of this is appropriate to check-in. >> >>> I'll stop the buildworld in progress and try it. >> >> Please report if echo of the host type of context >> appears to make your local environment work vs. >> not. If it does work then it suggests that >> != uname -p did not get the expected text for >> some reason. >> >> Older material: >> >> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: >>> On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: >>> >>>> It turns out that simply commenting out lines 447-452 in >>>> /usr/src/Makefile.inc1 allows buildworld to run, even with >>>> no /etc/make.conf in place. >>> >>> For reference: >>> >>> 447 .if make(buildworld) >>> 448 BUILD_ARCH!= uname -p >>> 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} >>> 450 .error To cross-build, set TARGET_ARCH. >>> 451 .endif >>> 452 .endif >>> >>> (I suggest that the .error message include the >>> MACHINE_ARCH text and the BUILD_ARCH text, probably >>> with ""s around each so that empty is easy to see.) >>> >>> >>> I've had problems with Makefiles using != and uname >>> ending up with the MACRO assigned being an empty string >>> despite a command-line uname returning the expected >>> text. >>> >>> For example I've applied the below local work arounds >>> to my /usr/ports/Mk/bsd.port.mk copy as part of setting >>> up to do amd64 -> aarch64 or amd64 -> armv6 cross >>> builds of ports via poudriere (I've not updated to a >>> armv7-targeting vintage sources yet): >>> >>> >>> # Get the operating system type >>> .if !defined(OPSYS) >>> -OPSYS!= ${UNAME} -s >>> +OPSYS!= echo FreeBSD >>> .endif >>> _EXPORTED_VARS+= OPSYS >>> >>> .if !defined(_OSRELEASE) >>> -_OSRELEASE!= ${UNAME} -r >>> +_OSRELEASE!= echo 12.0-CURRENT >>> .endif >>> _EXPORTED_VARS+= _OSRELEASE >>> >>> >>> I was specifically ending up with _OSRELEASE >>> being empty as seen in poudriere prior to the >>> workaround and that was messing up poudriere >>> such that it stopped with an associated >>> message. >> >> >> === >> Mark Millard >> markmi at dsl-only.net >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Sat Oct 14 05:47:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6C6CE3DAF3 for ; Sat, 14 Oct 2017 05:47:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 86EB3642E9; Sat, 14 Oct 2017 05:47:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v9E5l72A076038 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 22:47:08 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v9E5l6WS076037; Fri, 13 Oct 2017 22:47:06 -0700 (PDT) (envelope-from fbsd) Date: Fri, 13 Oct 2017 22:47:06 -0700 From: bob prohaska To: mmel@freebsd.org Cc: Mark Millard , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Difficulty with armv6 to v7 transition. Message-ID: <20171014054706.GC75288@www.zefox.net> References: <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 05:47:00 -0000 Hi Michal, On Sat, Oct 14, 2017 at 06:28:13AM +0200, Michal Meloun wrote: > Bob, > can you please try this? > setenv MACHINE_ARCH armv7; make buildworld TARGET=arm TARGET_ARCH=armv7 > I _believe_ I did try that, with no success, but the scrollback buffer isn't long enough to let me verify it. Right now the machine is running buildworld, using BUILD_ARCH!= echo armv7 in /usr/src/Makefile.inc1 to set BUILD_ARCH. If the buildworld fails I'll try setenv, just to verify. Should know late Saturday or early Sunday. A more immediate puzzle is how to test whether the buildworld command produced an armv7 userland, or something else, before running installworld. I'd hate to trash the system _again_. Running clang -v ought to give a good hint, if I can find the executable. Is there a better test? Thanks! bob prohaska > > > >> BUILD_ARCH should end up matching what > >> you start under, not the end target as > >> I understand things. > >> > >> If I tried a cross build on a host > >> other than armv7 that BUILD_ARCH result > >> would be wrong. (I use amd64 for cross > >> building aarch64 and arm6 . I'm not up to > >> an armv7 capable context yet and may not > >> be for some time.) > >> > >> That change is a local workaround that is > >> specific to the environment you are using > >> for a build. > >> > >> This is like my 12.0-CURRENT change being > >> specific to my not building on 11.x or 10.x . > >> It is just a local workaround that applies > >> just to a more limited context. > >> > >> I've not figured out what is going on (how/why) > >> for the != uname behavior that I observed. But > >> echoing the expected result instead did work. > >> > >> None of this is appropriate to check-in. > >> > >>> I'll stop the buildworld in progress and try it. > >> > >> Please report if echo of the host type of context > >> appears to make your local environment work vs. > >> not. If it does work then it suggests that > >> != uname -p did not get the expected text for > >> some reason. > >> > >> Older material: > >> > >> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: > >>> On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: > >>> > >>>> It turns out that simply commenting out lines 447-452 in > >>>> /usr/src/Makefile.inc1 allows buildworld to run, even with > >>>> no /etc/make.conf in place. > >>> > >>> For reference: > >>> > >>> 447 .if make(buildworld) > >>> 448 BUILD_ARCH!= uname -p > >>> 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} > >>> 450 .error To cross-build, set TARGET_ARCH. > >>> 451 .endif > >>> 452 .endif > >>> > >>> (I suggest that the .error message include the > >>> MACHINE_ARCH text and the BUILD_ARCH text, probably > >>> with ""s around each so that empty is easy to see.) > >>> > >>> > >>> I've had problems with Makefiles using != and uname > >>> ending up with the MACRO assigned being an empty string > >>> despite a command-line uname returning the expected > >>> text. > >>> > >>> For example I've applied the below local work arounds > >>> to my /usr/ports/Mk/bsd.port.mk copy as part of setting > >>> up to do amd64 -> aarch64 or amd64 -> armv6 cross > >>> builds of ports via poudriere (I've not updated to a > >>> armv7-targeting vintage sources yet): > >>> > >>> > >>> # Get the operating system type > >>> .if !defined(OPSYS) > >>> -OPSYS!= ${UNAME} -s > >>> +OPSYS!= echo FreeBSD > >>> .endif > >>> _EXPORTED_VARS+= OPSYS > >>> > >>> .if !defined(_OSRELEASE) > >>> -_OSRELEASE!= ${UNAME} -r > >>> +_OSRELEASE!= echo 12.0-CURRENT > >>> .endif > >>> _EXPORTED_VARS+= _OSRELEASE > >>> > >>> > >>> I was specifically ending up with _OSRELEASE > >>> being empty as seen in poudriere prior to the > >>> workaround and that was messing up poudriere > >>> such that it stopped with an associated > >>> message. > >> > >> > >> === > >> Mark Millard > >> markmi at dsl-only.net > >> > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-arm@freebsd.org Sat Oct 14 06:28:34 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6076E3E754 for ; Sat, 14 Oct 2017 06:28:34 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A596654C5 for ; Sat, 14 Oct 2017 06:28:34 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wr0-x243.google.com with SMTP id k15so1900543wrc.4 for ; Fri, 13 Oct 2017 23:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:reply-to:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=JrDz3l0iSoRujCdb3/9WTBxLBb44n/v79cGYPI4j4SY=; b=cUo1xJeNHtpz4TdSs058Bbw72IkuMLVBeVY8WnMcML0UggL9lXqzKprIokNTAXhb5s 42XPECI7jsJkP6HBwTQAowCK0hgbqrMFhnhcfruh25bSc2YH4T9CgoZOKVjaMwldy8oT 1HxLXSUp3D0Glgyyu5S9CypbDj7BN7/l4/xNErHkMVcVlpzSHnWaz3XPRM/aLOsk3+dt 33azzNgZbwwzMbPbp87cpa2Yr2Xh2QnFo1j9f3E6gfJrfgHhP4Kv7wkByGJ8lbUomIcP b2UIqCj0tAiCbzp3JMjWg0Iz61k3Visdo9dpyMlbhaaPPKMyFv96YVcgERmyzZC3QMMG sV8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:reply-to:subject:to:cc:references :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=JrDz3l0iSoRujCdb3/9WTBxLBb44n/v79cGYPI4j4SY=; b=UjNmfAprp/FoNeJfWjqkbz8PRb4j7zRknHB5nHfLBmEMmwUdfaWI9o/4y8d3h/vcZQ 0yalJSwthGxEBeVkNSLgv8urEKXpXuc18esMejki7eHnYU7vJ91bqiGOcBF6WGQ/E7Kt P2Q4m7rZYsMwQsuNCSQI9YjgQ9ZOH69tA791+i1H7eA0GXlKMp4F7wB5TyvsWTM7Kjmp ltfFsEmFyQQXHbbHgZOE5NDuvu2vVl/+bhp6Uz1PqkXk2w+jpLldk6m5qncuRXJ5U4ZS cAKyoy4odx3J1sEphCePKYb6m74iQ+Xm3E1KZJ0MLb1SUdqRfYGZawJWPH0R3bLwwBy9 tu4g== X-Gm-Message-State: AMCzsaVDAcKx8EFu8O2AzPRI/dD8c9/BPgvJRv2yc0V2E+81x0EJ3aug Dagx9gpj9V9imB2Db/RjUmDtmTOFW3I= X-Google-Smtp-Source: AOwi7QD8mByhSCDQ698+/4rxchsfVtlldHewnKjorc16lIP66ESLBKVuFJ6xc2+/5AE3eLMAwcL0Vg== X-Received: by 10.223.135.21 with SMTP id a21mr2917561wra.245.1507962512731; Fri, 13 Oct 2017 23:28:32 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id m25sm2901373wmi.7.2017.10.13.23.28.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Oct 2017 23:28:32 -0700 (PDT) From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: mmel@freebsd.org Subject: Re: Difficulty with armv6 to v7 transition. To: bob prohaska Cc: Mark Millard , freebsd-arm@freebsd.org, bob prohaska References: <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> <20171014054706.GC75288@www.zefox.net> Message-ID: <559584b5-47c6-b9f8-9fae-43ee76fc99cc@freebsd.org> Date: Sat, 14 Oct 2017 08:28:32 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171014054706.GC75288@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 06:28:35 -0000 On 14.10.2017 7:47, bob prohaska wrote: > Hi Michal, > > On Sat, Oct 14, 2017 at 06:28:13AM +0200, Michal Meloun wrote: >> Bob, >> can you please try this? >> setenv MACHINE_ARCH armv7; make buildworld TARGET=arm TARGET_ARCH=armv7 >> > I _believe_ I did try that, with no success, but the scrollback buffer > isn't long enough to let me verify it. > > Right now the machine is running buildworld, using > BUILD_ARCH!= echo armv7 > in /usr/src/Makefile.inc1 to set BUILD_ARCH. If the > buildworld fails I'll try setenv, just to verify. Should know > late Saturday or early Sunday. > A more immediate puzzle is how to test whether the buildworld command > produced an armv7 userland, or something else, before running installworld. > I'd hate to trash the system _again_. Running clang -v ought to give a > good hint, if I can find the executable. Is there a better test? > For not-installed world executable you can dump ABI version encoded in .note.tag section: ' objdump -s -j .note.tag  //bin/sh' the right binary have something like this: ----------------------------------------------------- /bin/sh:     file format elf32-littlearm Contents of section .note.tag:  814c 08000000 04000000 01000000 46726565  ............Free  815c 42534400 b24f1200 08000000 04000000  BSD..O..........  816c 02000000 46726565 42534400 00000000  ....FreeBSD.....  817c 08000000 06000000 03000000 46726565  ............Free  818c 42534400 61726d76 37000000           BSD.armv7... ------------------------------------------------------- where ' FreeBSD.armv7' is ABI version. For installed world, the next method is 'make -V MACHINE_ARCH -f/dev/null' And for kernel, 'sysctl kern.supported_archs' and 'sysctl  hw.machine_arch' shoul return armv7 > Thanks! > > bob prohaska > > > >>>> BUILD_ARCH should end up matching what >>>> you start under, not the end target as >>>> I understand things. >>>> >>>> If I tried a cross build on a host >>>> other than armv7 that BUILD_ARCH result >>>> would be wrong. (I use amd64 for cross >>>> building aarch64 and arm6 . I'm not up to >>>> an armv7 capable context yet and may not >>>> be for some time.) >>>> >>>> That change is a local workaround that is >>>> specific to the environment you are using >>>> for a build. >>>> >>>> This is like my 12.0-CURRENT change being >>>> specific to my not building on 11.x or 10.x . >>>> It is just a local workaround that applies >>>> just to a more limited context. >>>> >>>> I've not figured out what is going on (how/why) >>>> for the != uname behavior that I observed. But >>>> echoing the expected result instead did work. >>>> >>>> None of this is appropriate to check-in. >>>> >>>>> I'll stop the buildworld in progress and try it. >>>> Please report if echo of the host type of context >>>> appears to make your local environment work vs. >>>> not. If it does work then it suggests that >>>> != uname -p did not get the expected text for >>>> some reason. >>>> >>>> Older material: >>>> >>>> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: >>>>> On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: >>>>> >>>>>> It turns out that simply commenting out lines 447-452 in >>>>>> /usr/src/Makefile.inc1 allows buildworld to run, even with >>>>>> no /etc/make.conf in place. >>>>> For reference: >>>>> >>>>> 447 .if make(buildworld) >>>>> 448 BUILD_ARCH!= uname -p >>>>> 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} >>>>> 450 .error To cross-build, set TARGET_ARCH. >>>>> 451 .endif >>>>> 452 .endif >>>>> >>>>> (I suggest that the .error message include the >>>>> MACHINE_ARCH text and the BUILD_ARCH text, probably >>>>> with ""s around each so that empty is easy to see.) >>>>> >>>>> >>>>> I've had problems with Makefiles using != and uname >>>>> ending up with the MACRO assigned being an empty string >>>>> despite a command-line uname returning the expected >>>>> text. >>>>> >>>>> For example I've applied the below local work arounds >>>>> to my /usr/ports/Mk/bsd.port.mk copy as part of setting >>>>> up to do amd64 -> aarch64 or amd64 -> armv6 cross >>>>> builds of ports via poudriere (I've not updated to a >>>>> armv7-targeting vintage sources yet): >>>>> >>>>> >>>>> # Get the operating system type >>>>> .if !defined(OPSYS) >>>>> -OPSYS!= ${UNAME} -s >>>>> +OPSYS!= echo FreeBSD >>>>> .endif >>>>> _EXPORTED_VARS+= OPSYS >>>>> >>>>> .if !defined(_OSRELEASE) >>>>> -_OSRELEASE!= ${UNAME} -r >>>>> +_OSRELEASE!= echo 12.0-CURRENT >>>>> .endif >>>>> _EXPORTED_VARS+= _OSRELEASE >>>>> >>>>> >>>>> I was specifically ending up with _OSRELEASE >>>>> being empty as seen in poudriere prior to the >>>>> workaround and that was messing up poudriere >>>>> such that it stopped with an associated >>>>> message. >>>> >>>> === >>>> Mark Millard >>>> markmi at dsl-only.net >>>> >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> From owner-freebsd-arm@freebsd.org Sat Oct 14 06:49:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5ED5E3EE70 for ; Sat, 14 Oct 2017 06:49:00 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8208F65D9F for ; Sat, 14 Oct 2017 06:49:00 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io0-x236.google.com with SMTP id i38so11118843iod.2 for ; Fri, 13 Oct 2017 23:49:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qcCn0T4JcazXfOh72iLNzTPPApW8fcI9IxJhKvjKPzg=; b=i3+j0X4xoCH15SLFRp8QonxthTSUoy315oMuVqUg/NHkExD7CXUUYKLZm46Wq5/jkB BNP5RMye8TkXFo5fONv1Iba2Oq1yORH/yju1xvUlAc7Yw3qlOcOhPlgMcp9ATR/kf+xq oSahQjqzVeh8quRPdYGCoS6CkdooRCtGchDKFAOwA6VPGrr8aaYJw0iEB8dOUVSUwluL l1OMtPrPvlnBNSrbLCLXvksfR+j0Xv1F6Y+ByaklmRdLTOO7xeb2oX+gsy1S7CwLh9GM aYv9+3QxeCt6pJPyyJCEeyvfIDKw+hZ5NuFtD/UuEg/IHT9TRUUggGTPL1l8vn2RvIk4 cOLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qcCn0T4JcazXfOh72iLNzTPPApW8fcI9IxJhKvjKPzg=; b=brVLfhJ8FlCYAAi6Sl0rpBRhUPU1WDvSVhLQwO1RsNtabTh2UJjkEp5aSue9tq/HYb 4FjFOQPYrIhg+znY3T7JP41E0M3+13iR1o8IDNKwa6n1S48RDKapX9tjAs0hXqUSW1fx Hjl7vVB79iJ3rPa/UITbYMoOC3GfW33/1IFTqtK/Q7lPw0C21iLVHZDq90r3/SPdB42P AuMOSs1XGFrtjHtLq3ezZF6hqKiFTWwMzzoJhqePd4RwQSO9MSbxfPYhH4w+ZSwCPyoF FwBhfky0CF4r8iyqv8gggZOsHLfjEfvYMfOQ7248Uvb2jtPTGgOYZL+IZ4Ba6THYhLls xMTA== X-Gm-Message-State: AMCzsaX70KGjwHX7LZizJSKablGCrOL9hArBf7lq/BrmMBysO/hpXvWD VeE1MzjnR6qvzOYb2XHfY5cu5S/MAKteA5Ij+jHfpmie+jM= X-Google-Smtp-Source: AOwi7QBuxW+a+VuZE0wFAEK+fQp+zJyAVTQyq64eAMj73ArtGq8booA2A0FGrNMvGaNIpRqgsWFhnE/LSBXT4xcnn7w= X-Received: by 10.107.68.10 with SMTP id r10mr4720693ioa.202.1507963739554; Fri, 13 Oct 2017 23:48:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.157.141 with HTTP; Fri, 13 Oct 2017 23:48:58 -0700 (PDT) In-Reply-To: References: <201709222206.QAA21968@mail.lariat.net> <07D27DD7-2434-4A2E-91CE-A05D12BBAC2A@netgate.com> <201709230004.SAA22590@mail.lariat.net> <4E771B56-D588-468E-AB60-35DB4DB31318@netgate.com> <201709242207.QAA05638@mail.lariat.net> From: Marcin Wojtas Date: Sat, 14 Oct 2017 08:48:58 +0200 Message-ID: Subject: Re: ARM board recommendations with true GigE ports To: Jim Thompson Cc: Brett Glass , Russell Haley , freebsd-arm , Glen Barber Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 06:49:00 -0000 Hi Jim, 2017-10-13 20:57 GMT+02:00 Jim Thompson : > > On Sun, Sep 24, 2017 at 5:06 PM, Brett Glass wrote: >> >> So, how would I obtain an image for the Solidrun "ClearFog" board (whose >> specs say it uses the Marvell ARMADA 88F628 SoC)? Is it supported by >> any of the snapshots of 11.1-RELEASE or 12.0-CURRENT? Or would I have to >> set up >> a development system to cross-compile? If there's no SD/MMC driver (as >> suggested >> by some of the messages earlier in the thread), what media would I use to >> boot >> the system and as mass storage? Is there better support for the >> "Macchiatobin" >> board, whose specs say it uses a "Marvell AMADA 8040"? >> >> --Brett Glass > > > I don't see where anyone has responded to Brett, (I was in Europe starting > with EuroBSDcon for two weeks, so I didn't notice that the thread had gone > stale without answering Brett's question.) > Apologies if I missed someone else answering. > > Solid-Run has some documentation specific to FreeBSD on the ClearFog, > including build instructions for FreeBSD > https://wiki.solid-run.com/doku.php?id=products:a38x:software:os:freebsd > That URL above has a link to pre-built images that Solid-Run has made if > that's what you're after. > http://images.solid-build.xyz/A38X/freebsd/ I pointed Brett same URL's on September 25th, now I see it was off the lists. > > I booted pfSense 2.4.1 (not released, but based on FreeBSD 11.1) from USB on > a ClearFog Base (with eMMC) yesterday. ClearFog Pro works as well. > We use a customized toolchain that started off as crochet, but the > instructions on that page should serve to get you to freebsd -HEAD running > from microSD. Getting from there to FreeBSD 11.1-RELEASE > is simple. Since arm32 isn't a tier-1 architecture in FreeBSD, I don't > know what it takes to have RE make images for these boards. I know I've > given Glen Barber a selection of boards (arm and non-arm) to > use in his efforts to make FreeBSD images for various boards, and if it's as > simple as sending him a ClearFog, he only needs to hold his hand up. I have > about 20 of them sitting in my office. > > Since Brett mentioned "mass storage", I haven't tried the m-sata on > ClearFog, but the m.2 SATA ports on our product based on the Armada 385 > work, so presumably the m-sata on the ClearFog also works. > > The Marvell 8040 stuff is further behind. It boots, but no interfaces, etc. > Did you run MacchiatoBin? When adding support, we tested normal boot from UEFI - USB, SATA and RTC work fine on HEAD (now the latter should work as runtime service, but I didn't have time to test Andrew T. patches). What firmware did you use? Please check my howto, pointing to the updated sources, which allow to build UEFI image for the board: http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+UEFI+EDK+II > I'll be trying the espresso.bin board (Armada 3700) next. > Ok, please let know how it goes. Marcin From owner-freebsd-arm@freebsd.org Sat Oct 14 16:03:33 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4779CE4A3FF for ; Sat, 14 Oct 2017 16:03:33 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3AFA74074 for ; Sat, 14 Oct 2017 16:03:31 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 33ed03d5-b0f9-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 33ed03d5-b0f9-11e7-a893-25625093991c; Sat, 14 Oct 2017 16:03:23 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9EG3Iv9001643; Sat, 14 Oct 2017 10:03:18 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507996998.77532.4.camel@freebsd.org> Subject: Re: Difficulty with armv6 to v7 transition. From: Ian Lepore To: mmel@freebsd.org, bob prohaska Cc: freebsd-arm@freebsd.org Date: Sat, 14 Oct 2017 10:03:18 -0600 In-Reply-To: <559584b5-47c6-b9f8-9fae-43ee76fc99cc@freebsd.org> References: <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> <20171014054706.GC75288@www.zefox.net> <559584b5-47c6-b9f8-9fae-43ee76fc99cc@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 16:03:33 -0000 On Sat, 2017-10-14 at 08:28 +0200, Michal Meloun wrote: > > On 14.10.2017 7:47, bob prohaska wrote: > > > > Hi Michal, > > > > On Sat, Oct 14, 2017 at 06:28:13AM +0200, Michal Meloun wrote: > > > > > > Bob, > > > can you please try this? > > > setenv MACHINE_ARCH armv7; make buildworld TARGET=arm TARGET_ARCH=armv7 > > > > > I _believe_ I did try that, with no success,  but the scrollback buffer  > > isn't long enough to let me verify it.  > > > > Right now the machine is running buildworld, using  > > BUILD_ARCH!= echo armv7 > > in /usr/src/Makefile.inc1 to set BUILD_ARCH.  If the > > buildworld fails I'll try setenv, just to verify. Should know > > late Saturday or early Sunday. > > A more immediate puzzle is how to test whether the buildworld command > > produced an armv7 userland, or something else, before running installworld. > > I'd hate to trash the system _again_. Running clang -v ought to give a  > > good hint, if I can find the executable. Is there a better test?  > > > For not-installed world executable you can dump ABI version encoded in > .note.tag section: > ' objdump -s -j .note.tag  //bin/sh' > > the right binary have something like this: > ----------------------------------------------------- > /bin/sh:     file format elf32-littlearm > > Contents of section .note.tag: >  814c 08000000 04000000 01000000 46726565  ............Free >  815c 42534400 b24f1200 08000000 04000000  BSD..O.......... >  816c 02000000 46726565 42534400 00000000  ....FreeBSD..... >  817c 08000000 06000000 03000000 46726565  ............Free >  818c 42534400 61726d76 37000000           BSD.armv7... > ------------------------------------------------------- > where ' FreeBSD.armv7' is ABI version. > > For installed world, the next method is 'make -V MACHINE_ARCH -f/dev/null' > And for kernel, 'sysctl kern.supported_archs' and 'sysctl  > hw.machine_arch' shoul return armv7 > > You can also get some info formatted nicely with readelf -A: root@wand:~ # readelf -A /sbin/init Attribute Section: aeabi File Attributes   Tag_CPU_arch: ARM v7   Tag_CPU_arch_profile: Application Profile   Tag_ARM_ISA_use: Yes   Tag_THUMB_ISA_use: 32-bit Thumb   Tag_FP_arch: VFPv3   Tag_Advanced_SIMD_arch: NEONv1   Tag_ABI_PCS_GOT_use: direct   Tag_ABI_PCS_wchar_t: wchar_t size 4   Tag_ABI_FP_denormal: Sign Only   Tag_ABI_FP_exceptions: Needed   Tag_ABI_FP_number_model: IEEE 754   Tag_ABI_align_needed: 8-byte align   Tag_ABI_align_preserved: 8-byte align   Tag_ABI_enum_size: 32-bit   Tag_ABI_VFP_args: AAPCS (VFP variant)   Tag_ABI_optimization_goals: Speed   Tag_ABI_FP_16bit_format: IEEE 754   Tag_conformance: 2.09 When doing it to check before installworld, be sure to check the new one in $OBJDIRPREFIX/arm.armv7//src/sbin/init/init -- Ian From owner-freebsd-arm@freebsd.org Sat Oct 14 16:43:02 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7452EE4AC8B for ; Sat, 14 Oct 2017 16:43:02 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F252174F57; Sat, 14 Oct 2017 16:43:01 +0000 (UTC) (envelope-from eddy.petrisor@gmail.com) Received: by mail-wr0-x244.google.com with SMTP id k15so2428114wrc.4; Sat, 14 Oct 2017 09:43:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0MAoP/VnJE0Nuu8I9ynnJ7dwgBrx6QzWB5yRN1KpSxc=; b=DLxtig1zh9YqKYqWQXUuL2HLU0l0q8zkGc8CuVzIOSu318Pzyh0usUcFp1RkXxv34s 1NvJWAuNASglT+CVQ4cqudf49pFs6BVIu7rONl/+aSPVe8hawuDTBuHMX0D4gPf8bwXR ExgeIEq5FYIb22llvOtJvm3sZhs75NFum2/Uz926y6jkZz7sSXb+uMHAplumuSCCOo3r obhk3lLskUAi1J2HAAtNI3HdZ739meYmqv5oFbVBPyIJmL4Q24/FH+h+OFR41i40LKmE D+bUhngvdEWg0UpjgaeQPG/nTAlp4HBLkWHjEHyvJusVAk8h+UspMDovTwdne6YtQP82 7eRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0MAoP/VnJE0Nuu8I9ynnJ7dwgBrx6QzWB5yRN1KpSxc=; b=GK+8mevmpwAzG1uc4kBqxHhV4WaARAvmr+EfXnmn5EcF+0lmCkmuKvKbMOquAgAT9K 0/RjeSyohbNp3YQa4QJCTkyrIsbZm89stn5BBYqSHm1qtdEN9W/qUiWC9Nj6lffIHIIp q6uokAQpyPVGK7ybuFRmGZlHhQMop3Ns6kbXzUOW36mgvTnjyyM1ekja10tkNBsFbG9b HpmBqur/t4WU8GXxalAlvzendGVpbdD0d1OTDaCJFLHzua0pLNjvCzPZ0+5YF7r4ILqd TLIdec9AnfeS/Ac4kdlquMyWTXg+J67r5tngZ8iQ4nOV/eMQt1Yi1H6VRaRKUQTxquHS r40w== X-Gm-Message-State: AMCzsaW5dqeVYUvQxFmIPDFrAYuPvOqtc9JK+ila7NuOglXYEAJoQzx2 WTC0K9SCFZFLhvIrLge+XRa8IbqgpNXicr853rjxnA== X-Google-Smtp-Source: AOwi7QDoAuDXKfXOidq0yKA2NYk+kq+7D9q3+apMRIr+kausvejVC0nESiItixHbTsHMo0b5p9IcU0bKb65YfWmLU7Q= X-Received: by 10.223.134.212 with SMTP id 20mr3854122wry.81.1507999380180; Sat, 14 Oct 2017 09:43:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.173.129 with HTTP; Sat, 14 Oct 2017 09:42:58 -0700 (PDT) Received: by 10.223.173.129 with HTTP; Sat, 14 Oct 2017 09:42:58 -0700 (PDT) In-Reply-To: <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> From: =?UTF-8?Q?Eddy_Petri=C8=99or?= Date: Sat, 14 Oct 2017 19:42:58 +0300 Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: mmel@freebsd.org Cc: bob prohaska , freebsd-arm@freebsd.org, Mark Millard , bob prohaska Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 16:43:02 -0000 Pe 14 oct. 2017 7:28 AM, "Michal Meloun" a scris: On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!= uname -p >>> with >>> BUILD_ARCH!= echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=arm TARGET_ARCH=armv7 I have been trying recently to add support for cross building FreeBSD from Linux and concluded that MACHINE is the system on which the build is done. I don't think I found BUILD* meaning yet. Unfortunately I concluded the FreeBSD build system would really benefit from a clean-up in terms of variables and documenting their use. May I suggest creating a wiki page documenting the usage a clean up can be done? Michal > >> BUILD_ARCH should end up matching what >> you start under, not the end target as >> I understand things. >> >> If I tried a cross build on a host >> other than armv7 that BUILD_ARCH result >> would be wrong. (I use amd64 for cross >> building aarch64 and arm6 . I'm not up to >> an armv7 capable context yet and may not >> be for some time.) >> >> That change is a local workaround that is >> specific to the environment you are using >> for a build. >> >> This is like my 12.0-CURRENT change being >> specific to my not building on 11.x or 10.x . >> It is just a local workaround that applies >> just to a more limited context. >> >> I've not figured out what is going on (how/why) >> for the != uname behavior that I observed. But >> echoing the expected result instead did work. >> >> None of this is appropriate to check-in. >> >>> I'll stop the buildworld in progress and try it. >> >> Please report if echo of the host type of context >> appears to make your local environment work vs. >> not. If it does work then it suggests that >> != uname -p did not get the expected text for >> some reason. >> >> Older material: >> >> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: >>> On 2017-Oct-13, at 10:59 AM, bob prohaska wrote: >>> >>>> It turns out that simply commenting out lines 447-452 in >>>> /usr/src/Makefile.inc1 allows buildworld to run, even with >>>> no /etc/make.conf in place. >>> >>> For reference: >>> >>> 447 .if make(buildworld) >>> 448 BUILD_ARCH!= uname -p >>> 449 .if ${MACHINE_ARCH} != ${BUILD_ARCH} >>> 450 .error To cross-build, set TARGET_ARCH. >>> 451 .endif >>> 452 .endif >>> >>> (I suggest that the .error message include the >>> MACHINE_ARCH text and the BUILD_ARCH text, probably >>> with ""s around each so that empty is easy to see.) >>> >>> >>> I've had problems with Makefiles using != and uname >>> ending up with the MACRO assigned being an empty string >>> despite a command-line uname returning the expected >>> text. >>> >>> For example I've applied the below local work arounds >>> to my /usr/ports/Mk/bsd.port.mk copy as part of setting >>> up to do amd64 -> aarch64 or amd64 -> armv6 cross >>> builds of ports via poudriere (I've not updated to a >>> armv7-targeting vintage sources yet): >>> >>> >>> # Get the operating system type >>> .if !defined(OPSYS) >>> -OPSYS!= ${UNAME} -s >>> +OPSYS!= echo FreeBSD >>> .endif >>> _EXPORTED_VARS+= OPSYS >>> >>> .if !defined(_OSRELEASE) >>> -_OSRELEASE!= ${UNAME} -r >>> +_OSRELEASE!= echo 12.0-CURRENT >>> .endif >>> _EXPORTED_VARS+= _OSRELEASE >>> >>> >>> I was specifically ending up with _OSRELEASE >>> being empty as seen in poudriere prior to the >>> workaround and that was messing up poudriere >>> such that it stopped with an associated >>> message. >> >> >> === >> Mark Millard >> markmi at dsl-only.net >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sat Oct 14 16:54:10 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0093CE4AFE1 for ; Sat, 14 Oct 2017 16:54:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB2827549B for ; Sat, 14 Oct 2017 16:54:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x229.google.com with SMTP id j140so13812093itj.1 for ; Sat, 14 Oct 2017 09:54:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=A65PZDry7BTY5dP9kLZi+CNEdNjMCskYAV3pMRyuCE8=; b=OSnc+sef6Uef7M0OA18+yjFxzDr7UKbev9z1+GvJq1OoX6VUcjRaQTQYDOfJKLzLaV rdjFtbjlmqEX+i4FdsCKMkpHUjQwu7dU5OQasmvn/0ILPvlTI95UMubasBZMP9UdRywd MhiLFcYSa7WPrC7dY+CDPUy3fhSGVKMvrcbeM/DGTHML6d+y/mJis00pWrrG34oqDDDJ fyZ70n9X/bynv16fjEqHubdwWONaCeVh1p4n18rnh94t45atZC0f6ryVd+gdZ7BAvXh+ Q4hTQfmA42zGEKtzUVRgte6cwp8K3mot1F4JVoeNMAyWkS2ov+2sF2e5laPsPnOZyXBc 65dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=A65PZDry7BTY5dP9kLZi+CNEdNjMCskYAV3pMRyuCE8=; b=cnZmLkdthumFQOKYCNByaflU0wClt48+vKbAa7HIWl+YJGGCWWCeIl7KXRwIfFnYuh V2zZOGcQi9StcEBY3ZJcw9tME5CZ4pUNZtqHFe/tccq0a3QPNMGA4Lp/lu0NeJoYO3SO 7PNPJxnpdMMhXWfC9DcrqR1HY0LIo4pPCtP7c/Yyhpf5ZYwJLTBdgjnHyOaK/XJQe1Yv V7HnSk+rYlx78snxD4l30CuwLtNpGmOj07Mr79WzdhEGKlmJabUzTEKOh0llbRNk3MZX JExz9n6DD3Nxx8zuWuDWQRTKwhmwETKCkE3EDUCjfN+zJ2KFKDIvsupLteDbbP51DAUD on/w== X-Gm-Message-State: AMCzsaUe/mk15p7k4e88EU1++22mh39Riz1i5r9Z6q/0mBr6tfx0BCFr VKiVhWzxn+aJuH3k2+0gMTtg3molBQCbQMUhcSacfw== X-Google-Smtp-Source: ABhQp+QMh/+RM5STvaLil+0inrEBcKr6msmcgPF9Hi1L1WcVJCwJ2J6K7Crc5QZzQcb34VA5TTDkSHhSJQzZqviniu0= X-Received: by 10.36.69.100 with SMTP id y97mr5460946ita.50.1508000048638; Sat, 14 Oct 2017 09:54:08 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Sat, 14 Oct 2017 09:54:07 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:5085:1a2f:dcb:9d2d] Received: by 10.79.94.130 with HTTP; Sat, 14 Oct 2017 09:54:07 -0700 (PDT) In-Reply-To: References: <1507573171.84167.9.camel@freebsd.org> <20171011023356.GA57571@www.zefox.net> <20171011030021.GB57571@www.zefox.net> <20171013020604.GA70845@www.zefox.net> <20171013175943.GA74121@www.zefox.net> <20171014010713.GA75288@www.zefox.net> <254A2C41-59A9-4E4E-8982-ADDBAE2B5F91@dsl-only.net> <20171014021133.GB75288@www.zefox.net> <39f6419f-48f3-aaec-dfa4-3048c8a893d8@freebsd.org> From: Warner Losh Date: Sat, 14 Oct 2017 10:54:07 -0600 X-Google-Sender-Auth: 9W0iPLOTfHVw7HLrkvOFc07lpEg Message-ID: Subject: Re: Difficulty with armv6 to v7 transition. To: =?UTF-8?Q?Eddy_Petri=C8=99or?= Cc: Michal Meloun , freebsd-arm@freebsd.org, bob prohaska Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 16:54:10 -0000 On Oct 14, 2017 10:43 AM, "Eddy Petri=C8=99or" wr= ote: Pe 14 oct. 2017 7:28 AM, "Michal Meloun" a scris: On 14.10.2017 4:11, bob prohaska wrote: > On Fri, Oct 13, 2017 at 06:27:22PM -0700, Mark Millard wrote: >> On 2017-Oct-13, at 6:07 PM, bob prohaska wrote: >> >>> Seems it would have been better to replace >>> BUILD_ARCH!=3D uname -p >>> with >>> BUILD_ARCH!=3D echo armv7 >>> for present purposes. >> >> Are you starting under armv6 ? armv7 ? > I'm afraid it's a mix, due to some untimely foot-shooting. > > Uname - p reports armv7, but clang -v reports > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) > Target: armv6-unknown-freebsd12.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > > I'll keep trying to unscramble the mess I've made until an armv7 RPI2 > snapshot is released, then start over if necessary. > > Thanks for reading! > > bob prohaska > Bob, can you please try this? setenv MACHINE_ARCH armv7; make buildworld TARGET=3Darm TARGET_ARCH=3Darmv7 I have been trying recently to add support for cross building FreeBSD from Linux and concluded that MACHINE is the system on which the build is done. At the start of the build, yes. But we set it while doing the actual cross build to the target. I don't think I found BUILD* meaning yet. That's because they are internal and should never be messed with. They are a detail we don't commit to keeping. If they matter, we have done something wrong. Unfortunately I concluded the FreeBSD build system would really benefit from a clean-up in terms of variables and documenting their use. May I suggest creating a wiki page documenting the usage a clean up can be done? We do document most of them in build man page. That's what should be updated. It spells this stuff out. Warner Michal > >> BUILD_ARCH should end up matching what >> you start under, not the end target as >> I understand things. >> >> If I tried a cross build on a host >> other than armv7 that BUILD_ARCH result >> would be wrong. (I use amd64 for cross >> building aarch64 and arm6 . I'm not up to >> an armv7 capable context yet and may not >> be for some time.) >> >> That change is a local workaround that is >> specific to the environment you are using >> for a build. >> >> This is like my 12.0-CURRENT change being >> specific to my not building on 11.x or 10.x . >> It is just a local workaround that applies >> just to a more limited context. >> >> I've not figured out what is going on (how/why) >> for the !=3D uname behavior that I observed. But >> echoing the expected result instead did work. >> >> None of this is appropriate to check-in. >> >>> I'll stop the buildworld in progress and try it. >> >> Please report if echo of the host type of context >> appears to make your local environment work vs. >> not. If it does work then it suggests that >> !=3D uname -p did not get the expected text for >> some reason. >> >> Older material: >> >> On Fri, Oct 13, 2017 at 11:36:46AM -0700, Mark Millard wrote: >>> On 2017-Oct-13, at 10:59 AM, bob prohaska wrote= : >>> >>>> It turns out that simply commenting out lines 447-452 in >>>> /usr/src/Makefile.inc1 allows buildworld to run, even with >>>> no /etc/make.conf in place. >>> >>> For reference: >>> >>> 447 .if make(buildworld) >>> 448 BUILD_ARCH!=3D uname -p >>> 449 .if ${MACHINE_ARCH} !=3D ${BUILD_ARCH} >>> 450 .error To cross-build, set TARGET_ARCH. >>> 451 .endif >>> 452 .endif >>> >>> (I suggest that the .error message include the >>> MACHINE_ARCH text and the BUILD_ARCH text, probably >>> with ""s around each so that empty is easy to see.) >>> >>> >>> I've had problems with Makefiles using !=3D and uname >>> ending up with the MACRO assigned being an empty string >>> despite a command-line uname returning the expected >>> text. >>> >>> For example I've applied the below local work arounds >>> to my /usr/ports/Mk/bsd.port.mk copy as part of setting >>> up to do amd64 -> aarch64 or amd64 -> armv6 cross >>> builds of ports via poudriere (I've not updated to a >>> armv7-targeting vintage sources yet): >>> >>> >>> # Get the operating system type >>> .if !defined(OPSYS) >>> -OPSYS!=3D ${UNAME} -s >>> +OPSYS!=3D echo FreeBSD >>> .endif >>> _EXPORTED_VARS+=3D OPSYS >>> >>> .if !defined(_OSRELEASE) >>> -_OSRELEASE!=3D ${UNAME} -r >>> +_OSRELEASE!=3D echo 12.0-CURRENT >>> .endif >>> _EXPORTED_VARS+=3D _OSRELEASE >>> >>> >>> I was specifically ending up with _OSRELEASE >>> being empty as seen in poudriere prior to the >>> workaround and that was messing up poudriere >>> such that it stopped with an associated >>> message. >> >> >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >> > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"