From owner-freebsd-ports@freebsd.org  Mon Apr 11 11:58:18 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 4FCDDB0A04D
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 11 Apr 2016 11:58:18 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170])
 (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 18EFE1954
 for <freebsd-ports@freebsd.org>; Mon, 11 Apr 2016 11:58:17 +0000 (UTC)
 (envelope-from mailinglists@toco-domains.de)
Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6])
 by toco-domains.de (Postfix) with ESMTPA id 194431AAF01E;
 Mon, 11 Apr 2016 13:58:14 +0200 (CEST)
Subject: Re: 'porting' AMD compiler suite
To: "William A. Mahaffey III" <wam@hiwaay.net>
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>
Cc: FreeBSD ports list !!!! <freebsd-ports@freebsd.org>
From: Torsten Zuehlsdorff <mailinglists@toco-domains.de>
Message-ID: <570B9155.9090405@toco-domains.de>
Date: Mon, 11 Apr 2016 13:58:13 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <570AFF1C.9010303@hiwaay.net>
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 11:58:18 -0000

On 11.04.2016 03:32, 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/
>> _______________________________________________
>> 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 ....

If everything is the same: try sed. :)

Greetings,
Torsten