Date: Mon, 11 Apr 2016 13:58:13 +0200 From: Torsten Zuehlsdorff <mailinglists@toco-domains.de> To: "William A. Mahaffey III" <wam@hiwaay.net> Cc: FreeBSD ports list !!!! <freebsd-ports@freebsd.org> Subject: Re: 'porting' AMD compiler suite Message-ID: <570B9155.9090405@toco-domains.de> In-Reply-To: <570AFF1C.9010303@hiwaay.net> References: <570ACDB6.1020703@hiwaay.net> <20160410230338.GB24900@server.rulingia.com> <570AE735.2060606@hiwaay.net> <CAOgwaMtE0710DoB00grPi6D_NMqToxL8rGDqm76QKMS_mD%2BeWA@mail.gmail.com> <570AEE9F.10704@hiwaay.net> <alpine.BSF.2.20.1604101911580.84801@wonkity.com> <570AFF1C.9010303@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?570B9155.9090405>