Your message dated Thu, 21 Aug 2025 12:02:42 +0200 with message-id <[email protected]> and subject line Re: [Pkg-tcltk-devel] Bug#1092566: tdom FTBFS on hppa and powerpc due to 32-bit big endian has caused the Debian Bug report #1092566, regarding tdom FTBFS on hppa and powerpc due to 32-bit big endian to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1092566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092566 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tdom Version: 0.9.5-1.1 Tags: ftbfs Usertags: hppa powerpc Testcase fails like this: ---- Result was: 1 {error "not well-formed (invalid token)" at line 14048575688 character 50379238646} ---- Result should have been (exact matching): 1 {error "not well-formed (invalid token)" at line 3 character 11} ==== attrList-4.1 FAILED The interesting part here is that 14048575688 is hex value 0x3.455C40C8 and 50379238646 is hex value 0xB.BAD62CF6. In both cases the "upper" 32bits (0x3, and 0xb=11 decimal) have the expected value. hppa and powerpc are 32-bit platforms, and both big endian. The problem is somewhere in the code, where a 32-bit "(unsigned?)long" value is written to memory, but somewhere else a 64-bit "long" value is read back. Please make sure to use e.g. "uint64_t" type instead to avoid such problem. Helge
--- End Message ---
--- Begin Message ---Version: 0.9.6-1 Fixed by upstream on 0.9.6, currently on sid. https://buildd.debian.org/status/package.php?p=tdom Kind regards, Héctor
--- End Message ---
