> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/handbook/di-4-zhang-an-zhuang-ying-yong-cheng-xu-ruan-jian-bao-he-ports/4.8.-ru-he-chu-li-sun-huai-de-port.md).

# 4.8.如何处理损坏的 Port

当某个 Port 无法构建或安装时，可以尝试以下方法：

1. 在 [问题报告数据库](https://www.freebsd.org/support/) 中搜索该 Port 是否有待解决的修复。如果有，实施提议的修复可能会解决该问题。
2. 向 Port 的维护者寻求帮助。在 Port 目录中输入 `make maintainer`，或阅读 Port 的 `Makefile` 以查找维护者的电子邮件地址。记得在发给维护者的电子邮件中包含导致错误的输出信息。

   > **注意**
   >
   > 有些 Port 不是由个人维护，而是由 [邮件列表](https://docs.freebsd.org/en/articles/mailing-list-faq/) 代表的群体维护。许多（但不是所有）此类地址看起来像 <freebsd-listname@FreeBSD.org>。发送邮件时请注意这一点。
   >
   > 特别是，由 <ports@FreeBSD.org> 维护的 Port 并非由特定个人维护。相反，所有的修复和支持都来自订阅该邮件列表的一般社区。总是需要更多的志愿者！

   如果没有收到邮件回复，请按照 [编写 FreeBSD 问题报告](https://docs.freebsd.org/en/articles/problem-reports/) 中的说明使用 Bugzilla 提交 bug 报告。
3. 修复它！[Porter's Handbook](https://docs.freebsd.org/en/books/porters-handbook/) 包含有关 Port 基础设施的详细信息，可用于修复偶尔损坏的 Port，或提交新的 Port。使用 [pkg 管理二进制包](/handbook/di-4-zhang-an-zhuang-ying-yong-cheng-xu-ruan-jian-bao-he-ports/4.4.-shi-yong-pkg-jin-hang-er-jin-zhi-bao-guan-li.md) 中的说明，安装软件包而不是 Port。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://book.bsdcn.org/handbook/di-4-zhang-an-zhuang-ying-yong-cheng-xu-ruan-jian-bao-he-ports/4.8.-ru-he-chu-li-sun-huai-de-port.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.