From owner-freebsd-ports@freebsd.org  Mon Apr 11 01:34:22 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 DF78CB0AB51
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 11 Apr 2016 01:34:22 +0000 (UTC) (envelope-from wam@hiwaay.net)
Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B332E19DB
 for <freebsd-ports@freebsd.org>; Mon, 11 Apr 2016 01:34:22 +0000 (UTC)
 (envelope-from wam@hiwaay.net)
Received: from kabini1.local (user-24-214-48-39.knology.net [24.214.48.39])
 (authenticated bits=0)
 by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u3B1YKue012718
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-ports@freebsd.org>; Sun, 10 Apr 2016 20:34:21 -0500
Subject: Re: 'porting' AMD compiler suite
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>
Cc: FreeBSD ports list !!!! <freebsd-ports@freebsd.org>
From: "William A. Mahaffey III" <wam@hiwaay.net>
Message-ID: <570AFF1C.9010303@hiwaay.net>
Date: Sun, 10 Apr 2016 20:39:50 -0453.75
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.BSF.2.20.1604101911580.84801@wonkity.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
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 01:34:23 -0000

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/
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>


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 ....

-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.