From owner-freebsd-ports@freebsd.org  Mon Apr 11 16:36:57 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@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 73B22B0BD9E
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 11 Apr 2016 16:36:57 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 416A413C5
 for <freebsd-ports@freebsd.org>; Mon, 11 Apr 2016 16:36:57 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3BGatV6014583
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 11 Apr 2016 10:36:55 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3BGat7R014579;
 Mon, 11 Apr 2016 10:36:55 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Mon, 11 Apr 2016 10:36:55 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: "William A. Mahaffey III" <wam@hiwaay.net>
cc: FreeBSD ports list !!!! <freebsd-ports@freebsd.org>
Subject: Re: 'porting' AMD compiler suite
In-Reply-To: <570AFF1C.9010303@hiwaay.net>
Message-ID: <alpine.BSF.2.20.1604111036250.92635@wonkity.com>
References: <570ACDB6.1020703@hiwaay.net>
 <20160410230338.GB24900@server.rulingia.com> <570AE735.2060606@hiwaay.net>
 <CAOgwaMtE0710DoB00grPi6D_NMqToxL8rGDqm76QKMS_mD+eWA@mail.gmail.com>
 <570AEE9F.10704@hiwaay.net> <alpine.BSF.2.20.1604101911580.84801@wonkity.com>
 <570AFF1C.9010303@hiwaay.net>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Mon, 11 Apr 2016 10:36:55 -0600 (MDT)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 16:36:57 -0000

On Sun, 10 Apr 2016, William A. Mahaffey III wrote:

> On 04/10/16 20:22, Warren Block wrote:
>> On Sun, 10 Apr 2016, William A. Mahaffey III wrote:
>> 
>>> Or set the (g)make variable 'MAKE' to gmake & let it propogate ....
>> 
>> What you are doing is, in effect, creating a port.  If you create a real 
>> port, there are numerous tools to deal with just this sort of problem, like 
>> USES=gmake.
>> 
>> The Porter's Handbook describes the whole process of creating a port: 
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
>
> I wasn't planning to go that far to start with, but that could change. I am 
> having to edit a largish # of the source files to comment out '#include 
> <malloc.h>' lines, is there a way to automate that for port/pkg maintenance ? 
> I haven't reviewed the porters-handbook (yet), but I have hit that snag to 
> start with ....

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#slow-patch-automatic-replacements