'porting' AMD compiler suite

Warren Block wblock at wonkity.com
Mon Apr 11 16:36:57 UTC 2016

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


More information about the freebsd-ports mailing list