| 59 | |
| 60 | ==== Determining the dependencies of a port ==== |
| 61 | |
| 62 | * A very useful, though not foolproof, technique is to invoke port with the "-t" flag; this will activate the "trace" mode, in which Macports will tell you, after successfully completing each of the stages it goes through: |
| 63 | * if it thinks there are any undeclared dependencies at that stage; |
| 64 | * if it thinks there are any unused dependencies at that stage; |
| 65 | * if any attempts were made to write to files outside of the "sandbox" areas used for fetching patching, configuring, building, testing and destrooting. |
| 66 | * Some ways in which the trace mode can be fooled are: |
| 67 | * if you have the {{{sysutils/coreutils}}} port installed, ports that use configure scripts produced by GNU Autoconf will detect and use the "{{{ginstall}}}" or "{{{install}}}" executable that {{{sysutils/coreutils}}} installs into {{{${prefix}/bin}}}, and trace mode will declare coreutils as an undeclared dependency in the configure stage. This is (almost certainly) false, as the system-provided {{{/usr/bin/install}}} will work just fine. |