Bug 1666108 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Hey

So this below is my mozconfig file 
---- 
export CC="/usr/bin/gcc-9"
export CXX="/usr/bin/g++-9"

mk_add_options PYTHON=/usr/bin/python3.6

ac_add_options --disable-elf-hack

# Debug builds
ac_add_options --enable-debug
ac_add_options --enable-debug-symbols
# Stricter builds
ac_add_options --enable-warnings-as-errors

# To fix _FORTIFY_SOURCE issues
ac_add_options --disable-hardening
#ac_add_options --enable-optimize
--- 
Steps to reproduce : Build with GCC9 (atleast on linux)
Actual results : 
I receive ALOT(about 1600 warnings of a fresh m-c build) of these warnings :
`cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++`

Expected results : No warnings 
Workaround : Seems that if i change to GCC8 i will not receive these warnings.
Revision 1 by
on 
Hey

So this below is my mozconfig file 
```
export CC="/usr/bin/gcc-9"
export CXX="/usr/bin/g++-9"

mk_add_options PYTHON=/usr/bin/python3.6

ac_add_options --disable-elf-hack

# Debug builds
ac_add_options --enable-debug
ac_add_options --enable-debug-symbols
# Stricter builds
ac_add_options --enable-warnings-as-errors

# To fix _FORTIFY_SOURCE issues
ac_add_options --disable-hardening
#ac_add_options --enable-optimize
```

Steps to reproduce : Build with GCC9 (atleast on linux)
Actual results : 
I receive ALOT(about 1600 warnings of a fresh m-c build) of these warnings :
`cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++`

Expected results : No warnings 
Workaround : Seems that if i change to GCC8 i will not receive these warnings.

Back to Bug 1666108 Comment 0