make[4]: Nothing to be done for 'install-exec-am'. 2023-07-14T13:54:56 make[4]: Nothing to be done for 'install-data-am'. 2023-07-14T13:54:57 >>> host-libfribidi 1.0.9 Downloading 2023-07-14T13:54:57 --2023-07-14 13:54:57-- https://github.com/fribidi/fribidi/releases/download/v1.0.9/fribidi-1.0.9.tar.xz 2023-07-14T13:54:57 Resolving github.com (github.com)... 20.205.243.166 2023-07-14T13:54:58 Connecting to github.com (github.com)|20.205.243.166|:443... connected. 2023-07-14T13:54:59 HTTP request sent, awaiting response... 302 Found

根据你提供的信息，看起来你正在进行一个为 "host-libfribidi" 的操作，并尝试从 GitHub 上下载版本号为 1.0.9 的 fribidi 软件包。

根据日志中的信息，下载请求已经成功连接到了 GitHub，并收到了一个 302 Found 的响应。这意味着 GitHub 返回了一个重定向，可能是将下载链接指向了其他位置。＊＊＊

相关问题

configure: error: 2023-07-14T14:41:02 *** Can't find cairo-pdf.h. You must build Cairo with the pdf 2023-07-14T14:41:02 *** backend enabled. 2023-07-14T14:41:02 package/pkg-generic.mk:218: recipe for target '/home/twdz/hyb/new3566/sdk/rk356x_linux_release_v1.3.0b_20221213/buildroot/output/rockchip_rk3566/build/libgtk3-3.24.33/.stamp_configured' failed

The error message you provided indicates that the configuration process is failing because it cannot find the `cairo-pdf.h` header file. The message suggests that you need to build Cairo with the PDF backend enabled.

To resolve this issue, you can follow these steps:

1. Make sure you have the Cairo library installed on your system. You can install it using the package manager of your Linux distribution. For example, on Ubuntu, you can use the following command:

   sudo apt-get install libcairo2-dev

2. If you already have Cairo installed, ensure that it was built with the PDF backend enabled. If not, you may need to build Cairo from source with the necessary configurations.

3. After ensuring that Cairo is properly installed and configured, try configuring and building your project again. This should resolve the issue related to `cairo-pdf.h` not being found.

If the issue persists or you encounter any other errors, please provide more details about your build environment and the steps you have taken so far, so that I can assist you further.

[root@master huaweicloud-csi-driver-master]# kubectl describe volumesnapshot new-snapshot-demo Name: new-snapshot-demo Namespace: default Labels: <none> Annotations: <none> API Version: snapshot.storage.k8s.io/v1 Kind: VolumeSnapshot Metadata: Creation Timestamp: 2023-07-14T08:39:13Z Generation: 1 Managed Fields: API Version: snapshot.storage.k8s.io/v1 Fields Type: FieldsV1 fieldsV1: f:spec: .: f:source: .: f:persistentVolumeClaimName: f:volumeSnapshotClassName: Manager: kubectl-create Operation: Update Time: 2023-07-14T08:39:13Z Resource Version: 2868683 UID: c5d551aa-03b8-4d5c-bbf1-bf4606a77b08 Spec: Source: Persistent Volume Claim Name: evs-snapshot-pvc Volume Snapshot Class Name: evs-snapshot-class Events: <none>

根据提供的描述信息，我们可以看到以下内容：

- 快照名称为 "new-snapshot-demo"，命名空间为 "default"。
- 创建时间为 "2023-07-14T08:39:13Z"。
- 快照的绑定状态未提供，因此无法确定快照是否已正确绑定到存储卷。
- 快照的配置指定了 `evs-snapshot-pvc` 作为持久卷声明的名称，并且 `evs-snapshot-class` 作为快照类的名称。

根据这些信息，我们仍然无法确定快照是否已正确绑定到存储卷。

为了更好地帮助您解决问题，请提供以下信息：

1. 有关 `evs-snapshot-pvc` 持久卷声明的详细配置，包括 YAML 文件或其他描述文件。

2. 有关 `evs-snapshot-class` 快照类的详细配置，包括 YAML 文件或其他描述文件。

3. 任何与错误或警告消息相关的其他日志或事件。

提供这些信息将使我们能够更准确地分析问题并提供解决方案。非常抱歉给您带来的困惑和不便。