Bug 609366 – net-im/openmittsu-0.9.2_p78 : /.../format.h:2166:24: error: expected unqualified-id before numeric constant

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-02-14 22:20:39 UTC]

                 from /var/tmp/portage/net-im/openmittsu-0.9.2_p78/work/openMittsu-0.9.2_p78/src/Client.cpp:1:
/var/tmp/portage/net-im/openmittsu-0.9.2_p78/work/openMittsu-0.9.2_p78/3rdparty/spdlog/include/spdlog/details/format.h: In member function ‘void fmt::internal::ArgFormatterBase<Impl, Char>::visit_char(int)’:
/var/tmp/portage/net-im/openmittsu-0.9.2_p78/work/openMittsu-0.9.2_p78/3rdparty/spdlog/include/spdlog/details/format.h:2166:24: error: expected unqualified-id before numeric constant
         const unsigned CHAR_WIDTH = 1;

                        ^

  -----------------------------------------------------------------

  This is an unstable amd64 chroot image (named gnome-unstable_20170201-093005) at a hardened host acting as a tinderbox.

  -----------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-5.4.0 *
llvm-config:
3.9.1
Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python3.5 (fallback)
  [3]   python2.7 (fallback)
  [4]   jython2.7 (fallback)
Available Ruby profiles:
  [1]   ruby21 (with Rubygems) *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.3.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

[Comment 1 Toralf Förster 2017-02-14 22:20:41 UTC]

Created attachment 463770 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-02-14 22:20:44 UTC]

Created attachment 463772 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2017-02-14 22:20:47 UTC]

Created attachment 463774 [details]
environment

[Comment 4 Toralf Förster 2017-02-14 22:20:50 UTC]

Created attachment 463776 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2017-02-14 22:20:55 UTC]

Created attachment 463778 [details]
net-im:openmittsu-0.9.2_p78:20170214-214241.log

[Comment 6 Ulrich Müller 2017-02-15 09:13:37 UTC]

Created attachment 463806 [details, diff]
Patch renaming the CHAR_WIDTH variable

Strange that I cannot reproduce this. Unstable amd64 here, same gcc version, same flags (so exactly the same command in the log) and I don't even get a warning.

So attached patch is a shot in the dark, renaming CHAR_WIDTH to MY_CHAR_WIDTH. Does it fix the problem for you?

[Comment 7 Ulrich Müller 2017-02-15 10:31:30 UTC]

In fact, it is this upstream issue: https://github.com/gabime/spdlog/issues/300
It is already fixed in git upstream: https://github.com/fmtlib/fmt/commit/abbefd71666055daac9e14e78262620f9e845850

[Comment 8 Ulrich Müller 2017-02-15 10:52:41 UTC]

Reported to openMittsu upstream: https://github.com/blizzard4591/openMittsu/issues/19

[Comment 9 Ulrich Müller 2017-02-15 12:46:35 UTC]

Fixed. No revbump because it is a build failure.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1b3025bcd147286244c69b2c6d7b10cd2e98d869