Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Mar 2024 22:20:23 +0100
From:      Moin Rahman <bofh@freebsd.org>
To:        Miroslav Lachman <000.fbsd@quip.cz>
Cc:        "freebsd-ports@FreeBSD.org" <freebsd-ports@freebsd.org>
Subject:   Re: how to see order of make targets steps in ports tree?
Message-ID:  <D0E257C5-08A1-45BF-95A4-1367864D96BD@freebsd.org>
In-Reply-To: <530b7a49-470c-4437-ba95-ec68bc5ad1a4@quip.cz>
References:  <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> <49B3BF7D-E6B0-409B-B37B-F8F5660E099D@freebsd.org> <8f0601e3-c57f-4d67-8047-1c92088e886d@quip.cz> <B68E3C0A-8FC7-414B-8874-4F11F87415D2@freebsd.org> <530b7a49-470c-4437-ba95-ec68bc5ad1a4@quip.cz>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_50AB719F-8856-4E41-8687-55F3901A3068
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Mar 14, 2024, at 10:08 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>=20
> On 14/03/2024 20:59, Moin Rahman wrote:
>>> On Mar 14, 2024, at 8:57 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>>> On 14/03/2024 20:35, Moin Rahman wrote:
>>>>> On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>>>>>=20
>>>>> Is there a way to see the order of the executed steps by "make"?
>>>>>=20
>>>>> 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.
>>>>>=20
>>>> =E2=9D=AF rg --no-filename '^_USES_patch' Mk | sort
>>>> _USES_patch+=3D 190:pathfix
>>>> _USES_patch+=3D 200:dos2unix
>>>> _USES_patch+=3D 210:fix-shebang
>>>> _USES_patch+=3D 290:gnome-pre-patch
>>>> _USES_patch+=3D 600:charsetfix-post-patch
>>>> _USES_patch+=3D 650:post-patch-erlang
>>>> _USES_patch=3D 701:cabal-post-patch
>>>=20
>>> Good to know this grep! Thanks.
>>> But where is the step using patches from port's "files" directory?
>>>=20
>>> Kind regards
>>> Miroslav Lachman
>> rg do-patch Mk
>=20
> Is this the right order and is this a complete list of targets?
> It seems to me that some things are in the wrong order.
>=20
> # grep -h -rE '[0-9]{3}:' /usr/ports/Mk/ | sed -E =
's/.*=3D[[:space:]]//;s/^[[:space:]]+//;s/ ([0-9]{3}:)/\n\1/g;s/ \\$//' =
| grep -E '^[0-9]{3}:' | sort
> 010:check-build-conflicts
> 050:ask-license
> 050:extract-message
> 050:post-chroot
> 050:stage-message
> 100:build-message
> 100:checksum
> 100:install-message
> 100:package-message
> 100:patch-message
> 100:pre-everything
> 100:stage-dir
> 100:test-message
> 125:show-unsupported-system-error
> 150:build-depends
> 150:check-makefile
> 150:extract-depends
> 150:fetch-depends
> 150:identify-install-conflicts
> 150:patch-depends
> 150:run-depends
> 150:test-depends
> 151:lib-depends
> 160:create-binary-alias
> 161:create-binary-wrappers
> 170:create-base-pkgconfig
> 190:clean-wrkdir
> 190:pathfix
> 190:phpize-message
> 190:show-errors
> 200:${EXTRACT_WRKDIR}
> 200:check-already-installed
> 200:configure-message
> 200:dos2unix
> 200:go-pre-fetch
> 200:show-warnings
> 210:apply-slist
> 210:fix-shebang
> 210:show-dev-errors
> 220:show-dev-warnings
> 250:cargo-configure
> 250:check-categories
> 250:do-phpize
> 250:pear-pre-install
> 260:do-autogenerate-plist
> 270:do-generate-deinstall-script
> 290:${STAGEDIR}${KMODDIR}
> 290:gnome-pre-patch
> 290:start-display
> 291:${STAGEDIR}${KERN_DEBUGDIR}${KMODDIR}
> 295:mate-pre-configure
> 300:check-makevars
> 300:create-manifest
> 300:pre-build
> 300:pre-configure
> 300:pre-extract
> 300:pre-fetch
> 300:pre-install
> 300:pre-package
> 300:pre-patch
> 300:pre-test
> 350:check-desktop-entries
> 400:check-depends
> 400:check-depends-ncurses
> 400:fake-pkg
> 400:generate-plist
> 445:mate-pre-configure-script
> 450:pre-build-script
> 450:pre-configure-script
> 450:pre-extract-script
> 450:pre-fetch-script
> 450:pre-package-script
> 450:pre-patch-script
> 450:pre-su-install
> 450:qmake-configure
> 470:do-autoreconf
> 475:create-users-groups
> 480:patch-libtool
> 490:ap-gen-plist
> 490:run-autotools-fixup
> 500:check-deprecated
> 500:do-build
> 500:do-configure
> 500:do-extract
> 500:do-fetch
> 500:do-install
> 500:do-package
> 500:do-patch
> 500:do-test
> 500:pkg-depends
> 500:security-check
> 520:do-7-zip-extract
> 550:check-vulnerable
> 550:fetch-specials
> 550:kmod-post-install
> 550:pear-post-install
> 560:fix-perl-things
> 590:gem-extract
> 600:cargo-extract
> 600:charsetfix-post-patch
> 600:check-license
> 600:fixup-lib-pkgconfig
> 600:nuget-extract
> 600:webplugin-post-install
> 601:paket-extract
> 601:trigger-post-install
> 650:check-config
> 650:post-patch-erlang
> 690:fonts-install-fontpathd
> 690:gnome-post-gconf-schemas
> 690:gnome-post-omf
> 690:post-extract-gh-DEFAULT
> 690:post-extract-gl-${_group}
> 700:buildanyway-message
> 700:post-build
> 700:post-configure
> 700:post-extract
> 700:post-fetch
> 700:post-install
> 700:post-patch
> 701:cabal-post-extract
> 701:cabal-post-patch
> 701:electronfix-post-install
> 701:remove-common-files
> 720:elfctl-post-build
> 735:ocaml-findlib
> 740:ocaml-ldconfig
> 750:cran-auto-plist
> 750:options-message ${_USES_sanity}
> 750:post-install-script
> 751:cabal-post-install-script
> 751:debuginfo-extract
> 755:cran-strip
> 775:move-uniquefiles
> 790:patch-lafiles
> 800:go-post-extract
> 800:go-post-fetch
> 800:post-stage
> 800:post-test
> 820:gem-autoplist
> 820:kodi-autoplist
> 850:compress-man
> 850:post-build-script
> 850:post-configure-script
> 850:post-extract-script
> 850:post-fetch-script
> 850:post-package-script
> 850:post-patch-script
> 860:install-rc-script
> 860:stop-display
> 870:install-ldconfig-file
> 880:install-license
> 890:install-desktop-entries
> 899:add-pkg-message
> 899:add-plist-phpext
> 900:add-plist-info
> 910:add-plist-docs
> 920:add-plist-examples
> 930:add-plist-data
> 933:add-plist-egginfo
> 934:add-plist-pymod
> 935:add-plist-python
> 940:add-plist-post ${POST_PLIST:C/^/990:/}
> 950:move-uniquefiles-plist
> 995:electronfix-stage-qa
> 995:stage-qa
> 999:extract-fixup-modes
>=20
> Kind regards
> Miroslav Lachman

You are looking at it on a wrong perspective I think.
The numbers matter only within a single target.

So if you consider my earlier examples you will see that we have 701 in =
patch target.

Bu definitely patch target takes place lot earlier in the targets then =
the others in this list.

Kind regards,
Moin


--Apple-Mail=_50AB719F-8856-4E41-8687-55F3901A3068
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmXzahdfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE
Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA
vJGskBAAgWldlAMUiBpIxuQ3W8jsl8QGeQ9u1boIvLOkiLlXtZm4c72oCSmzozwG
9o87c+HjxdMofrbbpQiNQW7BRnaohMvrS1vF5RHOzZyfe3da3eqhKK8ryXHkfUtt
l/NuXwGNSRdNAI9RhPSW8OUqrnCeUpFCztwStaGVAw0rzW33/HAClt9Oo1lc8Bqj
nU6g9Nric5M6OYwGLLITKUpIxITyFsYOjxl/kvF6VNgX386quzU82BtA2zAk33J4
CFCdpS3usO8Cv9YWfSltOESfJ2OAu92LV75bI6h2WCc7r8SZ3I/0ClBDHK8L0koZ
lxrOLbWpYEddJq/M5YHZn4A+iD+RdeIJZrQ9ZamxHcPkIQzp9dIQJrDUu30FmQSF
DrAmdOh1LHhdyouzwwbB2sdAYpR5R8UC3ihvzD1EoI+8aBchpVuL2shxEspeWXz/
U4c4goSmgyPnddcKq14xFrUQkd6h3m47KhNkqXnPM31glo3YJeLxFG+fDCcCshEN
ZHHBtTYsA5mcaphbiYJJ82jNwnE4kSiGBJjmYoUWDVOxbSe5tPUUjiqHZ/tWr4bn
p+2uNgnXr1IZG+eKgfCXBiS8dtDkxDBSItVebmPP11lGyoZIWi7jCyJ1zUTN0fO8
fLzrsGPnCxMSNbeld5Dlq0uLRd3oE9TsAO+YYiZ98ZuxnFC/Hog=
=yr8z
-----END PGP SIGNATURE-----

--Apple-Mail=_50AB719F-8856-4E41-8687-55F3901A3068--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0E257C5-08A1-45BF-95A4-1367864D96BD>