Becaues of the foolish usage of gcc_secure, those safety options was added by OBS with gcc_secure, without our knowing it. Especially, gcc_secure does this by change gcc to a shell script, and hide the true gcc. This makes a huge amount of confusion for developers and users. So we add these options '-fPIC -D_FORTIFY_SOURCE=2 -O2 -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -Wtrampolines -fsigned-char' directly to nginx.spec. After this, we can confirm the compile options' consistency with or without gcc_secure. Signed-off-by: snoweay <snoweay@163.com> (cherry picked from commit bb0a157ddfef4c1f5f1baa276392f0aae46feddb)
nginx
Description
{When you're done, you can delete the content in this README and update the file with details for others getting started with your repository}
Software Architecture
Software architecture description
Installation
- xxxx
- xxxx
- xxxx
Instructions
- xxxx
- xxxx
- xxxx
Contribution
- Fork the repository
- Create Feat_xxx branch
- Commit your code
- Create Pull Request
Gitee Feature
- You can use Readme_XXX.md to support different languages, such as Readme_en.md, Readme_zh.md
- Gitee blog blog.gitee.com
- Explore open source project https://gitee.com/explore
- The most valuable open source project GVP
- The manual of Gitee https://gitee.com/help
- The most popular members https://gitee.com/gitee-stars/
Description
Languages
HTML
94.9%
Shell
5.1%