From owner-freebsd-ports@freebsd.org Mon Apr 11 13:09:42 2016 Return-Path: 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 301ADB0C719 for ; Mon, 11 Apr 2016 13:09:42 +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 0319C1360 for ; Mon, 11 Apr 2016 13:09:41 +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 u3BD9dNQ014593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 11 Apr 2016 08:09:40 -0500 Subject: Re: 'porting' AMD compiler suite References: <570ACDB6.1020703@hiwaay.net> <20160410230338.GB24900@server.rulingia.com> <570AE735.2060606@hiwaay.net> <570AEE9F.10704@hiwaay.net> <570AFF1C.9010303@hiwaay.net> <570B9155.9090405@toco-domains.de> Cc: FreeBSD ports list !!!! From: "William A. Mahaffey III" Message-ID: <570BA213.6020608@hiwaay.net> Date: Mon, 11 Apr 2016 08:15:09 -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: <570B9155.9090405@toco-domains.de> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2016 13:09:42 -0000 On 04/11/16 07:04, Torsten Zuehlsdorff wrote: > 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 ' 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 > That's what I did, I was asking if there is some infrastructure in the ports system to automate that sort of stuff for port-maintenance .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.