GCC7

Differences between revisions 34 and 39 (spanning 5 versions)
Revision 34 as of 2017-09-11 06:50:02
Size: 508
Editor: ginggs
Comment:
Revision 39 as of 2018-07-13 18:28:56
Size: 853
Editor: ginggs
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
As of June 2017 with GCC 6, some packages fail autopkgtests on armhf only, due to warnings output to stderr, similar to the following: As of June 2017 with GCC 6, some packages fail autopkgtests on armhf only, due to notes output to stderr similar to the following:
Line 11: Line 11:
Since the release of GCC 7.1, the wording of the notes changed slightly:
{{{note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<const double*, std::vector<double> >’ changed in GCC 7.1}}}

Line 14: Line 18:
 * globjects
Line 20: Line 25:
 * primesieve

Workaround: add the following to '''debian/tests/control'''

{{{Restrictions: allow-stderr}}}

arm gcc 7 abi transition

As of June 2017 with GCC 6, some packages fail autopkgtests on armhf only, due to notes output to stderr similar to the following: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<const double*, std::vector<double> >’ will change in GCC 7.1

See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728

Since the release of GCC 7.1, the wording of the notes changed slightly: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<const double*, std::vector<double> >’ changed in GCC 7.1

Affected packages:

  • glbinding
  • globjects
  • ciftilib
  • fast5
  • shark
  • viennacl
  • mathicgb
  • givaro
  • primesieve

Workaround: add the following to debian/tests/control

Restrictions: allow-stderr

GCC7 (last edited 2018-07-15 07:31:20 by ginggs)