Bug 2429676 - F44FailsToInstall: anyterm [NEEDINFO]
Summary: F44FailsToInstall: anyterm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anyterm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Wakely
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F44FailsToInstall, RAWHIDEFailsToInstall 2429148
TreeView+ depends on / blocked
 
Reported: 2026-01-14 19:07 UTC by Fedora Fails To Install
Modified: 2026-01-22 13:58 UTC (History)
2 users (show)

Fixed In Version: anyterm-1.2.3-50.fc44
Clone Of:
Environment:
Last Closed: 2026-01-22 13:58:51 UTC
Type: ---
Embargoed:
fti-bugs: needinfo? (abo)


Attachments (Terms of Use)

Description Fedora Fails To Install 2026-01-14 19:07:52 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

Your package (anyterm) Fails To Install in Fedora 44:

can't install anyterm:
  - nothing provides libboost_system.so.1.83.0()(64bit) needed by anyterm-1.2.3-46.fc43.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-44-x86_64 --config-opts mirrored=False install anyterm


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!

Comment 1 Jonathan Wakely 2026-01-15 01:40:36 UTC
FTBFS in rawhide:

include/charset/char_t.hh:65:26: error: redeclaration of C++ built-in type ‘char8_t’

Comment 2 Jonathan Wakely 2026-01-15 01:42:53 UTC
See https://koji.fedoraproject.org/koji/taskinfo?taskID=141029805

Comment 3 Fedora Fails To Install 2026-01-22 11:22:05 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 7+ weeks.
This is the first reminder (step 3) from the policy.

Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.

Comment 4 Jonathan Wakely 2026-01-22 13:48:43 UTC
The code does this:

typedef char_t<8>::type  char8_t;

#define HAVE_BUILTIN_CHAR_T __cplusplus >= 201100L
#if ! HAVE_BUILTIN_CHAR_T

typedef char_t<16>::type char16_t;
typedef char_t<32>::type char32_t;

#endif


Upstream "fixed" it in r20470 with this patch:

------------------------------------------------------------------------
r20470 | phil | 2021-10-29 18:59:41 +0100 (Fri, 29 Oct 2021) | 1 line

C++20 defines char8_t


Index: libpbe/include/charset/char_t.hh
===================================================================
--- libpbe/include/charset/char_t.hh    (revision 20469)
+++ libpbe/include/charset/char_t.hh    (working copy)
@@ -36,12 +36,11 @@
 // Defined-size character types
 // ----------------------------
 //
-// The built-in types char and wchar_t have different numbers of bits on
-// different platforms.  C++0x will probably have new char types of determined
-// sizes; this file provides three typedefs, char8_t, char16_t and char32_t 
-// that do the same sort of thing.  These map to char and wchar_t when 
-// appropriate, and to an unsigned integer of the appropriate size (using 
-// Boost.Integer) otherwise.
+// C++20 finally has char8_t, char16_t and char32_t.
+// C++11 had char16_t and char32_t.
+// 
+// This file conditionally defines those types when they do not exist 
+// in the language.
 //
 // The specialised template class char_t<N> provides a typedef 'type' for an
 // N-bit character.
@@ -62,11 +61,16 @@
   typedef wchar_t type;
 };
 
+#define HAVE_BUILTIN_CHAR8_T __cplusplus >= 202002L
+#if ! HAVE_BUILTIN_CHAR8_T
+
 typedef char_t<8>::type  char8_t;
 
-#define HAVE_BUILTIN_CHAR_T __cplusplus >= 201100L
-#if ! HAVE_BUILTIN_CHAR_T
+#endif
 
+#define HAVE_BUILTIN_CHAR1632_T __cplusplus >= 201100L
+#if ! HAVE_BUILTIN_CHAR1632_T
+
 typedef char_t<16>::type char16_t;
 typedef char_t<32>::type char32_t;
 


But this is broken, the preprocessor expands it to ! __cplusplus >= 201100L which is equivalent to 0 >= 201100 which is always false.

I'll apply the upstream patch for now and report the preprocessor logic bug to the upstream author.

Comment 5 Jonathan Wakely 2026-01-22 13:58:51 UTC
Fixed in https://bodhi.fedoraproject.org/updates/FEDORA-2026-75e21fcd8f

But maybe the package should be updated to newer upstream sources, so that Patch1 and Patch2 can be dropped.


Note You need to log in before you can comment on or make changes to this bug.