Jeff Law wrote: > > > On 12/19/20 9:40 PM, Rex Dieter wrote: >> Mattia Verga via devel wrote: >> >>> While trying to build a new kde-partitionmanager release, I get a >>> strange build failure which seems related to character encoding: >>> >>> https://kojipkgs.fedoraproject.org//work/tasks/8985/57428985/build.log >>> >>> /builddir/build/BUILD/partitionmanager-20.12.0/i686-redhat-linux- >> gnu/src/config.cpp:48:1: >>> error: extended character is not valid in an identifier >>> 48 | 挀漀渀猀琀 挀栀愀爀⨀ 挀漀渀猀琀 Config::EnumFileSystem::enumToString[] = { >>> "Unknown", "Extended", "Ext2", "Ext3", "Ext4", "LinuxSwap", "Fat16", >>> "Fat32", "Ntfs", "ReiserFS", "Reiser4", "Xfs", "Jfs", "Hfs", >>> "HfsPlus", "Ufs", "Unformatted", "Btrfs", "Hpfs", "Luks", "Ocfs2", >>> "Zfs", "Exfat", "Nilfs2", "Lvm2_PV", "F2fs", "Udf", "Iso9660", >>> "Luks2", "Fat12", "LinuxRaidMember", "BitLocker", "Apfs", "Minix" }; >>> | ^ >>> /builddir/build/BUILD/partitionmanager-20.12.0/i686-redhat-linux- >> gnu/src/config.cpp:48:1: >>> error: extended character ⨀ is not valid in an identifier >>> /builddir/build/BUILD/partitionmanager-20.12.0/i686-redhat-linux- >> gnu/src/config.cpp:48:1: >>> error: extended character is not valid in an identifier >>> /builddir/build/BUILD/partitionmanager-20.12.0/i686-redhat-linux- >> gnu/src/config.cpp:48:1: >>> error: extended character is not valid in an identifier >>> >>> This seems to happen only on i686 arch, so I don't think sources are >>> corrupted in some way. Also, there seems to be no relevant changes >>> between the latest built release and this one that could justify the >>> failure: >>> >>> https://github.com/KDE/kpmcore/compare/v20.11.90...v20.12.0 >>> >>> Any idea what's going on? >> Wierd issue with kconfig_compiler on i686 when built with gcc-11, see bug >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1907799 > I wouldn't be surprised if this turns out to be a gcc bug. In fact, > I've got my eye on upstream gcc bug 98366. > > While I'm on PTO for the next two weeks, I'll probably be checking-in on > a few things. If there's a good way to test this I expect I'll have a > compiler with the 98366 fix handy today/tomorrow. Tentatively, looks like this gcc issue is fixed using gcc-11.0.0-0.11.fc34, thanks! -- Rex _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
