Bugs in Archlinux32 packages, specific to 32-bit issues.

Bugs  FS#2  to  FS#92  have been recovered and may be incomplete, the
recovered Google/Bing cache data can be found here.

IDCategoryTask TypePrioritySeveritySummary  descStatusProgress
319PackagesBug ReportMediumLow[js102] rebuild results in a broken JS interpreter outp...New
0%
Task Description
 2:33.16 1 warning generated.
 2:47.25     Finished release [optimized] target(s) in 2m 24s
 3:50.23 js/src/build/libjs_static.a
 3:50.23 js/src/build/libmozjs-102.so
 3:51.27 js/src/gdb/gdb-tests
 3:51.27 js/src/shell/js
 3:51.33 js/src/jsapi-tests/jsapi-tests
 3:52.83 ./spidermonkey_checks.stub
 3:54.52 TEST-PASS | check_spidermonkey_style.py | ok
 3:54.79 TEST-PASS | check_macroassembler_style.py | ok
 3:54.84 TEST-PASS | check_js_opcode.py | ok
 3:55.04 7 compiler warnings present.
 3:55.09 Overall system resources - Wall time: 233s; CPU: 0%; Read bytes: 0; Write bytes: 0; Read time: 0; Write time: 0
 3:55.13 warning: intl/icu/source/i18n/nfsubs.cpp:1313:17 [-Wunused-but-set-variable] variable 'pow' set but not used
 3:55.13 warning: intl/icu/source/i18n/ucol.cpp:108:12 [-Wdeprecated-declarations] 'ucol_safeClone_71' is deprecated
 3:55.13 warning: mfbt/tests/TestResult.cpp:101:20 [-Wdeprecated-declarations] 'is_literal_type_v<mozilla::Result<int *, Failed>>' is deprecated
 3:55.13 warning: mfbt/tests/TestResult.cpp:102:20 [-Wdeprecated-declarations] 'is_literal_type_v<mozilla::Result<mozilla::Ok, Failed>>' is deprecated
 3:55.13 warning: mfbt/tests/TestResult.cpp:103:20 [-Wdeprecated-declarations] 'is_literal_type_v<mozilla::Result<mozilla::Ok, Foo8>>' is deprecated
 3:55.13 warning: mfbt/tests/TestResult.cpp:104:20 [-Wdeprecated-declarations] 'is_literal_type_v<mozilla::Result<Foo8, Foo16>>' is deprecated
 3:55.13 warning: mfbt/tests/TestResult.cpp:105:21 [-Wdeprecated-declarations] 'is_literal_type_v<mozilla::Result<mozilla::Ok, mozilla::UniquePtr<int>>>' is deprecated
 3:55.13 Your build was successful!
 Config object not found by mach.
Configure complete!
Be sure to run |mach build| to pick up any changes
To view resource usage of the build, run |mach resource-usage|.
To take your build for a test drive, run: |mach run|
Profiling instrumented JS...
/startdir/PKGBUILD: line 154:  6398 Segmentation fault      (core dumped) "$js" run.js
283PackagesBug ReportVery LowLow[icu70/icu71 ] packages not rebuilt yetAssigned
0%
Task Description

starting to collect them here packages which require icu69 (and have thus not been rebuilt
for icu 71 yet):

libreoffice-fresh

313PackagesBug ReportMediumLow[hg] broken on i486New
0%
Task Description
Traceback (most recent call last):
  File "/usr/bin/hg", line 59, in <module>
    dispatch.run()
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 143, in run
    status = dispatch(req)
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 232, in dispatch
    status = _rundispatch(req)
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 276, in _rundispatch
    ret = _runcatch(req) or 0
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 451, in _runcatch
    return _callcatch(ui, _runcatchfunc)
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 461, in _callcatch
    return scmutil.callcatch(ui, func)
  File "/usr/lib/python3.10/site-packages/mercurial/scmutil.py", line 153, in callcatch
    return func()
  File "/usr/lib/python3.10/site-packages/mercurial/dispatch.py", line 441, in _runcatchfunc
    return _dispatch(req)

That’s why ‘nss’ is not rebuilding on i486.

321PackagesBug ReportMediumLow[gnome] brokenAssigned
0%
Task Description

mutter had a checksum issue (trivial).

gnome-shell misses a current version of gjs:

Dependency gjs-1.0 found: NO found 1.70.2 but need: '>= 1.73.1'
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency gjs-1.0 found: NO 

gnome-shell/meson.build:80:0: ERROR: Dependency lookup for gjs-1.0 with method 'pkgconfig' failed: Invalid version, need 'gjs-1.0' ['>= 1.73.1'] found '1.70.2'.

A full log can be found at /build/gnome-shell/src/build/meson-logs/meson-log.txt
82Packages: StableBug ReportMediumLow[glibc] ld warning: /usr/lib32/ld-linux.so.2: corrupt G...New
0%
Task Description

Attached to Project: Archlinux32
Opened by Jeff Hodd - 11.07.2019
Last edited by Andreas Baumann - 09.08.2019
FS#82 - [glibc] ld warning: /usr/lib32/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

All software builds are producing this warning. Some builds are failing because of the error return on linking. I’m also seeing failures on LD_PRELOADs.

/bin/ld: warning: /usr/lib/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

Easy to reproduce. Just build this program:

# test.c
# Compiled with ‘gcc test.c’ int main() {

  return 0;

}

This was reported at bugs.archlinux.org (reference https://bugs.archlinux.org/task/63015) where it was closed and considered fixed if built using the –enable-cet flag. I built glibc with the –enable-cet flag, but am still seeing the failures, so not fixed.
Closed by Andreas Baumann
09.08.2019 11:44
Reason for closing: Fixed

  Comments (6)
  Related Tasks (0/0)

Jeff Hodd commented on 16.07.2019 03:29

I’ve narrowed down the glibc upgrade to glibc-2.29-1.26 -&gt; glibc-2.29-1.27. The error doesn’t occur with glibc-2.29-1.26. There were 3 changes made to the arch32 PKGBUILD for the glibc-2.29-1.27 release. One of them caused this issue.
Admin
Andreas Baumann commented on 16.07.2019 05:33

There is another thing which can change: the toolchain.
This GNU_PROPERTY error is something the compiler emits (we think it’s CET stuff, but it’s badly
documented). Binutils ld seems not to like this ELF section.

The error is the same as in:

https://bugs.archlinux.org/task/63015

What’s puzzling me: –enable-cet is there in glibc, gcc, binutils (just not for i486, as CET doesn’t\
work for older CPUs).

Commit: 09d03cbd4c57b8eabfadd22b67929d958b2409d7 and d57a456faa674c24e8869a26a14c497c95accf1f in
glibc are mine, they try to change stack alignment and handling of SSE for pentium4 for Java, also without effect.
Admin
Andreas Baumann commented on 16.07.2019 05:35

About linker warnings being turned to errors (as for compiler warnings turned to errors): this
is something the DEVELOPER should do, NOT the PACKAGER. Released software should:
- NOT include asserts
- NOT include debug code
- NOT include code only used for running tests
- NOT use -Werror
- NOT use -Wl,–fatal-warnings

See for instance extra-cmake-modules-5.59.0-ld-no-fatal-warning.patch.
Jeff Hodd commented on 16.07.2019 21:50

I knew about the cet issue. Did quite abit of looking around to get some insight into it (even looked at the code - elf-properties.c - and it looks like the Elf_Internal_Note description size is coming back with a value of 0. the other possibility is that (size % 4) is something other than 0 which is less likely). From what i could gather, cet is supposed to be enabled in the latest builds of glibc for i686 even though, as you pointed out, it’s not well documented. I did do a 2.29-4 i686 build with cet enabled and it made no difference vis-a-vis the warning. I also checked the upstream diff between 2.29-1.26 and 2.29-1.27 and noticed the addition of –enable-static-pie and thought maybe position independent executables may explain it. Did another glibc build with static pie disabled and that made no difference. Am about to go back and check the diff again and see what else may have changed.

I did check the CMakeLists.txt file for my failing build and it uses -Werror and -Wl,–fatal-warnings so I will remove those. But that doesn;t actually fix the underlying issue of the warning which we shouldn;t be seeing.

It is up to the developer, but too often one has to show that a change fixes an issue before you’ll get any attention. I may not be THE developer for this particular package, but I am A developer (in general), so I don;t feel uncomfortable making code changes.

I’ll keep looking around for differences between the 1.26 and 1.27 builds.
Jeff Hodd commented on 16.07.2019 22:15

if (note-&gt;descsz &lt; 8 || (note-&gt;descsz % align_size) != 0)

  {

bad_size:

    _bfd_error_handler
(_("warning: %pB: corrupt GNU_PROPERTY_TYPE (%ld) size: %#lx"),
 abfd, note-&gt;type, note-&gt;descsz);
    return FALSE;
  }

The warning is printing out the description size - and that’s 0.

Apparently it’s supposed to be &gt;= 8 and divisible by 4:

unsigned int align_size = bed-&gt;s-&gt;elfclass == ELFCLASS64 ? 8 : 4;

I am assuming that arch32 doesn’t support ELFCLASS64.
Jeff Hodd commented on 22.07.2019 17:13

https://bbs.archlinux32.org/viewtopic.php?id=2770

Google Cache

345PackagesBug ReportVery LowLow[gcompris-qt] doesn't start due to Qt 5.15.10Unconfirmed
0%
Task Description

I fails to start with: “Cannot mix incompatible Qt library (5.15.9) with this library (5.15.10)”

340PackagesBug ReportVery LowCritical[chromium] broken due to outdated libraries, plus also ...Unconfirmed
0%
Task Description

The package needs to be recompiled for re2 v10 and several required dependencies were not installed, such as icu69 (?) and more.

246PackagesBug ReportMediumLow[blender] doesn't work (and doesn't build)New
0%
Task Description

blender 2.93 has dependencies on wrong versions of
- llvm (via openshadinglanguage)
- boost (via openimageio)

Could NOT find PythonLibsUnix (missing: PYTHON_LIBRARY PYTHON_LIBPATH PYTHON_INCLUDE_DIR PYTHON_INCLUDE_CONFIG_DIR)’

blender 3.0.1:
Haru not found, disabling WITH_HARU’ and ‘Cycles OSL requires WITH_LLVM, the library may not have been found. Configure LLVM or disable WITH_CYCLES_OSL

Let’s tackle one issue after the other. :-)

Showing tasks 51 - 58 of 58 Page 2 of 2 - 1 - 2

Available keyboard shortcuts

Tasklist

Task Details

Task Editing