Attempt to answer the 'why can I not build /usr/ports/INDEX' FAQ.
This commit is contained in:
parent
91d51b7f45
commit
3f94aa402c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21144
1 changed files with 50 additions and 0 deletions
|
@ -4857,6 +4857,56 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="make-index">
|
||||
<para>I just tried to build <filename>INDEX</filename>
|
||||
using <command>make index</command>, and it failed.
|
||||
Why?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>First, always make sure that you have a completely
|
||||
up-to-date Ports Collection. Errors that affect building
|
||||
<filename>INDEX</filename> from an up-to-date copy of the
|
||||
Ports Collection are high-visibility and are thus almost
|
||||
always fixed immediately.</para>
|
||||
|
||||
<para>However, if you are up-to-date, perhaps you are seeing
|
||||
another problem. <command>make index</command> has a
|
||||
known bug in dealing with incomplete copies of the Ports
|
||||
Collection. It assumes that you have a local copy of every
|
||||
single port that every other port that you have a local copy
|
||||
of depends on. To explain, if you have a copy of
|
||||
<filename>foo/bar</filename> on your disk, and
|
||||
<filename>foo/bar</filename> depends on
|
||||
<filename>baz/quux</filename>, then you must also have
|
||||
a copy of <filename>baz/quux</filename> on your disk, and
|
||||
the ports <filename>baz/quux</filename> depends on, and
|
||||
so on. Otherwise, <command>make index</command> has
|
||||
insufficient information to create its dependency tree.</para>
|
||||
|
||||
<para>This is particularly a problem for &os; users who
|
||||
utilize &man.cvsup.1; to track the Ports Collection but
|
||||
choose not to install certain categories by specifying
|
||||
them in <filename>refuse</filename>. In theory, one
|
||||
should be able to refuse categories, but in practice
|
||||
there are too many ports that depend on ports in other
|
||||
categories. Until someone comes up with a solution for
|
||||
this problem, the general rule is is that if you want to
|
||||
build <filename>INDEX</filename>, you must have a complete
|
||||
copy of the Ports Collection.</para>
|
||||
|
||||
<para>There are rare cases where <filename>INDEX</filename>
|
||||
will not build due to odd cases involving
|
||||
<makevar>WITH_<replaceable>*</replaceable></makevar> or
|
||||
<makevar>WITHOUT_<replaceable>*</replaceable></makevar>
|
||||
variables being set in <filename>make.conf</filename>. If
|
||||
you suspect that this is the case, please try to make
|
||||
<filename>INDEX</filename> with those Makevars turned off
|
||||
before reporting it to &a.ports;.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="find-ldso">
|
||||
<para>Where do I find ld.so?</para>
|
||||
|
|
Loading…
Reference in a new issue