From nobody Thu Mar 14 18:55:13 2024 X-Original-To: freebsd-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 4Twc5V2Pdvz5DbyQ for ; Thu, 14 Mar 2024 18:55:26 +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 4Twc5T2y1Sz4PbL for ; Thu, 14 Mar 2024 18:55:25 +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="c/ZVGSzy"; dkim=pass header.d=quip.cz header.s=private header.b=cT1OAP2L; 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 9264CD7889 for ; Thu, 14 Mar 2024 19:55:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710442514; bh=VLwsYXITTxzzokzRrQIrIopMtVPnqETFyLWcwGPToE4=; h=Date:To:From:Subject; b=c/ZVGSzyFOlf1J+GspMpeNRKCHmud3qO4dFA+Jjh3vb4j7kgniz6ZfQODefVFpilj NuSV+tsxzN7cg3UD11DWH3LJBHQpp2W4z7iEx643xut+sEsIK7c5yCFowXAaa9K5G+ 424XyE1lTQsN0hw85DqvNd+v2sSQKs0jK/MCTdFY= 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 C2C8FD7884 for ; Thu, 14 Mar 2024 19:55:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710442513; bh=VLwsYXITTxzzokzRrQIrIopMtVPnqETFyLWcwGPToE4=; h=Date:To:From:Subject; b=cT1OAP2LchT3jAPXtVpkCF+rFPdbKRpFflOH7fX2nviOnLl5ge2YTdjnniNcN+Ab1 harN0zKmezNJUAoTBZy4nQkMf1luHSwudzcFFhilHDRYrS20MBm5Rg7RFq1fes95oU HXzzGra8+RJfUFmkY8UoLVW+kvhQZjICcfRmHkkw= Message-ID: <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> Date: Thu, 14 Mar 2024 19:55:13 +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 To: "freebsd-ports@FreeBSD.org" Content-Language: en-US From: Miroslav Lachman <000.fbsd@quip.cz> Subject: how to see order of make targets steps in ports tree? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: - X-Spamd-Result: default: False [-1.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; 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)[]; R_SPF_NA(0.00)[no SPF record]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; DMARC_NA(0.00)[quip.cz]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; DKIM_TRACE(0.00)[quip.cz:+] X-Rspamd-Queue-Id: 4Twc5T2y1Sz4PbL 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