From owner-freebsd-arm@freebsd.org  Sun Oct  8 16:07:17 2017
Return-Path: <owner-freebsd-arm@freebsd.org>
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 <freebsd-arm@mailman.ysv.freebsd.org>;
 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 <freebsd-arm@freebsd.org>; 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 <ian@freebsd.org>
To: Mark Linimon <linimon@lonesome.com>
Cc: freebsd-arm <freebsd-arm@freebsd.org>
Date: Sun, 08 Oct 2017 10:07:13 -0600
In-Reply-To: <20171008053812.GA23271@lonesome.com>
References: <CAC67Hz8kctZyTEW+0qQRVYLzPEK7cG9JXhw90fwHx84fnuwO0w@mail.gmail.com>
 <CANCZdfo-1ngKQSkkW5zjZwMWj0QnVnrf2WaJ68=bh_oNPKZ3hw@mail.gmail.com>
 <CAC67Hz8RxH+Nd0dPbn4qstpFJEkoFWkKpTQ81sX6K3NUuYPDtA@mail.gmail.com>
 <1507403387.86205.286.camel@freebsd.org>
 <CANCZdfpd=E5D03F2CXprYCqS-ghRHhnocYJna7UnB-5vdJDwDg@mail.gmail.com>
 <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." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=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