From nobody Thu Mar 14 19:48:48 2024 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TwdH90FlNz5DhcX for ; Thu, 14 Mar 2024 19:48:53 +0000 (UTC) (envelope-from SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4TwdH759krz4Yfh for ; Thu, 14 Mar 2024 19:48:51 +0000 (UTC) (envelope-from SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=quip.cz header.s=private header.b=tVMEHyDm; dkim=pass header.d=quip.cz header.s=private header.b=MvmxpzF5; dmarc=none; spf=none (mx1.freebsd.org: domain of "SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz" has no SPF policy when checking 94.124.105.4) smtp.mailfrom="SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz" Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 3CDA6D7889; Thu, 14 Mar 2024 20:48:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710445730; bh=95V7q0GIo9+uFyEuMxO0Z7IBCB1vTspMHSHl3ojP7+0=; h=Date:Subject:To:References:From:In-Reply-To; b=tVMEHyDmSJWhDJ0lU8f4xL1gRqnu+ZPWGGOT/8cpSGeMs2rztwat8XC+ibVpF/swT EpuKjGIxNaotbxh5kF2Xtd3sjFZCyHz+k/0vlLAtMIRczkZPpnmmh/3ly+Z98OlhQs UF0byDwRraegDFaYA8Bj/biRcZ8LFZU1OKCOornY= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 18110D7884; Thu, 14 Mar 2024 20:48:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710445729; bh=95V7q0GIo9+uFyEuMxO0Z7IBCB1vTspMHSHl3ojP7+0=; h=Date:Subject:To:References:From:In-Reply-To; b=MvmxpzF51xzVGFJ6F0nh2eLhWqQNBqTJswPNFDn9YPQqGYRCMtsv5Qs00hl65M/Et 55AWHegeHdxhgemz8k50ZAze3arGTLos/gAh2yHvShdr8jMYgBImkwtF8OSob1qmAJ UPaQFxcTuBasKMF/fXMnlGR4xYJITKTgZZXdui30= Message-ID: <689c9c3c-122a-4823-babc-a0d037f4691c@quip.cz> Date: Thu, 14 Mar 2024 20:48:48 +0100 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: how to see order of make targets steps in ports tree? Content-Language: en-US To: Hubert Tournier , ports@freebsd.org References: <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> <8a86080b-6a62-4dbe-8596-e3bc03c4ec63@gmail.com> From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <8a86080b-6a62-4dbe-8596-e3bc03c4ec63@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: - X-Spamd-Result: default: False [-1.99 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_ALLOW(-0.20)[quip.cz:s=private]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; DKIM_TRACE(0.00)[quip.cz:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; DMARC_NA(0.00)[quip.cz]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[ports@freebsd.org]; TAGGED_RCPT(0.00)[]; TO_DN_SOME(0.00)[] X-Rspamd-Queue-Id: 4TwdH759krz4Yfh On 14/03/2024 20:24, Hubert Tournier wrote: > Hello, > > Check this link: > > https://docs.freebsd.org/en/books/porters-handbook/slow-porting/#slow-work > > From what I have seen, shebangfix is done during the patch target. You > use SHEBANG_FILES to specify which files it needs to affect I spent a lot of time reading porters handbook to find detailed information about this, but it is not there. The problem is with databases/mysqltuner - upstream broke mysqltuner.pl by missing shebang line. I created patch to add back the previous "#!/usr/bin/env perl" but it is not later replaced by shebangfix to "#!/usr/local/bin/perl" as I expect (probably is shebangfix executed before). That's why I would like to know "some magic command" which shows me the exact steps executed by "make" I made another patch that adds FreeBSD shebang: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277703 > Le 14/03/2024 à 19:55, Miroslav Lachman a écrit : >> Is there a way to see the order of the executed steps by "make"? >> >> tl;dr: I know "make" will run many targets like fetch, checksum, >> extract, patch... but I would like to see some verbose info about >> these steps, mainly what is the order of the steps when I run "make". >> I tried to create some patch to one the port and it seems like >> "shebangfix" is run before "patch" but I don't know how to see what is >> true order of the targets. >> >> Kind reagards >> Miroslav Lachman >> >