'porting' AMD compiler suite

William A. Mahaffey III wam at hiwaay.net
Mon Apr 11 01:34:23 UTC 2016

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

More information about the freebsd-ports mailing list