-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quikc start get some other vendor module error #1923
Comments
Pls. check the https://tengine.taobao.org/document_cn/ngx_http_dubbo_module_cn.html specifically. |
I have reviewed the link you provided, but it does not solve the issue of the URL being invalid. If there is no need to install PCRE and zlib, then this problem does not exist. |
@lianglli This is the result without adding PCRE: checking for PCRE library ... not found
checking for PCRE library in /usr/local/ ... not found
checking for PCRE library in /usr/include/pcre/ ... not found
checking for PCRE library in /usr/pkg/ ... not found
checking for PCRE library in /opt/local/ ... not found
./configure: error: the HTTP rewrite module requires the PCRE library.
You can either disable the module by using --without-http_rewrite_module
option, or install the PCRE library into the system, or build the PCRE library
statically from the source with nginx by using --with-pcre=<path> option. This is the result with adding three modules: adding module in ./modules/mod_dubbo
./configure: error: no ./modules/mod_dubbo/config was found
make: *** No rule to make target 'build', needed by 'default'. Stop.
make: *** No rule to make target 'install'. Stop. |
The above error is [./configure: error: the HTTP rewrite module requires the PCRE library.] specifically. The mod_dubbo does not depend on PCRE. Pls. check the follow build script specifically. |
Ⅰ. Issue Description
quick start url 404
Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
sbin/nginx -V
):uname -a
):The text was updated successfully, but these errors were encountered: