From owner-freebsd-arm@freebsd.org Fri Oct 27 15:28: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 5D023E48887 for ; Fri, 27 Oct 2017 15:28:36 +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 40E576A6C9 for ; Fri, 27 Oct 2017 15:28:36 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 38ae404a-bb2b-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 38ae404a-bb2b-11e7-b50b-53dc5ecda239; Fri, 27 Oct 2017 15:26:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9RFRS4G004410; Fri, 27 Oct 2017 09:27:28 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1509118047.56824.69.camel@freebsd.org> Subject: Re: Make packages for armv7 makes armv6 packages From: Ian Lepore To: Carl Johnson , freebsd-arm@freebsd.org Date: Fri, 27 Oct 2017 09:27:27 -0600 In-Reply-To: <86h8ulntob.fsf@elm.localnet> References: <86lgjxo74h.fsf@elm.localnet> <1509058543.56824.61.camel@freebsd.org> <86h8ulntob.fsf@elm.localnet> 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: Fri, 27 Oct 2017 15:28:36 -0000 On Thu, 2017-10-26 at 20:41 -0700, Carl Johnson wrote: > Ian Lepore writes: > > > > > On Thu, 2017-10-26 at 15:51 -0700, Carl Johnson wrote: > > > > > > I have a 12.0-CURRENT RPI2 system that I have been updating with > > > packages that I build on my amd64 desktop system.  I just tried building > > > armv7 packages to see if the system could be upgraded that way.  I did a > > > buildworld and buildkernel for armv7 and everything worked properly.  I > > > then did a make packages for armv7 and it referenced the files created > > > by the armv7 build, but then built armv6 packages.  The 'pkg info -F' > > > data showed armv6 architecture, and they were placed in the > > > FreeBSD:12.0:armv6 repo directory.   I don't think I did anything wrong, > > > and the commands I used were: > > > > > >   make -j4 KERNCONF=RPI2 TARGET=arm TARGET_ARCH=armv7 buildworld buildkernel > > >   make -j4 KERNCONF=RPI2 TARGET=arm TARGET_ARCH=armv7 packages > > >    > > > I checked the typescript file and the only reference to armv6 was the > > > line where it reports it is creating the the repository in > > > .../FreeBSD:12:armv6/... at the end. > > > > > > Does anybody have any suggestions on what I am missing, or are the > > > packages not implemented yet for armv7?  I have upgraded it several > > > times before this conversion to armv7, so I think my procedure is > > > basically correct.  The svn revision I used for this was r325018, which > > > was the latest at this time. > > > > > > Thanks for any ideas on this. > > I think the problem is that pkg itself hasn't been updated to know > > about armv7.  If you apply this patch to ports-mgmt/pkg > > > > https://bz-attachments.freebsd.org/attachment.cgi?id=187008 > > > > then I think it should create armv7 packages for you. > Thanks, but what is supposed to handle that file?  I see two patches in > there, but I don't know what the other lines are supposed to do. > The extra stuff is subversion properties that are only important if the changes are committed.  The standard patch(1) will ignore that extra stuff, so you can just apply the patches as Boris showed in his reply. -- Ian