Binutils 2.46 tarball was packaged with 'development=true'.
The binutils 2.46 release tarball incorrectly has 'development=true', causing -Werror to be enabled and builds to fail.
The binutils 2.46 release tarball was packaged with the development variable set to true in bfd/development.sh. This setting enables -Werror by default, causing build failures on systems where warnings are present. The reporter notes that the “with-gold” release was packaged with development=false, suggesting the issue is unintended in the main release.
- proposer
Reports that the binutils 2.46 tarball was packaged with 'development=true', causing build failures due to -Werror being enabled.
“The 'development' variable in bfd/development.sh is set to true, which causes '-Werror' to be enabled by default, resulting in build failures on my system.”
In Details
The development variable in bfd/development.sh controls whether -Werror is enabled by default during the build. Enabling -Werror treats all compiler warnings as errors, causing the build to fail if any warnings are present. This is typically enabled during development but disabled for releases.
For Context
During software builds, compiler warnings can be treated as errors using the -Werror flag. This ensures that the codebase is free of warnings, which can sometimes indicate potential bugs. However, for release tarballs, this is often disabled to allow users with different environments and compiler setups to build the software without encountering errors due to warnings. The development flag usually controls this behavior.