This patch was taken from https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00375.html. It is used by propeller-gcc-4. Since the 3.0.3 release of gperf (made in May 2007), the generated func has had the gnu_inline attribute applied to it. The gcc source however has not been updated to include that which has lead to a mismatch. In practice, this hasn't been an issue for two reasons: (1) Before gcc-5, the default standard was (gnu) C89, and gcc does not warn or throw an error in this mode. (2) Starting with gcc-4.8, the compiler driver used to build gcc was changed to C++, and g++ does not warn or throw an error in this mode. This error does show up though when using gcc-5 to build gcc-4.7 or older as then the default is (gnu) C11 and the C compiler driver is used. That failure looks like: In file included from .../gcc-4.7.4/gcc/cp/except.c:990:0: cfns.gperf: At top level: cfns.gperf:101:1: error: 'gnu_inline' attribute present on 'libc_name_p' cfns.gperf:26:14: error: but not here Whether the compiler should always emit this error regardless of the active standard or compiler driver is debatable
aboutsummaryrefslogtreecommitdiff
path: root/gnu/packages/patches/ghostscript-no-header-creationdate.patch
diff options
context:
space:
mode:
authorLeo Famulari <leo@famulari.name>2021-05-09 12:30:10 -0400
committerLeo Famulari <leo@famulari.name>2021-05-09 12:44:27 -0400
commit069399ee9dbf75b7c89583f03346a63b2cfe4ac6 (patch)
tree6f191532d3b6e4f2ff21dcbd2491c73045d233c2 /gnu/packages/patches/ghostscript-no-header-creationdate.patch
parent0f2b5f7f733dbc4c66c1e9f8dbb5189ba6f56a80 (diff)
downloadguix-069399ee9dbf75b7c89583f03346a63b2cfe4ac6.tar.gz
guix-069399ee9dbf75b7c89583f03346a63b2cfe4ac6.zip
gnu: certbot, python-acme: Update to 1.15.0.
* gnu/packages/tls.scm (python-acme, certbot): Update to 1.15.0.
Diffstat (limited to 'gnu/packages/patches/ghostscript-no-header-creationdate.patch')
0 files changed, 0 insertions, 0 deletions