hf400159 commented on a change in pull request #6442:
URL: https://github.com/apache/apisix/pull/6442#discussion_r813849611



##########
File path: docs/zh/latest/how-to-build.md
##########
@@ -115,7 +115,11 @@ sudo yum install ./apisix/*.rpm
 
 - 4.1 `make deps` 安装 `lualdap` 失败, 错误信息如: `Could not find header file for LDAP`
 
-      解决方案: 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`
+      解决方案: luarocks 支持添加自定义的包地址到项目中。通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 
比如 `luarocks config variables.LDAP_DIR /usr/local/opt/openldap/`,你应该按照下面流程设置:
+      1. 使用包括但不仅限于 `brew` 等工具将 `openldap` 安装到本地;
+      2. 找到你本地安装 `openldap` 的位置。此处注意 M1 芯片的 macOS 中 `brew` 的默认地址是  
`/opt/homebrew/cellar/`,之前的 macOS 默认是 `/usr/local/opt/`;
+      3. 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`。      
+

Review comment:
       del

##########
File path: docs/zh/latest/how-to-build.md
##########
@@ -115,7 +115,11 @@ sudo yum install ./apisix/*.rpm
 
 - 4.1 `make deps` 安装 `lualdap` 失败, 错误信息如: `Could not find header file for LDAP`
 
-      解决方案: 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`
+      解决方案: luarocks 支持添加自定义的包地址到项目中。通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 
比如 `luarocks config variables.LDAP_DIR /usr/local/opt/openldap/`,你应该按照下面流程设置:
+      1. 使用包括但不仅限于 `brew` 等工具将 `openldap` 安装到本地;
+      2. 找到你本地安装 `openldap` 的位置。此处注意 M1 芯片的 macOS 中 `brew` 的默认地址是  
`/opt/homebrew/cellar/`,之前的 macOS 默认是 `/usr/local/opt/`;
+      3. 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`。      

Review comment:
       ```suggestion
         3. 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量,比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`。
   ```

##########
File path: docs/zh/latest/how-to-build.md
##########
@@ -115,7 +115,11 @@ sudo yum install ./apisix/*.rpm
 
 - 4.1 `make deps` 安装 `lualdap` 失败, 错误信息如: `Could not find header file for LDAP`
 
-      解决方案: 通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 比如 `luarocks config 
variables.LDAP_DIR /usr/local/opt/openldap/`
+      解决方案: luarocks 支持添加自定义的包地址到项目中。通过 `luarocks config` 手动设置 `LDAP_DIR` 变量, 
比如 `luarocks config variables.LDAP_DIR /usr/local/opt/openldap/`,你应该按照下面流程设置:
+      1. 使用包括但不仅限于 `brew` 等工具将 `openldap` 安装到本地;
+      2. 找到你本地安装 `openldap` 的位置。此处注意 M1 芯片的 macOS 中 `brew` 的默认地址是  
`/opt/homebrew/cellar/`,之前的 macOS 默认是 `/usr/local/opt/`;

Review comment:
       ```suggestion
         2. 找到 `openldap` 本地安装目录。需要注意,ARM 架构的 macOS 中 `brew` 的默认地址是  
`/opt/homebrew/cellar/`,x86 架构的 macOS 默认是 `/usr/local/opt/`;
   ```

##########
File path: docs/en/latest/how-to-build.md
##########
@@ -119,7 +119,10 @@ Follow the steps below to install Apache APISIX via the 
source release package.
 
   **Note**: If `make deps` fails with "install `lualdap` failed" with an error 
like `Could not find header file for LDAP` try the solution below.
 
-  Solution: Set `LDAP_DIR` with `luarocks config` manually. For example 
`luarocks config variables.LDAP_DIR /usr/local/opt/openldap/`.
+      Solution: luarocks supports adding custom package addresses to the 
project. You can set `LDAP_DIR` with `luarocks config` manually, for example 
`luarocks config variables.LDAP_DIR /usr/local/opt/openldap/`. You should 
config as follows:
+      1. Install `openldap` locally using tools including but not limited to 
'brew';
+      2. Find the location of your local installation of `openldap`. Note here 
that the default address of `brew` in the macOS of the M1 chip is 
`/opt/homebrew/cellar/`, and the previous macOS default is `/usr/local/opt/`;

Review comment:
       Please refer to Chinese for modification.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to