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 TypePriority  descSeveritySummaryStatusProgress
 45 PackagesBug ReportMediumLow doublecmd: access violation - Arch Linux Closed
100%
Task Description

21.06.2018 - Both the gtk2 and the qt5 version fail with: [FORMS.PP] ExceptionOccurred Sender=EAccessViolation Exception=Access violation Stack trace: …

 46 Packages: Build-listBug ReportMediumLow electron - pic issues Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Erich Eckner - 27.06.2018
 FS#46  - electron - pic issues

/usr/bin/clang++ -Wl,-O1,–sort-common,–as-needed,-z,relro,-z,now -Wl,-z,noexecstack -Wl,-rpath=\$ORIGIN -rdynamic -Wl,–export-dynamic -pthread -Wl,–no-keep-memory –sysroot=/ -Lusr/lib/libfakeroot -Wl,-rpath-link=usr/lib/libfakeroot -m32 -Wl,-z,noexecstack -Wl,-O1 -Wl,–as-needed -Wl,–gc-sections -flto=thin -fuse-ld=lld -Wl,–icf=all -Wl,–lto-O0 -Wl,-mllvm,-function-sections -Wl,-mllvm,-data-sections -Wl,-rpath-link=lib/ -o electron -Wl,–start-group obj/atom/app/electron.atom_main.o obj/libelectron_lib.a obj/brightray/libbrightray.a obj/vendor/breakpad/libbreakpad_client.a -Wl,–end-group lib/libnode.so -Wl,–start-group /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libangle.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libbase.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libcc.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libchromiumcontent.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libcomponents.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libmedia.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libnet.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libpdfium.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libppapi.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libservices.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libskia.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libwebkit.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libwebkitbindings.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libwebkitcore.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libwebkitmodules.a /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libwebrtc.a -Wl,–end-group -lpthread -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lfribidi -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -ldbus-1 -lX11-xcb -lxcb -lXi -lXcursor -lXdamage -lXrandr -lXcomposite -lXext -lXfixes -lXrender -lX11 -lXtst -lXss -lgconf-2 -lgmodule-2.0 -lglib-2.0 -lssl3 -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lasound -lcap -lcups -lrt -ldl -lresolv -lfontconfig -lexpat -lavcodec -lavformat -lavutil -levent -lFLAC -lharfbuzz-icu -lharfbuzz -ljsoncpp -lminizip -lpulse -lvpx -lwebpdemux -lwebpmux -lwebp -lxslt -lm -lxml2 -lz -ljpeg -lre2 -lsnappy -latomic
/usr/bin/ld.lld: error: can’t create dynamic relocation R_386_32 against local symbol in readonly segment; recompile object files with -fPIC
>>> defined in /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libchromiumcontent.a(dct.o)
>>> referenced by ../../third_party/openh264/src/codec/common/x86/dct.asm
>>> dct.o:(.text+0×337) in archive /build/electron/src/electron/vendor/libchromiumcontent/dist/main/static_library/libchromiumcontent.a

I doubt, that this file gets compiled at all - the only occurences upto the above are:
[29/30] AR obj/chromiumcontent/libchromiumcontent.a
and
[34/16236] COPY /build/electron/src/electron/vendor/libchromiumcontent/src/out-ia32/static_library/obj/chromiumcontent/libchromiumcontent.a

  Comments (1)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 27.07.2018 04:23

I tried to remove all *.a and *.o files first, but this just creates other issues

Google Search

 47 Packages: StableBug ReportMediumLow rankmirrors $repo guessing broken in i686 only Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Levi - 26.07.2018
Last edited by Erich Eckner - 27.07.2018
 FS#47  - rankmirrors $repo guessing broken in i686 only

I usually use rankmirrors on my mirrorlist prior to installing them fully to sort them such that the quickest mirrors are listed first.

I found that when using them to sort my mirrorlist.pacnew, it would claim each server target was unreachable, and reproduce them in their original order, making the tool rather useless.
Workaround

I also discovered that I can work around the problem by passing an argument of ‘-r core’ to the invocation, e.g. ‘$ rankmirrors -r core /etc/pacman.d/mirrorlist.pacnew > mirrorlist.temp’
Steps to reproduce

  rankmirrors -t /etc/pacman.d/mirrorlist.pacnew

This -t option prints out the timings, or unreachable if it failed to create a valid uri.
Investigation

My investigations thus far show that /usr/bin/rankmirrors is a bash script, and it looks like the if statement starting on line 79 in the current version (the first if statement in the getfetchurl function) is designed to replace the $repo string with whatever $TARGETREPO is, else ‘core’ which suggests it should work by default.

The only consistent difference in the format of the mirrorlist file between here and on my x64 machine (where rankmirrors continues to work fine) is that on x64 the repos almost all have /os before /$repo while we often have it at the root of the public filesystem, or under something other than /os.

Unfortunately the vagaries of bash string substitution are something I rarely touch and never touch again provided they continue to work, so I can’t guess why this would have stopped working for us. If I have time to dig further I’ll comment here though, of course.
Closed by Erich Eckner
27.07.2018 04:22
Reason for closing: Fixed
Additional comments about closing:

note, that this deliberately does not work with upstream’s mirror layout

  Comments (2)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 26.07.2018 19:13

ok, I just checked - with my mirrorlist, it works (this is not the default mirrorlist) - so I suspect, it breaks due to our format of the urls ($root/$arch/$repo instead of $root/$repo/os/$arch) - I’ll look into this
Admin
Erich Eckner commented on 26.07.2018 19:38

I think, I fixed it - let’s see if it “compiles” and runs :-)

Google Cache

 48 Packages: TestingBug ReportMediumLow Testing repo missing a new version of python-six Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Levi - 19.08.2018
Last edited by Erich Eckner - 24.09.2018
 FS#48  - Testing repo missing a new version of python-six

I’ve become aware that python-six doesn’t identify that it depends specifically on python3.6 (it claims in the text that it’s for python 3 as well as python 2, which I don’t believe can be true; it only puts python files in /usr/lib/python3.6).

It has however allowed python 3.7 into the testing repo while no new version of python-six is available, and this version of python3 can no longer find a version of six when you import it.

As far as I know this is not an issue for anyone strictly on the release repos yet, and still won’t be an issue for anyone not using python-six either directly or indirectly.
Steps to reproduce

(upgrade at least python from the testing repos)
# python
# import six
> … > ModuleNotFoundError: No module named ‘six’
Steps to fix

A new version of python-six that supplies its files to python3.7/site-packages should be built and uploaded to the testing repos, and it should probably identify its dependent versions better.

I note arch64 has a newer python-six that supplies its libs to python3.7 just fine, although it also doesn’t identify its versions to my liking.
Closed by Erich Eckner
24.09.2018 08:45
Reason for closing: Fixed

  Comments (2)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 20.08.2018 04:26

python-six-1.11.0-3.0 in [staging] is made for python 3.7

The issue is known, (internally) documented and won’t be fixed within the next weeks, but hopefully I have time to look into this after my holidays.
Levi commented on 27.08.2018 16:39

Thanks, I see this is available in the testing repo already, and I’ve just tested it. I don’t seem to have rights to comment and close (or perhaps this bug needs to be further progressed before that become available, I dunno), but I’ve tried to reproduce this after upgrading, and it now works for me, so I can confirm that I consider this issue resolved and closed, unless you want to keep it open as a note that I don’t think this has been pushed through the the mainline repos yet, while python 3.7 is there already.

Powered by Flyspray

Google Cache

 49 PackagesBug ReportMediumLow ffmpeg update failures in release and testing Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Levi - 20.08.2018
Last edited by Erich Eckner - 29.10.2018
 FS#49  - ffmpeg update failures in release and testing

When I have done a pacman -Syu recently, it offers to update libx264 with x264:

:: Replace libx264 with testing/x264? [Y/n]
resolving dependencies… looking for conflicting packages… error: failed to prepare transaction (could not satisfy dependencies)
:: removing libx264 breaks dependency ‘libx264.so=152-32’ required by ffmpeg

As can be seen there, it fails because a dependency is not met.

This is reportedly also a problem on the release branches.

Using pacman’s query functionality I can see that x264 claims to provide libx264.so=155-32 rather than 152-32 i.e. x264 is too new for the current version of ffmpeg.

I consider this a high priority defect because ffmpeg is used by rather a lot of a/v playback and transcoding software.
Steps to reproduce

$ pacman -Syu

Workaround

Press n and enter when it offers to upgrade libx264. Ensure you’re not using multiple -ys on your pacman invocation.
Suggested fix

Provide an updated ffmpeg.
Closed by Erich Eckner
29.10.2018 11:50
Reason for closing: Fixed

  Comments (0)

Google Cache

Bing Cache

 50 PackagesBug ReportMediumLow [imagemagick] is not installable because of [perl] Closed
100%
Task Description

24.09.2018 - The current extra/imagemagick depends on ‘perl<5.27’, but core/perl is 5.28. $ pacman -Si imagemagick perl Repository : extra Name …

 51 PackagesBug ReportMediumLow ufw needs rebuild for python 3.7 Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Paul Gover - 07.09.2018
Last edited by Erich Eckner - 24.09.2018
 FS#51  - ufw needs rebuild for python 3.7

Been using ufw for some time. Today, I wanted to turn logging off.
Command “ufw logging off” should just work. Instead it gives:

ufw logging off
Traceback (most recent call last):

File “/usr/bin/ufw”, line 26, in

import ufw.frontend

ModuleNotFoundError: No module named ‘ufw’

which I trace to the fact ufw is installed in
/usr/lib/python3.6/site-packages/ufw
and there’s no longer a python 3.6 executable; it’s all 3.7 now.
Closed by Erich Eckner
24.09.2018 07:32
Reason for closing: Fixed

  Comments (3)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 07.09.2018 09:46

ufw-0.35-5.0 from [community-testing] should work - I’m moving it to [community] just now
Paul Gover commented on 07.09.2018 09:48

Sorry to add to your workload. I assumed a UFW problem was local to me. Now I’ve read the furore about python 3.7 etc. on the forums, my apologies. I’ll try the community-testing version. Thanks for the speedy response.
Paul Gover commented on 11.09.2018 15:21

To confirm, UFW is working fine for me now. Thanks.



Google Cache

 52 PackagesBug ReportMediumLow Some packages are built by "Unknown Packager" Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Luke Shumaker - 21.09.2018
 FS#52  - Some packages are built by “Unknown Packager”

Some packages have

packager = Unknown Packager

, which is caused by

makepkg.conf:PACKAGER

not being set.

I analyzed every .pkg.tar.xz file in the Arch 32 repos (all architectures). The earliest Unknown Packager package was built on June 9, 2017, and they’ve been intermittent since then. Here’s a listing of how many times each packager appears:

    2  Dave Reisner 
    2  Fabio Castelli (Muflone) 
    2  Giancarlo Razzolini 
    2  Jelle van der Waa 
    2  Laurent Carlier 
    2  S?bastien Luttringer 
    2  schuay 
    3  Florian Pritz 
    3  Johannes L?thberg 
    4  Alexander R?dseth 
    4  Andreas Radke 
    4  Eli Schwartz 
    4  Tobias Powalowski 
    5  Gaetan Bisson 
    5  Jonathan Steel 
    6  Bart?omiej Piotrowski 
    6  Erich Eckner 
    7  Kyle Keen 
    8  Evangelos Foutras 
    8  Maxime Gauduin 
    9  Jaroslav Lichtblau 
    9  Lukas Fleischer 
   18  BlackEagle 
   21  Sergej Pupykin 
   22  Guillaume ALAUX 
   29  Sven-Hendrik Haase 
   32  Levente Polyak 
   35  Jan Alexander Steffens (heftig) 
   39  Felix Yan 
   43  Jan de Groot 
   44  Andreas Baumann 
   75  Ball? Gy?rgy 
   81  Antonio Rojas 
 6592  Unknown Packager
20577  Erich Eckner 
------------------------------------------------------------------
27707  total

This causes a problem for us in Parabola, because we just started applying the usual upload checks from

db-update

to packages that we import.

  Comments (3)
  Related Tasks (0/0)

bill auger commented on 24.09.2018 05:20

i was trying to make sense of this today and my results were pretty strange

i wrote a script to extract ‘Unknown Packager’ from the db caches in /var/lib/pacman/sync/ and i got very different counts then what luke reported - i ran the same script on both parabola i686 and again on arch32 - it did show that all of the packages by ‘Unknown Packager’ are in [extra], [community], and [core]

<pre>
$ wc -l ./unknown-packagers-parabola
1800 ./unknown-packagers-parabola

$ wc -l ./unknown-packagers-arch32
2250 ./unknown-packagers-arch32
</pre>

one thing i noted was that one of the packages (4ti2) that arch32 has by ‘Unknown Packager’ for v1.6.7 shows as v1.6.9 packaged by ‘Erich Eckner’ on parabola and the parabola package has a higher version number and later build date - maybe my mirrorlist is wonky on arch32 but it is the default one that was installed

<pre>
arch32:
package: 4ti2-1.6.7-1
build date: 1497644502
packager: Unknown Packager

parabola:
package: 4ti2-1.6.9-1.0
build date: 1536224793
packager: Erich Eckner
</pre>

the script i used is attached to the corresponding parabola bug report
https://labs.parabola.nu/issues/1652 https://labs.parabola.nu/attachments/444/find-unknown-packagers Admin
Erich Eckner commented on 24.09.2018 08:47

The buildmaster now rejects package built by “Unknown Packager” - what remains is to rebuild all packages, that are already committed.
Admin
Erich Eckner commented on 24.09.2018 08:54

btw: operating on the package database is much faster than extracting every single package:

find . -name ‘*.db.tar.gz’ | \

while read -r repo; do
  tar -Oxzf "${repo}" --wildcards '*/desc' | \
    sed -n '/^%FILENAME%$\|^%PACKAGER%$/{N;s/\n/ /;p;d;}'
done | \
sed '/^%FILENAME% /{N;/\n%PACKAGER% Unknown Packager$/!d;s/\n.*//;s/^%FILENAME% //;}'

Google Cache

 53 PackagesBug ReportMediumLow [gnome-terminal]: fails to star Closed
100%
Task Description

26.09.2018 - using openbox (not gnome) $ gnome-terminal # Couldn’t register with accessibility bus: Did not receive a reply. Possible causes include: the …

 54 Packages: StableBug ReportMediumLow [pam] links against libaudit, but doesn't declare a dep ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Luke Shumaker - 09.10.2018
 FS#54  - [pam] links against libaudit, but doesn’t declare a dependency on [audit]

Both core/pam 1.3.1-1.2 and staging/pam 1.3.1-1.3 have their libpam.so link against libaudit:

$ readelf –dynamic /usr/lib/libpam.so.0.84.2

Dynamic section at offset 0xfdbc contains 27 entries:

Tag        Type                         Name/Value

0×00000001 (NEEDED) Shared library: [libaudit.so.1]

However, the package does not declare depends=(audit) (’audit’ is the package that contains libaudit.so).

This is normally a fairly invisible mistake because recent versions of systemd depend on audit, so systemd-users (i.e. most users) will have audit installed anyway.

This affects `su` (of util-linux) and `sudo` (of sudo), which both link against libpam.

  Comments (4)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 09.10.2018 20:42

pam also links against libaudit.so.1 iff rebuilt for x86_64 - but not the currently built one for x86_64:

— /dev/fd/63 2018-10-09 22:41:57.015507993 +0200
+++ /dev/fd/62 2018-10-09 22:41:57.015507993 +0200
@@ -3,9 +3,9 @@
pkgbase = pam
pkgver = 1.3.1-1
pkgarch = x86_64
-pkgbuild_sha256sum = 3a72016938e6f3e8660a0f8774b576bf58aa4c7b218948e1fadcf39a3e7ebf9d
-packager = Erich Eckner
-builddate = 1539104335
+pkgbuild_sha256sum = e178fcb37ae20afe3f75b66ec5c29bb9eaf5d5e25d032d62e01e2fc54cf2ed32
+packager = Tobias Powalowski
+builddate = 1529655718
builddir = /build
buildenv = !distcc
buildenv = color
@@ -23,129 +23,129 @@
options = !upx
options = !debug
installed = acl-2.2.53-1-x86_64
-installed = archlinux-keyring-20181003-1-any
+installed = archlinux-keyring-20180404-1-any
installed = argon2-20171227-3-x86_64
installed = attr-2.4.48-1-x86_64
-installed = audit-2.8.4-2-x86_64
installed = autoconf-2.69-4-any
-installed = automake-1.16.1-1-any
+installed = automake-1.15.1-1-any
installed = bash-4.4.023-1-x86_64
-installed = binutils-2.31.1-3-x86_64
+installed = binutils-2.30-5-x86_64
installed = bison-3.0.5-1-x86_64
-installed = bzip2-1.0.6-8-x86_64
-installed = ca-certificates-20180821-1-any
-installed = ca-certificates-mozilla-3.39-1-x86_64
-installed = ca-certificates-utils-20180821-1-any
-installed = coreutils-8.30-1-x86_64
+installed = bzip2-1.0.6-7-x86_64
+installed = ca-certificates-20170307-1-any
+installed = ca-certificates-cacert-20140824-4-any
+installed = ca-certificates-mozilla-3.37.3-1-x86_64
+installed = ca-certificates-utils-20170307-1-any
+installed = coreutils-8.29-1-x86_64
installed = cracklib-2.9.6-1-x86_64
-installed = cryptsetup-2.0.4-1-x86_64
-installed = curl-7.61.1-3-x86_64
+installed = cryptsetup-2.0.3-2-x86_64
+installed = curl-7.60.0-1-x86_64
installed = db-5.3.28-4-x86_64
-installed = dbus-1.12.10-2-x86_64
-installed = device-mapper-2.02.181-1-x86_64
+installed = dbus-1.12.8-1-x86_64
+installed = device-mapper-2.02.177-5-x86_64
installed = diffutils-3.6-1-x86_64
-installed = docbook-xml-4.5-8-any
+installed = docbook-xml-4.5-7-any
installed = docbook-xsl-1.79.2-4-any
-installed = e2fsprogs-1.44.4-1-x86_64
-installed = expat-2.2.6-1-x86_64
-installed = fakeroot-1.23-1-x86_64
-installed = file-5.34-1-x86_64
-installed = filesystem-2018.8-1-x86_64
+installed = e2fsprogs-1.44.2-1-x86_64
+installed = expat-2.2.5-1-x86_64
+installed = fakeroot-1.22-1-x86_64
+installed = file-5.33-3-x86_64
+installed = filesystem-2018.1-2-x86_64
installed = findutils-4.6.0-2-x86_64
installed = flex-2.6.4-1-x86_64
installed = gawk-4.2.1-1-x86_64
-installed = gc-7.6.8-1-x86_64
-installed = gcc-8.2.1+20180831-1-x86_64
-installed = gcc-libs-8.2.1+20180831-1-x86_64
-installed = gdbm-1.18-1-x86_64
+installed = gc-7.6.6-1-x86_64
+installed = gcc-8.1.1+20180531-1-x86_64
+installed = gcc-libs-8.1.1+20180531-1-x86_64
+installed = gdbm-1.14.1-1-x86_64
installed = gettext-0.19.8.1-2-x86_64
-installed = glib2-2.58.1-1-x86_64
-installed = glibc-2.28-4-x86_64
+installed = glib2-2.56.1-1-x86_64
+installed = glibc-2.27-3-x86_64
installed = gmp-6.1.2-1-x86_64
-installed = gnupg-2.2.10-1-x86_64
-installed = gnutls-3.5.19-2-x86_64
-installed = gpgme-1.11.1-2-x86_64
-installed = gpm-1.20.7.r27.g1fd1941-1-x86_64
+installed = gnupg-2.2.8-1-x86_64
+installed = gnutls-3.5.18-1-x86_64
+installed = gpgme-1.11.1-1-x86_64
+installed = gpm-1.20.7-8-x86_64
installed = grep-3.1-1-x86_64
installed = groff-1.22.3-7-x86_64
-installed = guile-2.2.4-1-x86_64
+installed = guile-2.2.3-1-x86_64
installed = gzip-1.9-1-x86_64
-installed = hwids-20180518-1-any
-installed = iana-etc-20180913-1-any
-installed = icu-62.1-1-x86_64
-installed = iptables-1:1.6.2-3-x86_64
-installed = json-c-0.13.1-2-x86_64
+installed = hwids-20171003-1-any
+installed = iana-etc-20180221-1-any
+installed = icu-61.1-1-x86_64
+installed = iptables-1.6.2-2-x86_64
+installed = json-c-0.13.1-1-x86_64
installed = kbd-2.0.4-1-x86_64
-installed = keyutils-1.5.11-1-x86_64
+installed = keyutils-1.5.10-2-x86_64
installed = kmod-25-1-x86_64
installed = krb5-1.16.1-1-x86_64
installed = less-530-1-x86_64
-installed = libarchive-3.3.3-1-x86_64
+installed = libarchive-3.3.2-2-x86_64
installed = libassuan-2.5.1-1-x86_64
-installed = libatomic_ops-7.6.6-1-x86_64
+installed = libatomic_ops-7.6.4-1-x86_64
installed = libcap-2.25-1-x86_64
installed = libcap-ng-0.7.9-1-x86_64
-installed = libelf-0.174-1-x86_64
+installed = libelf-0.171-1-x86_64
installed = libffi-3.2.1-2-x86_64
installed = libgcrypt-1.8.3-1-x86_64
-installed = libgpg-error-1.32-1-x86_64
+installed = libgpg-error-1.31-1-x86_64
+installed = libidn-1.34-2-x86_64
installed = libidn2-2.0.5-1-x86_64
installed = libksba-1.3.5-1-x86_64
-installed = libldap-2.4.46-2-x86_64
+installed = libldap-2.4.46-1-x86_64
installed = libmnl-1.0.4-1-x86_64
installed = libmpc-1.1.0-1-x86_64
-installed = libnftnl-1.1.1-1-x86_64
-installed = libnghttp2-1.33.0-1-x86_64
+installed = libnftnl-1.1.0-1-x86_64
+installed = libnghttp2-1.31.1-1-x86_64
installed = libnl-3.4.0-1-x86_64
-installed = libpcap-1.9.0-1-x86_64
+installed = libpcap-1.8.1-2-x86_64
installed = libpsl-0.20.2-1-x86_64
-installed = libsasl-2.1.26-13-x86_64
-installed = libseccomp-2.3.3-1-x86_64
+installed = libsasl-2.1.26-12-x86_64
+installed = libseccomp-2.3.2-2-x86_64
installed = libsecret-0.18.6-1-x86_64
installed = libssh2-1.8.0-2-x86_64
-installed = libsystemd-239.2-1-x86_64
+installed = libsystemd-238.133-4-x86_64
installed = libtasn1-4.13-1-x86_64
-installed = libtirpc-1.1.4-1-x86_64
-installed = libtool-2.4.6+42+gb88cebd5-2-x86_64
+installed = libtirpc-1.0.3-2-x86_64
+installed = libtool-2.4.6+40+g6ca5e224-7-x86_64
installed = libunistring-0.9.10-1-x86_64
installed = libusb-1.0.22-1-x86_64
-installed = libutil-linux-2.32.1-2-x86_64
-installed = libxml2-2.9.8-5-x86_64
+installed = libutil-linux-2.32-3-x86_64
+installed = libxml2-2.9.8-2-x86_64
installed = libxslt-1.1.32+3+g32c88216-1-x86_64
-installed = linux-api-headers-4.17.11-1-any
-installed = lz4-1:1.8.3-1-x86_64
+installed = linux-api-headers-4.16.1-1-any
+installed = lz4-1:1.8.2-2-x86_64
installed = m4-1.4.18-1-x86_64
installed = make-4.2.1-2-x86_64
installed = mpfr-4.0.1-1-x86_64
installed = ncurses-6.1-3-x86_64
installed = nettle-3.4-1-x86_64
-installed = npth-1.6-1-x86_64
-installed = openssl-1.1.1-1-x86_64
-installed = p11-kit-0.23.14-1-x86_64
-installed = pacman-5.1.1-1-x86_64
-installed = pacman-mirrorlist-20180912-1-any
-installed = pam-1.3.1-1-x86_64
+installed = npth-1.5-1-x86_64
+installed = openssl-1.1.0.h-1-x86_64
+installed = p11-kit-0.23.12-1-x86_64
+installed = pacman-5.1.0-2-x86_64
+installed = pacman-mirrorlist-20180524-1-any
+installed = pam-1.3.0-2-x86_64
installed = pambase-20171006-1-any
-installed = patch-2.7.6-3-x86_64
+installed = patch-2.7.6-1-x86_64
installed = pcre-8.42-1-x86_64
-installed = pcre2-10.32-1-x86_64
-installed = perl-5.28.0-1-x86_64
-installed = pinentry-1.1.0-4-x86_64
-installed = pkgconf-1.5.3-1-x86_64
+installed = pcre2-10.31-1-x86_64
+installed = perl-5.26.2-1-x86_64
+installed = pinentry-1.1.0-3-x86_64
+installed = pkgconf-1.4.2-2-x86_64
installed = popt-1.16-9-x86_64
installed = procps-ng-3.3.15-1-x86_64
installed = readline-7.0.005-1-x86_64
installed = sed-4.5-1-x86_64
-installed = shadow-4.6-1-x86_64
-installed = sqlite-3.25.2-1-x86_64
-installed = sudo-1.8.25.p1-1-x86_64
-installed = systemd-239.2-1-x86_64
+installed = shadow-4.5-4-x86_64
+installed = sqlite-3.24.0-1-x86_64
+installed = sudo-1.8.23-2-x86_64
+installed = systemd-238.133-4-x86_64
installed = tar-1.30-1-x86_64
installed = texinfo-6.5-1-x86_64
-installed = tzdata-2018e-2-x86_64
-installed = util-linux-2.32.1-2-x86_64
+installed = tzdata-2018e-1-any
+installed = util-linux-2.32-3-x86_64
installed = w3m-0.5.3.git20180125-1-x86_64
installed = which-2.21-2-x86_64
installed = xz-5.2.4-1-x86_64
-installed = zlib-1:1.2.11-3-x86_64
-installed = zstd-1.3.5-1-x86_64
+installed = zlib-1:1.2.11-2-x86_64
Admin
Erich Eckner commented on 09.10.2018 20:47

As can be seen, the new version of systemd pulls in audit, against which then the linking happens.
I would not do anything about this issue (if that’s ok with you, Luke), because:
1st it only affects systems w/o systemd - e.g. non-standard systems
2nd it will solve itself with the next (upstream) release/rebuild of pam (or at least, if upstream does not add audit to the depends, it will become an upstream bug which we should report to them)

regards,
Erich
Luke Shumaker commented on 09.10.2018 21:28

Parabola supports OpenRC, so this risks breaking sudo for Parabola OpenRC users, making it more severe for us downstream than it is for you.

That isn’t to say that you have to take actionand fix it for us; it is a low-priority bug for Arch Linux 32 users, so if you want to wait for it to be resolved in upsteam Arch, that’s your prerogative. But it means that in the mean-time, Parabola will have to repackage it to avoid breaking our OpenRC users’ boxes.
bill auger commented on 10.10.2018 01:16

related to: https://bugs.archlinux.org/task/60365

Google Cache

 55 PackagesBug ReportMediumLow Unknown bug FS#55 Closed
100%
Task Description

no task description

 56 PackagesBug ReportMediumLow libreoffice-fresh 6.1.3-1.0 in [extra] is not build aga ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Raphael Scholer - 11.11.2018
Last edited by Erich Eckner - 14.11.2018
 FS#56  - libreoffice-fresh 6.1.3-1.0 in [extra] is not build against packages in it

libreoffice-fresh seems not to be build against packages in [extra], but rather against packages in [*testing].

Running libreoffice produces the following error message:

/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: liborcus-0.14.so.0: cannot open shared object file: No such file or directory

extra/liborcus is 0.13.4-3.1
testing/liborcus is 0.14.1-1.0
Closed by Erich Eckner
14.11.2018 18:05
Reason for closing: Fixed

  Comments (1)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 12.11.2018 10:37

I moved liborcus and libixion from testing to extra - now it should work.

Google Cache

 57 Packages: StableBug ReportMediumLow libc fails on AMD-K6 Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 15.11.2018
Last edited by Andreas Baumann - 31.01.2019
 FS#57  - libc fails on AMD-K6

pacstrap /test base
LD_LIBRARY_PATH=/test/usr/lib gdb –args /test/bin/bash results in:

Program terminated with signal SIGILL, Illegal instruction.
#0 0xb7619991 in strcmp () from /test/usr/lib/libc.so.6
(gdb) bt
#0 0xb7619991 in strcmp () from /test/usr/lib/libc.so.6
#1 0xb75bd41f in setlocale () from /test/usr/lib/libc.so.6
#2 0x0076b7f2 in ?? ()
#3 0x0053acf6 in ?? ()
#4 0xb75b3a31 in __libc_start_main () from /test/usr/lib/libc.so.6
#5 0x0053e561 in ?? ()

So, getting the exact failing opcode is hard.

2.28-5.0 was ok,
2.28-5.2 is not.

So it’s something we changed or something changed on one of the i486 build slaves.

Happens only on the AMD-K6, all other machines with CPUs with limited special instruction
sets (Pentium-S, AMD Geode) are working fine.
Closed by Andreas Baumann
31.01.2019 13:50
Reason for closing: Fixed
Additional comments about closing:

works with glibc-2.28-5.5-i486

  Comments (11)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 10.01.2019 08:27

happens on a Pentium-S now too.
Pentium-II is still fine, so is AMD Geode..
Admin
Andreas Baumann commented on 24.01.2019 10:10

Finally got around to tackle this one
installing a minimal chroot with:

pacstrap /test bash

Then debugging the chroot call:

gdb –args /usr/bin/chroot /test

yields:

Dump of assembler code for function memcpy:

 0xb7ff22f0 &lt;+0&gt;:     test   %al,%al
 0xb7ff22f2 &lt;+2&gt;:     jne    0xb7ff22e8
 0xb7ff22f4 &lt;+4&gt;:     xor    %eax,%eax
 0xb7ff22f6 &lt;+6&gt;:     ret    
 0xb7ff22f7 &lt;+7&gt;:     mov    $0x1,%eax
 0xb7ff22fc &lt;+12&gt;:    mov    $0xffffffff,%ecx

&gt; 0xb7ff2301 &lt;+17&gt;: cmovb %ecx,%eax

 0xb7ff2304 &lt;+20&gt;:    ret    

End of assembler dump.

So, we got cmov creeping in.

/proc/cpuinfo tells us that neither early Pentiums nor AMD K6 had a CMOV opcode.

Now the trick question is, why is it creeping into the C library?

Is the C library compiled with the wrong flags?
Is the gcc assuming that every CPU has a CMOV instruction? Are flags wrong there
or is CMOV suddenly the default?
Admin
Andreas Baumann commented on 24.01.2019 10:39

Checking in glibc: this is the offending opcode

i686/strcmp.S: cmovbl %ecx, %eax

L(neq): movl $1, %eax

      movl    $-1, %ecx
      cmovbl  %ecx, %eax

Now the question is, why does glibc think it’s ok to use i686 optimizations
when compiling with -march-i486.
Admin
Andreas Baumann commented on 24.01.2019 11:09

Not found an obvious reason, retriggering rebuild on known-good (hopefully) i486 build slave.
Admin
Andreas Baumann commented on 24.01.2019 20:44

config.log shows me i686 as build host. This is guessed with config.guess.
Manually executing config.guess on the build machine results in i486-pc-linux-gnu.
setarch i486 ./config.guess results in i686-pc-linux-gnu.
setarch i486 uname -m results in i686.

This breaks every build on i486!

/usr/bin/setarch is owned by util-linux 2.33.1-2.3 and is is completly broken!

And of course, it’s used in setarch “${arch}” mkarchroot in staging-i486-build.

So the consequenses are:
- devtools32 must NOT use setarch anywhere in the *i486* files
- the whole i486 toolchain and all packages have to be rebuilt (basically from the stage of last bootstrapping, every package above could contain bad opcodes!).

The irony is, that building just with makepkg on a emulated i486 virtual machine works
fine, using the devtools breaks things..
Admin
Andreas Baumann commented on 24.01.2019 21:11

Actually, thinking about it: I should try to patch setarch in coreutils for i486.
So we don’t have to fork devtools32 too much from upstream..

binutils and gcc have an explicit host and build flags, so they should be fine.
Maybe rebuilding just glibc with a fixed setarch is sufficient.
Admin
Andreas Baumann commented on 24.01.2019 21:15

If we are unlucky, utsname information in setarch.c is wrong and it’s not
a coreutils problem..
Admin
Andreas Baumann commented on 25.01.2019 08:05

The man page of setarch documents the bug:

The execution domains currently only affects the output of uname -m. For example, on an AMD64 sys-

     tem, running setarch i386 program will cause program to see i686 instead of x86_64 as  the  machine
     type.  It also allows to set various personality options.  The default program is /bin/sh.

So, we are not allowed to fix this, as other programs may rely on the bug.

So, fixing the devtools32 it is… Admin
Andreas Baumann commented on 25.01.2019 09:15

setarch bug reported here:

https://github.com/karelzak/util-linux/issues/707

and here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506632

uname -p reports unknown, this explains why config.guess relies
on uname -m to guess the CPU.

We came to those possible solutions:
- fix setarch.c (rather let it report something different than what the kernel is providing)
- add flags to devtools32 to switch off setarch usage (means, we can no longer build i486 on x86_64 slaves)
- add –build=i486-pc-linux-gnu in every configure call necessary
- go with the CLFS uname hack
- hack setarch of the host machine
Admin
Andreas Baumann commented on 27.01.2019 16:05

The CLFS uname hack solution.

http://trac.clfs.org/ticket/146

http://clfs.org/view/svn/ppc/chroot/before-chroot.html Admin
Andreas Baumann commented on 27.01.2019 18:04

wget http://clfs.org/files/extras/uname_hack-20080713.tar.bz2

PKGBUILD of linux:
_srcver=4.20.4-arch1
pkgver=${_srcver//-/.}
pkgrel=1.0
make modules_prepare

make -C /root/linux/src/archlinux-linux SUBDIRS=$PWD uname_hack_fake_machine=i486

insmod uname_hack.ko

setarch i486 uname -m
i686
setarch i486 ./config.guess
i686-pc-linux-gnu

Ok, the uname hack no longer works, or setarch doesn’t rely on this module information.



Google Cache

 58 Packages: StableBug ReportMediumLow texlive-bin doesn't build Closed
100%
Task Description

22.12.2018 - g++ -DHAVE_CONFIG_H -I. -I../../../texk/web2c -I./w2c -I/build/texlive-bin/src/texlive-source/Work/texk -I/build/texlive-bin/src/texlive-source/texk …

 59 PackagesBug ReportMediumLow unison segfault Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 10.01.2019
Last edited by Andreas Baumann - 10.01.2019
 FS#59  - unison segfault

Calling unison, a file synchronizer written in Ocaml. Segfaults.
Most likely a string optimization inside Ocaml itself or a non-matching
library somewhere (recompile ocaml?)

(gdb) bt
#0 0x006782df in caml_string_equal ()
#1 0x005ce0d8 in camlUpdatearchiveMode_802888 ()
#2 0x005ce6e5 in camlUpdate
setArchiveData_802926 ()
#3 0x005da668 in camlGlobalsfun_802549 ()
#4 0x005fed99 in camlLwt_util
map_1080 ()
#5 0x005fedac in camlLwt_utilmap_1080 ()
#6 0x005da5b9 in camlGlobals
allRootsMap_301891 ()
#7 0x005cea7f in camlUpdateloadArchives_802958 ()
#8 0x005d4637 in camlUpdate
findUpdatesOnPaths_2603478 ()
#9 0x005b36f5 in camlUitextsynchronizeOnce_1102725 ()
#10 0x005b4041 in camlUitext
loop_1203129 ()
#11 0x005b41d6 in camlUitextsynchronizeUntilDone_1203134 ()
#12 0x005b442e in camlUitext
start_1303143 ()
#13 0x005acc54 in camlMainBody_401249 ()
#14 0x005ac19d in camlLinktext
entry ()
#15 0x005a8220 in caml_program ()
#16 0x0068b64d in caml_start_program ()
#17 0x0068b9f1 in caml_startup_common ()
#18 0x0068ba6a in caml_startup ()
#19 0x005a7c25 in main ()

Closed by Andreas Baumann
10.01.2019 14:15
Reason for closing: Not a bug
Additional comments about closing:

Cannot reprodduce but on a single machine. Might as well be something completly different..

  Comments (6)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 10.01.2019 08:31

easy trials first: let’s recompile ocaml
Admin
Andreas Baumann commented on 10.01.2019 09:30

Some things seem to be wrong here:

Warning 3: deprecated: Stdlib.String.capitalize
Use String.capitalize_ascii instead.
File “/build/unison/src/unison-2.51.2/build/src/uigtk2.ml”, line 1:
Error: /usr/lib/ocaml/lablgtk2/pango.cmi
is not a compiled interface for this version of OCaml.
It seems to be for an older version of OCaml.
make[1]: * [Makefile.OCaml:423: uigtk2.cmx] Error 2
make[1]: Leaving directory ‘/build/unison/src/unison-2.51.2/build/src’ make:
* [Makefile:14: src] Error 2

Admin
Andreas Baumann commented on 10.01.2019 09:56

rebuilding lablgtk2 now.
Admin
Andreas Baumann commented on 10.01.2019 11:29

rebuilding unison didn’t help.
Admin
Andreas Baumann commented on 10.01.2019 11:35

Ok, let’s rebuild ocaml itself.
Admin
Andreas Baumann commented on 10.01.2019 12:51

works on two vms (libvirt and Virtualbox), but not on my real eeepc.

Google Cache

 60 Packages: Build-listBug ReportMediumLow lightdm gtk greeter fails Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 10.01.2019
Last edited by Andreas Baumann - 20.01.2019
 FS#60  - lightdm gtk greeter fails

Jan 10 12:55:01 arch32-staging systemd-coredump[894]: Process 892 (lightdm-gtk-gre) of user 620 dumped core.

                                                    
                                                    Stack trace of thread 892:
                                                    #0  0x00000000b712bb25 n/a (libglib-2.0.so.0)
                                                    #1  0x00000000b7120230 g_log_default_handler (libglib-2.0.so.0)
                                                    #2  0x00000000b712bd7d g_logv (libglib-2.0.so.0)
                                                    #3  0x00000000b712bf55 g_log (libglib-2.0.so.0)
                                                    #4  0x00000000b711267a g_thread_new (libglib-2.0.so.0)
                                                    #5  0x00000000b7132a1e n/a (libglib-2.0.so.0)
                                                    #6  0x00000000b7132a7a n/a (libglib-2.0.so.0)
                                                    #7  0x00000000b70e78d7 g_unix_signal_source_new (libglib-2.0.so.0)
                                                    #8  0x00000000b70ea3ef g_unix_signal_add_full (libglib-2.0.so.0)
                                                    #9  0x00000000b70ea463 g_unix_signal_add (libglib-2.0.so.0)
                                                    #10 0x00000000004dc145 main (lightdm-gtk-greeter)
                                                    #11 0x00000000b6c87a49 __libc_start_main (libc.so.6)
                                                    #12 0x00000000004de7f5 _start (lightdm-gtk-greeter)

Closed by Andreas Baumann
20.01.2019 16:04
Reason for closing: Fixed
Additional comments about closing:

hotfixed in lightdm-1:1.28.0-1.3

  Comments (12)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 19.01.2019 07:49

So, this happens when registering a signal handler: g_unix_signal_add.

Usually this points into the direction of ABI mismatches..
Admin
Andreas Baumann commented on 19.01.2019 08:07

[+0.83s] DEBUG: Session pid=3468: Running command /usr/bin/lightdm-gtk-greeter
[+0.83s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.83s] DEBUG: Session pid=3468: Logging to /var/log/lightdm/seat0-greeter.log
[+1.45s] DEBUG: Seat seat0: Stopping; failed to start a greeter

the logfile is empty.

So, the question is, why doesn’t the greeter start and segfault.
Admin
Andreas Baumann commented on 19.01.2019 09:19

rebuilt both lightdm-gtk-greeter and glib2 with debugging information (options=debug in PKGBUILD).

Now the stacktrace looks like:

#0 0xb7178b25 in _g_log_abort (breakpoint=1) at ../glib/glib/gmessages.c:554
554 G_BREAKPOINT ();
(gdb) bt
#0 0xb7178b25 in _g_log_abort (breakpoint=1) at ../glib/glib/gmessages.c:554
#1 0xb716d230 in g_log_default_handler

  (log_domain=0xb71b40d0 "GLib", log_level=6, message=0x78ee60 "creating thread 'gmain': Error creating thread: Resource temporarily unavailable", unused_data=0x0) at ../glib/glib/gmessages.c:3111

#2 0xb7178d7d in g_logv

  (log_domain=0xb71b40d0 "GLib", log_level=G_LOG_LEVEL_ERROR, format=0xb7207a67 "creating thread '%s': %s", args=0xbf85e91c "\262\320 \267") at ../glib/glib/gmessages.c:1350

#3 0xb7178f55 in g_log

  (log_domain=0xb71b40d0 "GLib", log_level=G_LOG_LEVEL_ERROR, format=0xb7207a67 "creating thread '%s': %s") at ../glib/glib/gmessages.c:1413

#4 0xb715f67a in g_thread_new (name=0xb720d0b2 “gmain”, func=0xb7180b70 , data=0×0)

  at ../glib/glib/gthread.c:830

#5 0xb717fa1e in g_get_worker_context () at ../glib/glib/gmain.c:5888
#6 0xb717fa7a in ref_unix_signal_handler_unlocked (signum=15, signum=)

  at ../glib/glib/gmain.c:5224

#7 0xb71348d7 in _g_main_create_unix_signal_watch (signum=15) at ../glib/glib/gmain.c:5332
#8 0xb71348d7 in g_unix_signal_source_new (signum=15, signum=)

  at ../glib/glib/glib-unix.c:222

#9 0xb71373ef in g_unix_signal_add_full

  (priority=0, signum=15, handler=0x495f90 , user_data=0x1, notify=0x0)
  at ../glib/glib/glib-unix.c:252

#10 0xb7137463 in g_unix_signal_add (signum=15, handler=0x495f90 , user_data=0×1)
–Type for more, q to quit, c to continue without paging–

  at ../glib/glib/glib-unix.c:283

#11 0×00490145 in main (argc=, argv=) at lightdm-gtk-greeter.c:2768

Admin
Andreas Baumann commented on 19.01.2019 09:44

creating thread ‘gmain’: Error creating thread: Resource temporarily unavailable

This is the interesting one. Why should creating a thread run out of resources? And which
resources?
Admin
Andreas Baumann commented on 19.01.2019 09:47

This is not by any chance an unhandled EAGAIN?
Admin
Andreas Baumann commented on 19.01.2019 10:04

[pid 6607] execve(”/usr/bin/core_perl/plymouth”, [”plymouth”, “–ping”], 0xbfa9086c /* 22 vars */) = -1 ENOENT (No such file or directory)

this seems a collateral damage (aka hard-coded call to the bootup manager plymouth), not every
Linux distribution has a plymouth, so I hope, this is actually optional..
The -ping indicates, that plymouth is started with ping, to see whether it is around.
It doesn’t seem to have something to do with our problem though..

There is a strace entry showing the greeter gets started:

[pid 6616] execve(”/usr/bin/lightdm-gtk-greeter”, [”/usr/bin/lightdm-gtk-greeter”], 0xf61510 /* 15 vars */) = 0

later the sighandler tries to open a new thread:

825 GThread *thread;
826
827 thread = g_thread_new_internal (name, g_thread_proxy, func, data, 0, &amp;error);
828
829 if G_UNLIKELY (thread == NULL)
830 g_error (”creating thread ‘%s’: %s”, name ? name : ““, error-&gt;message);
831
832 return thread;

So, if it runs out of resources here (due to a systemd limit, rlimit thing), this would
explain the startup issues..

There is also a suspicious:

[pid 6616] mmap2(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = -1 EAGAIN (Resource temporarily unavailable)

So, I check the rlimit settings used by systemd for login session..
Admin
Andreas Baumann commented on 20.01.2019 09:21

Sounds related:

https://github.com/abrt/faf/issues/212 Admin
Andreas Baumann commented on 20.01.2019 10:37

mmh. why does lightdm-gtk-greeter work on 64-bit Archlinux?
Admin
Andreas Baumann commented on 20.01.2019 10:55

aha. the mmap works there.
Admin
Andreas Baumann commented on 20.01.2019 13:54

lightdm-gtk-greeter.c

mlockall (MCL_CURRENT | MCL_FUTURE);

commenting that out lets the mmap2 succeed.

As we deal with passwords, just disabling the locking is maybe not the best idea.

Incrementing the systemd limit in lightdm.conf LimitMEMLOCK=2684354560
didn’t help at all.
Admin
Andreas Baumann commented on 20.01.2019 13:58

Locking the whole greeter with all GTK inside is maybe also not the wisest idea..
Admin
Andreas Baumann commented on 20.01.2019 14:03

LimitMEMLOCK=infinity in /lib/systemd/system/lightdm.service seemed so help.

Google Cache

 61 Packages: StableBug ReportMediumLow dmd fails to build with evalu8.d:function evalu8(elem . ...Closed
100%
Task Description

01.05.2019 - From the discusison in: https://forum.dlang.org/thread/dsrjmpnavxqsjqmlvotf@forum.dlang.org. Well the problem is that the mangling produced …

 62 Packages: TestingBug ReportMediumLow sddm-greeter aborts Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 01.02.2019
Last edited by Andreas Baumann - 12.05.2019
 FS#62  - sddm-greeter aborts

(gdb) bt
#0 0xb7fbea41 in kernel_vsyscall ()
#1 0xb6418746 in raise () from /usr/lib/libc.so.6
#2 0xb64021e3 in abort () from /usr/lib/libc.so.6
#3 0xb6793775 in QMessageLogger::fatal(char const*, …) const () from /usr/lib/libQt5Core.so.5
#4 0xb74da6fc in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /usr/lib/libQt5Qml.so.5
#5 0xb756f446 in QJSEngine::QJSEngine(QJSEnginePrivate&amp;, QObject*) () from /usr/lib/libQt5Qml.so.5
#6 0xb76afe1d in QQmlEngine::QQmlEngine(QObject*) () from /usr/lib/libQt5Qml.so.5
#7 0xb7cf93bb in QQuickViewPrivate::init(QQmlEngine*) () from /usr/lib/libQt5Quick.so.5
#8 0x0050c571 in SDDM::GreeterApp::addViewForScreen(QScreen*) ()
#9 0x0050d1a4 in SDDM::GreeterApp::startup() ()
#10 0xb69a6a4e in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#11 0xb697a565 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#12 0xb697d8c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
from /usr/lib/libQt5Core.so.5
#13 0xb697dcd9 in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQt5Core.so.5
#14 0xb69d4f74 in ?? () from /usr/lib/libQt5Core.so.5
#15 0xb55bca1e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0xb55beafa in ?? () from /usr/lib/libglib-2.0.so.0
#17 0xb55beb46 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0xb69d44bb in QEventDispatcherGlib::processEvents(QFlags) ()
–Type for more, q to quit, c to continue without paging– from /usr/lib/libQt5Core.so.5
#19 0xb6978ff6 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5
#20 0xb698188b in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#21 0x004ed3d0 in main () There seems to be a problem around Javascript and Qt5 Comments (1)
Related Tasks (0/0) Admin
Andreas Baumann commented on 12.05.2019 18:25 New bug on pentium4:
Stack trace of thread 387:
#0 0x00000000b7fa8841
kernel_vsyscall (linux-gate.so.1)

         #1  0x00000000b63311b6 raise (libc.so.6)
         #2  0x00000000b631b1e3 abort (libc.so.6)
         #3  0x00000000b66b2773 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
         #4  0x00000000b7b98592 _ZN13QSGRenderLoop28handleContextCreationFailureEP12QQuickWindowb (libQt5Quick.so.5)
         #5  0x00000000b7b99a1d n/a (libQt5Quick.so.5)
         #6  0x00000000b7b9a35b n/a (libQt5Quick.so.5)
         #7  0x00000000b6c95427 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5)
         #8  0x00000000b7c22c60 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5)
         #9  0x00000000b68a8845 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
         #10 0x00000000b6c898ab _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5)
         #11 0x00000000b6c89bda _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gui.so.5)
         #12 0x00000000b6c5e085 _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5)
         #13 0x00000000b0b7631d n/a (libQt5XcbQpa.so.5)
         #14 0x00000000b54ddb1e g_main_context_dispatch (libglib-2.0.so.0)
         #15 0x00000000b54dfbfa n/a (libglib-2.0.so.0)
         #16 0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #17 0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #18 0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #19 0x00000000b68af8db _ZN16QCoreApplication4execEv (libQt5Core.so.5)
         #20 0x00000000004a4330 main (sddm-greeter)
         #21 0x00000000b631c669 __libc_start_main (libc.so.6)
         #22 0x00000000004a4635 _start (sddm-greeter)
         
         Stack trace of thread 388:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b7a236ce n/a (libxcb.so.1)
         #3  0x00000000b7a25864 xcb_wait_for_event (libxcb.so.1)
         #4  0x00000000b0b751ea n/a (libQt5XcbQpa.so.5)
         #5  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #6  0x00000000b620dab2 start_thread (libpthread.so.0)
         #7  0x00000000b63ea96a __clone (libc.so.6)
         
         Stack trace of thread 389:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b54dfb55 n/a (libglib-2.0.so.0)
         #3  0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #4  0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #5  0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #6  0x00000000b66f2412 _ZN7QThread4execEv (libQt5Core.so.5)
         #7  0x00000000b0a20cdd n/a (libQt5DBus.so.5)
         #8  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #9  0x00000000b620dab2 start_thread (libpthread.so.0)
         #10 0x00000000b63ea96a __clone (libc.so.6)
         
         Stack trace of thread 391:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b54dfb55 n/a (libglib-2.0.so.0)
         #3  0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #4  0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #5  0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #6  0x00000000b66f2412 _ZN7QThread4execEv (libQt5Core.so.5)
         #7  0x00000000b77189c3 n/a (libQt5Qml.so.5)
         #8  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #9  0x00000000b620dab2 start_thread (libpthread.so.0)
         #10 0x00000000b63ea96a __clone (libc.so.6)

Google Cache

63Packages: StableBug ReportMediumLownodejs crashes in libuv when cleaning up FSReqCallbackNew
0%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 07.02.2019
FS#63 - nodejs crashes in libuv when cleaning up FSReqCallback

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
[Current thread is 1 (Thread 0xb5614880 (LWP 2013))]
(gdb) bt
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
#1 0×00937274 in node::fs::FSReqAfterScope::~FSReqAfterScope() ()
#2 0x0093767d in node::fs::AfterInteger(uv_fs_s*) ()
#3 0xb7e910e0 in uv.work_done () from /usr/lib/libuv.so.1
#4 0xb7e9526e in ?? () from /usr/lib/libuv.so.1
#5 0xb7ea51f8 in uv.io_poll () from /usr/lib/libuv.so.1
#6 0xb7e95c51 in uv_run () from /usr/lib/libuv.so.1
#7 0x00905d37 in node::Start(v8::Isolate*, node::IsolateData*, std::vector, std::allocator &gt;, std::allocator, std::allocator &gt; &gt; &gt; const&amp;, std::vector, std::allocator &gt;, std::allocator, std::allocator &gt; &gt; &gt; const&amp;) ()
#8 0×00903655 in node::Start(int, char**) ()
#9 0x008acef1 in main ()

This affects gyp, vault and probably some other packages, depending whether those callbacks are used or not.

  Comments (1)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 07.02.2019 09:36

See also mailing list thread:

https://lists.archlinux.org/pipermail/arch-ports/2018-November/000835.html

Google Code

 64 Packages: StableBug ReportMediumLow [wireguard] wireguard-arch-0.0.20190227-3.0-i686 does n ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Daniel Moch - 16.03.2019
 FS#64  - [wireguard] wireguard-arch-0.0.20190227-3.0-i686 does not work with 4.20.10.arch1-1.0 kernel

running `modprobe wireguard` yields `modprobe: ERROR: could not insert ‘wireguard’: Exec format error`

  Comments (1)
  Related Tasks (0/0)

Daniel Moch commented on 16.03.2019 11:52

I should add that downgrading to wireguard-arch 0.0.20190123-7.0 resolved the issue.

Google Cache

 65 Packages: StableBug ReportMediumLow [qt5-styleplugins] incompatile QT version Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by bill auger - 08.04.2019
 FS#65  - [qt5-styleplugins] incompatile QT version

i can not get any QT program to start while that is installed - they complain about mixed QT versions

it looks like qt5-styleplugins was built with the [testing] repo enabled, with qt5-base-5.12.2, while other QT-base programs were built against qt5-base-5.12.1

  Comments (4)
  Related Tasks (0/0)

bill auger commented on 08.04.2019 16:47

$ qv4l2
Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01)
Aborted (core dumped)
$ sudo octopi
Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01)
Aborted
$ sudo calamares
Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01)
Aborted
$ sudo qtox
[16:43:22.069 UTC] :0 : Fatal: Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01)
Aborted

Admin
Erich Eckner commented on 08.04.2019 19:36

where does qt see this versions?
The symbols in e.g. usr/lib/libQt5-Widgets.so.5.* do not have the least version part:

14 0×02 0x08a28110 Qt_5.10

    Qt_5.9 

15 0×02 0x08a28111 Qt_5.11

    Qt_5.10 

16 0×00 0x08a28112 Qt_5.12

    Qt_5.11 

required from libQt5Core.so.5:

0x08a28112 0x00 22 Qt_5.12
0x00058a25 0x00 03 Qt_5

required from libQt5Widgets.so.5:

0x00058a25 0x00 02 Qt_5

bill auger commented on 30.04.2019 11:16

i read on the web somewhere that all QT programs search the system very aggressively searching for any QT libs it can find (and presumably selecting the newest)

what i have noticed is that this is an interaction between the packages: ‘qt5-styleplugins’ (the themes) and ‘qt5ct’ (the config system) - the presence of either package alone is not enough to cause the problem - the problem occurs only when the ‘gtk2’ theme is selected in the qt5ct config - this is the default configuration that the parabola LXDE liveISO boots into, that config is prepared when building the ISO; so i did not notice this before; but on a manual install, i noticed the qt5ct program crashes when selecting the theme

to reproduce this symptom:
install both ‘qt5-styleplugins’ and ‘qt5ct’ launch qt5ct
select gtk2 from the “Style” select options

$ gdb qt5ct
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type “show copying” and “show warranty” for details.
This GDB was configured as “i686-pc-linux-gnu”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:

  .

For help, type “help”.
Type “apropos word” to search for commands related to “word”… Reading symbols from qt5ct…(no debugging symbols found)…done.
(gdb) run
Starting program: /usr/bin/qt5ct
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/usr/lib/libthread_db.so.1”.
[New Thread 0xb3c40b40 (LWP 9932)]

(qt5ct:9928): dbind-WARNING : 11:06:08.450: Couldn’t connect to accessibility bus: Failed to connect to socket /tmp/dbus-nltxAHENFr: Connection refused
Configuration path: “/home/bill/.config/qt5ct” Shared QSS paths: (”/home/bill/.local/share/qt5ct/qss”, “/usr/local/share/qt5ct/qss”, “/usr/share/qt5ct/qss”, “/usr/share/gdm/qt5ct/qss”, “/var/lib/menu-xdg/qt5ct/qss”)
Shared color scheme paths: (”/home/bill/.local/share/qt5ct/colors”, “/usr/local/share/qt5ct/colors”, “/usr/share/qt5ct/colors”, “/usr/share/gdm/qt5ct/colors”, “/var/lib/menu-xdg/qt5ct/colors”)
[New Thread 0xb1ff2b40 (LWP 9933)]
libEGL warning: DRI2: failed to authenticate
libEGL warning: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri) libEGL warning: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri) libEGL warning: DRI2: failed to authenticate
libEGL warning: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri) libEGL warning: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri) [this is where i selected the GTK theme] Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01) Thread 1 “qt5ct” received signal SIGABRT, Aborted.
0xb7fd5841 in kernel_vsyscall ()
(gdb) bt
#0 0xb7fd5841 in
kernel_vsyscall ()
#1 0xb6a2e746 in raise () at /usr/lib/libc.so.6
#2 0xb6a181e3 in abort () at /usr/lib/libc.so.6
#3 0xb6da9775 in () at /usr/lib/libQt5Core.so.5
#4 0xb6dc09d1 in () at /usr/lib/libQt5Core.so.5
#5 0xb1268540 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so
#6 0xb125620b in () at /usr/lib/qt/plugins/styles/libqgtk2style.so
#7 0xb126b3ad in () at /usr/lib/qt/plugins/styles/libqgtk2style.so
#8 0xb79ecd9a in QStyleFactory::create(QString const&amp;) () at /usr/lib/libQt5Widgets.so.5
#9 0x00411d2f in ()
#10 0x0042e2fd in ()
#11 0x0042e4a3 in ()
#12 0xb6fbc929 in QMetaObject::activate(QObject*, int, int, void
) ()

  at /usr/lib/libQt5Core.so.5

#13 0xb7a85121 in QComboBox::activated(QString const&amp;) () at /usr/lib/libQt5Widgets.so.5
#14 0xb7a876d4 in () at /usr/lib/libQt5Widgets.so.5
#15 0xb7a8a454 in () at /usr/lib/libQt5Widgets.so.5
#16 0xb7a90276 in () at /usr/lib/libQt5Widgets.so.5
#17 0xb6fbc861 in QMetaObject::activate(QObject*, int, int, void) ()
at /usr/lib/libQt5Core.so.5
#18 0xb7a853c1 in QComboBoxPrivateContainer::itemSelected(QModelIndex const&amp;) ()
at /usr/lib/libQt5Widgets.so.5
#19 0xb7a85ae0 in QComboBoxPrivateContainer::eventFilter(QObject*, QEvent*) ()
at /usr/lib/libQt5Widgets.so.5
#20 0xb6f908cc in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#21 0xb79708b8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libQt5Widgets.so.5
#22 0xb7979108 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#23 0xb6f90bc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libQt5Core.so.5
#24 0xb7977e61 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWid– get*, QWidget
, QPointer&amp;, bool, bool) () at /usr/lib/libQt5Widgets.so.5
#25 0xb79d636c in () at /usr/lib/libQt5Widgets.so.5
#26 0xb79d90ea in () at /usr/lib/libQt5Widgets.so.5
#27 0xb79708c9 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#28 0xb7978aa2 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#29 0xb6f90bc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#30 0xb735fb9e in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5
#31 0xb7361172 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
#32 0xb73358c5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5
#33 0xb3f5b0ad in () at /usr/lib/libQt5XcbQpa.so.5
#34 0xb602792e in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#35 0xb60299ea in () at /usr/lib/libglib-2.0.so.0
#36 0xb6029a36 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#37 0xb6feaceb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5
#38 0xb6f8f656 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5
#39 0xb6f97eeb in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#40 0x0040d36d in ()
#41 0xb6a19a49 in __libc_start_main () at /usr/lib/libc.so.6
#42 0x0040d505 in ()
(gdb)

bill auger commented on 08.05.2019 15:39

it looks like the latest rebuilds have leap-frogged the version conflict

previously:

Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c01)

today:

Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50c03)

my guess is that either ‘qt5-styleplugins’ or ‘qt5ct’ still need a rebuild

Google Cache

Bing Cache

 66 Packages: StableBug ReportMediumLow clang is broken due to library dependencies Closed
100%
Task Description

01.05.2019 -  FS#66  - clang is broken due to library dependencies. clang clang: error while loading shared libraries: libLLVM-7.so: cannot open shared …

 67 Packages: StableBug ReportMediumLow ldc segfault - Arch Linux Closed
100%
Task Description

01.05.2019 - Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb30d3329 in getenv () from /usr/lib/libc.so.6 (gdb) bt #0 0xb30d3329 in …

68Packages: Build-listBug ReportMediumLowdmd rebuild results in gen_man segfaultNew
0%
Task Description

FS#68 : dmd rebuild results in gen_man segfault
Opened by Andreas Baumann - 01.05.2019. FS#68 - dmd rebuild results in gen_man segfault. make: Entering directory ‘/build/dmd/src/dmd/docs’ …

 69 Packages: Build-listBug ReportMediumLow firefox breaks heavily in micro-optimized code Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 09.05.2019
Last edited by Andreas Baumann - 09.05.2019
 FS#69  - firefox breaks heavily in micro-optimized code

The root cause is rust is not recompiling currently.

The log in detail:

14:57.22 error[E0432]: unresolved import `simd_funcs`
14:57.22 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:16:1 3
14:57.22 |
14:57.22 16 | use simd_funcs::*;
14:57.22 | ^^^^^^^^^^ maybe a missing `extern crate simd_funcs;`?
14:57.22 error[E0432]: unresolved import `packed_simd`
14:57.22 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:17:1 3
14:57.22 |
14:57.22 17 | use packed_simd::u16x8;
14:57.22 | ^^^^^^^^^^^ maybe a missing `extern crate packed_simd;`?
14:57.45 error[E0425]: cannot find function `load16_unaligned` in this scope
14:57.45 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:120 :34
14:57.45 |
14:57.45 120 | let input = unsafe { load16_unaligned(src_ptr.add(i * 16)) };
14:57.45 | ^^^^^^^^^^^^^^^^ not found in this scope
14:57.45 error[E0425]: cannot find function `simd_unpack` in this scope
14:57.45 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:121 :35
14:57.45 |
14:57.45 121 | let (first, second) = simd_unpack(input);
14:57.45 | ^^^^^^^^^^^ not found in this scope
14:57.45 error[E0425]: cannot find function `store8_unaligned` in this scope
14:57.45 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:123 :17
14:57.45 |
14:57.45 123 | store8_unaligned(dst_ptr.add(i * 16), shift_upper(first));
14:57.45 | ^^^^^^^^^^^^^^^^ not found in this scope
14:57.45 error[E0425]: cannot find function `store8_unaligned` in this scope
14:57.45 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/x_user_defined.rs:124 :17
14:57.45 |
14:57.45 124 | store8_unaligned(dst_ptr.add1);
14:57.45 | ^^^^^^^^^^^^^^^^ not found in this scope
14:57.46 error[E0412]: cannot find type `u16x8` in this scope
14:57.46 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:121:40
14:57.46 |
14:57.46 121 | pub fn simd_at(&amp;self, i: usize) -&gt; u16x8 {
14:57.46 | ^^^^^ not found in this scope
14:57.46 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.46 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:122:21
14:57.46 |
14:57.46 122 | assert!(i + SIMD_STRIDE_SIZE / 2 &lt;= self.len);
14:57.46 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STR IDE_SIZE`
14:57.47 error[E0425]: cannot find function `to_u16_lanes` in this scope
14:57.47 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:124:18
14:57.47 |
14:57.47 124 | unsafe { to_u16_lanes(load16_unaligned(self.ptr.add(byte_index))) }
14:57.47 | ^^^^^^^^^^^^ not found in this scope
14:57.47 error[E0425]: cannot find function `load16_unaligned` in this scope
14:57.47 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:124:31
14:57.47 |
14:57.47 124 | unsafe { to_u16_lanes(load16_unaligned(self.ptr.add(byte_index))) }
14:57.47 | ^^^^^^^^^^^^^^^^ not found in this scope
14:57.47 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.47 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:145:12
14:57.47 |
14:57.47 145 | if SIMD_STRIDE_SIZE / 2 &lt;= self.len {
14:57.47 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:57.48 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.48 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:146:47
14:57.48 |
14:57.48 146 | let len_minus_stride = self.len - SIMD_STRIDE_SIZE / 2;
14:57.48 | ^^^^^^^^^^^^^^^^ help: a constant with a sim ilar name exists: `ALU_STRIDE_SIZE`
14:57.48 error[E0425]: cannot find function `simd_byte_swap` in this scope
14:57.48 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:150:28
14:57.48 |
14:57.48 150 | simd = simd_byte_swap(simd);
14:57.48 | ^^^^^^^^^^^^^^ not found in this scope
14:57.49 error[E0425]: cannot find function `store8_unaligned` in this scope
14:57.49 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:153:21
14:57.49 |
14:57.49 153 | store8_unaligned(other.as_mut_ptr().add(offset), simd);
14:57.49 | ^^^^^^^^^^^^^^^^ not found in this scope
14:57.49 error[E0425]: cannot find function `contains_surrogates` in this scope
14:57.49 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:155:20
14:57.49 |
14:57.49 155 | if contains_surrogates(simd) {
14:57.49 | ^^^^^^^^^^^^^^^^^^^ not found in this scope
14:57.49 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.49 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:158:27
14:57.49 |
14:57.49 158 | offset += SIMD_STRIDE_SIZE / 2;
14:57.49 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `A LU_STRIDE_SIZE`
14:57.50 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.50 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:237:8
14:57.50 |
14:57.50 237 | if SIMD_STRIDE_SIZE &lt;= len {
14:57.50 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:57.50 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.50 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.50 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:237:8
14:57.50 |
14:57.50 237 | if SIMD_STRIDE_SIZE &lt;= len {
14:57.50 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:57.50 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.50 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:238:38
14:57.50 |
14:57.50 238 | let len_minus_stride = len - SIMD_STRIDE_SIZE;
14:57.50 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:57.51 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.51 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:241:52
14:57.51 |
14:57.51 241 | let mut second = src.simd_at(offset + (SIMD_STRIDE_SIZE / 2));
14:57.51 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:57.51 error[E0425]: cannot find function `simd_byte_swap` in this scope
14:57.51 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:243:25
14:57.51 |
14:57.51 243 | first = simd_byte_swap(first);
14:57.51 | ^^^^^^^^^^^^^^ not found in this scope
14:57.52 error[E0425]: cannot find function `simd_byte_swap` in this scope
14:57.52 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:244:26
14:57.52 |
14:57.52 244 | second = simd_byte_swap(second);
14:57.52 | ^^^^^^^^^^^^^^ not found in this scope
14:57.52 error[E0425]: cannot find function `simd_is_basic_latin` in this scope
14:57.52 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:246:17
14:57.52 |
14:57.52 246 | if !simd_is_basic_latin(first | second) {
14:57.52 | ^^^^^^^^^^^^^^^^^^^ help: a function with a similar name exists: `ascii_to_basic_latin`
14:57.52 error[E0425]: cannot find function `simd_pack` in this scope
14:57.52 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:249:26
14:57.52 |
14:57.52 249 | let packed = simd_pack(first, second);
14:57.52 | ^^^^^^^^^ not found in this scope
14:57.53 error[E0425]: cannot find function `store16_unaligned` in this scope
14:57.53 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:251:17
14:57.53 |
14:57.53 251 | store16_unaligned(dst.as_mut_ptr().add(offset), packed);
14:57.53 | ^^^^^^^^^^^^^^^^^ not found in this scope
14:57.53 error[E0425]: cannot find value `SIMD_STRIDE_SIZE` in this scope
14:57.53 –&gt; /build/firefox/src/mozilla-unified/third_party/rust/encoding_rs/src/handles.rs:253:23
14:57.53 |
14:57.53 253 | offset += SIMD_STRIDE_SIZE;
14:57.53 | ^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `ALU_STRIDE_SIZE`
14:59.28 error: aborting due to 25 previous errors
14:59.28 Some errors occurred: E0412, E0425, E0432.
14:59.28 For more information about an error, try `rustc –explain E0412`.
14:59.44 error: Could not compile `encoding_rs`.

  Comments (5)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 09.05.2019 19:36

Compilation of firefox continues..

14:59.44 To learn more, run the command again with –verbose.
14:59.45 make[4]: * [/build/firefox/src/mozilla-unified/config/rules.mk:1027: force-cargo-library-build] Error 101
14:59.45 make[3]:
* [/build/firefox/src/mozilla-unified/config/recurse.mk:74: toolkit/library/rust/target] Error 2
14:59.45 make[3]: * Waiting for unfinished jobs….
17:24.43 Compiling lalrpop v0.16.0 good build system :-&gt;
Admin
Andreas Baumann commented on 09.05.2019 19:38 Let’s see how bad the situation is on pentium4, could easily be Mozilla projects get
build only for pentium4 in the future..
Admin
Andreas Baumann commented on 09.05.2019 19:46 Aha: i686 finally failed: 17:24.43 Compiling lalrpop v0.16.0
21:26.67 Compiling webidl v0.8.0
22:03.14 Compiling binjs_meta v0.4.3
22:25.46 Compiling binast v0.1.1 (/build/firefox/src/mozilla-unified/js/src/frontend/binsource)
22:58.29 Finished release [optimized] target(s) in 17m 41s
22:58.32 make[2]:
* [/build/firefox/src/mozilla-unified/config/recurse.mk:34: compile] Error 2
22:58.32 make[1]: * [/build/firefox/src/mozilla-unified/config/rules.mk:415: default] Error 2
22:58.32 make:
* [client.mk:125: build] Error 2
22:58.33 0 compiler warnings present.

Admin
Andreas Baumann commented on 10.05.2019 05:59

pentium4 seems to work fine.
Levi commented on 16.05.2019 21:08

So, is this getting dropped for i686 then? Probably no great loss; I remember when I was using a P3 in my server box, I gave up trying to use anything graphical, and just used links when I needed to look something up on t’internet.

I note in the i686 repo there’s currently a firefox 65.x rather than the 66.x we’ve got in pentium4, and some language packs that are 66 and some that are 65. English and all its variants are still on 65.x, but I note that it looks broken to me for German or Finnish users. Time to put it out of its misery?

Google Cache

1) i * 16) + 8), shift_upper(second
70Packages: Build-listBug ReportMediumLowchromium not available for i686 (fails in compiler intr...New
0%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 10.05.2019
FS#70 - chromium needs SSE2

chromium starts, but every page it loads ends in “Aw snap” and on the console:

Check failed: cpu.has_sse2().

Google Cache

 71 Packages: StableBug ReportMediumLow FS#71 - rust doesn't rebuild Closed
100%
Task Description

We need llvm 7.0 instead of 7.1.
If we muss a llvm update, bootstrapping rust fails (due to a to old libLLVM.so).
defined multiple times

  1. &gt; /build/rust/src/rustc-1.34.1-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-02dad87448159bce/out/consts.rs:2112:5

2110 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

 |     ------------------------------------------------------------------------------------------------------------------------------------- previous definition of the type `U1024` here

2111 | pub type P1024 = PInt; pub type N1024 = NInt;
2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

 |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `U1024` redefined here

https://github.com/paholg/typenum/commit/14a3322d1081fd63d5eb44bf8ab8f90676208228

Can anobody tell me, how we apply patches to downloaded artifacts while building?!

  Comments (32)
  Related Tasks (0/0)

Admin
Erich Eckner commented on 13.05.2019 04:32

&gt; Can anobody tell me, how we apply patches to downloaded artifacts while building?!

I only have a racy solutions for that. Put the following at the start of build():

while true; do
find $rust-build-dir-path -type f -name $name-to-patch -execdir patch -p1 -i $srcdir/patch \; &amp;&amp; break
done &amp;
Admin
Erich Eckner commented on 29.07.2019 09:25

trying to compile rust 1.34 with llvm-libs 7:

error[E0428]: the name `U1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.34.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs:2112:5

|
2110 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

   |     ------------------------------------------------------------------------------------------------------------------------------------- previous definition of the type `U1024` here

2111 | pub type P1024 = PInt; pub type N1024 = NInt;
2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this module

error[E0428]: the name `P1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.34.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs:2113:5

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ----------------------------- previous definition of the type `P1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this module

error[E0428]: the name `N1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.34.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs:2113:35

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ----------------------------- previous definition of the type `N1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this module

error: aborting due to 3 previous errors

Admin
Erich Eckner commented on 29.07.2019 09:32

let’s try again with:

while true; do
  sed -i '
    2112 { /pub type U1024/ d }
    2113 { /pub type P1024/ d }
  ' build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs 2>/dev/null || true
done &

injected in build() … which is the mother of all race conditions
Admin
Erich Eckner commented on 30.07.2019 08:36

current error:

error: this file contains an un-closed delimiter

  1. -&gt; /build/rust/src/rustc-1.34.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs:482:56

|
54 | pub mod consts {

  |                - un-closed delimiter

… 482 | pub type U210 = UInt`, const, identifier, lifetime, or type, found `}`

  1. -&gt; /build/rust/src/rustc-1.34.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-101079a7a9ba8c17/out/consts.rs:482:55

|
482 | pub type U210 = UInt`, const, identifier, lifetime, or type here

error: aborting due to 2 previous errors

error: Could not compile `typenum`.
warning: build failed, waiting for other jobs to finish… error: build failed

trying again with some even-more-racing build()

build() {

cd "rustc-$pkgver-src"
while true; do
  find build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build \
    -type f \
    -name consts.rs \
    -exec grep -qF 'pub type P1024' {} \; \
    -exec sleep 1 \; \
    -exec sed -i '
      2112 { /pub type U1024/ d }
      2113 { /pub type P1024/ d }
    ' {} \; 2&gt;/dev/null || true
done &amp;
_kill_pid=$!
python2 ./x.py build -j"$(nproc)"
kill $_kill_pid

}

Admin
Erich Eckner commented on 30.07.2019 13:03

this is super-annoying: now the old “duplicate definition” error is back … but in package_rust()
Let’s build again (for several hours O.o) with this hack also applied in package_rust() … Admin
Erich Eckner commented on 30.07.2019 18:41

whoah, even more fun:

warning: the feature `try_from` has been stable since 1.34.0 and no longer requires an attribute to enable

  1. -&gt; src/tools/clippy/clippy_lints/src/lib.rs:12:12

|
12 | #![feature(try_from)]

 |            ^^^^^^^^
 |
 = note: #[warn(stable_features)] on by default

warning: the feature `try_from` has been stable since 1.34.0 and no longer requires an attribute to enable

  1. -&gt; src/tools/clippy/clippy_lints/src/lib.rs:12:12

|
12 | #![feature(try_from)]

 |            ^^^^^^^^
 |
 = note: #[warn(stable_features)] on by default

warning: the feature `try_from` has been stable since 1.34.0 and no longer requires an attribute to enable
–&gt; src/tools/clippy/src/driver.rs:4:12

|

4 | #![feature(try_from)]

|            ^^^^^^^^
|
= note: #[warn(stable_features)] on by default
  Finished release [optimized] target(s) in 9m 17s

Building stage2 tool rls (i686-unknown-linux-gnu)
error: the listed checksum of `/build/rust/src/rustc-1.34.0-src/vendor/rustc-ap-rustc_target/spec/i686_unknown_linux_gnu.rs` has changed:
expected: a75a6025d7e3424edf9baf3039056c0f8eea157631a175d00ac5a218aa54b510
actual: 484bf8be15015b330fa9a97b6dabb8c7627e59d5cddb2dd0e83478749f8aabad

directory sources are not intended to be edited, if modifications are required then it is recommended that [replace] is used with a forked copy of the source
command did not execute successfully: “/usr/bin/cargo” “build” “–target” “i686-unknown-linux-gnu” “-j” “4” “–release” “–frozen” “–manifest-path” “/build/rust/src/rustc-1.34.0-src/src/tools/rls/Cargo.toml” “–features” “clippy” “–message-format” “json” expected success, got: exit code: 101
thread ‘main’ panicked at ‘Unable to build RLS’, src/bootstrap/dist.rs:65:9
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
failed to run: /build/rust/src/rustc-1.34.0-src/build/bootstrap/debug/bootstrap install
Build completed unsuccessfully in 2:02:38

Admin
Erich Eckner commented on 08.08.2019 06:18

current approach: using rust-1.36 from manjaro32 (thanks, jonathon!) … this fails in stage 1, because it does not find some library, which actually _is_ there (but apparently not in the search path).
Admin
Erich Eckner commented on 09.08.2019 05:16

symlinking the library to the correct one hidden in some “stage1” folder solved it. Now we have rust 1.36 for i686 in [build-support] - let’s hope some build slave can build a regular rust (e.g. one where I do not extract additional files with bsdtar into the build chroot) from that and we can close this bug report.
Admin
Andreas Baumann commented on 22.08.2019 07:43

Rebuilds of rust on i686 and pentium4 show:

— stderr
error: couldn’t load codegen backend “/usr/lib/rustlib/i686-unknown-linux-gnu/codegen-backends/librustc_codegen_llvm-llvm.so”: “libLLVM-7.so: cannot open shared object file: No such file or directory”

Admin
Andreas Baumann commented on 22.08.2019 09:56

Tried with precompiled binaries (AUR package ‘rust-bin’):

https://aur.archlinux.org/packages/rust-bin/

Compiling 1.37.0 from source now results in LLVM: out of memory,
see also:

https://github.com/rust-lang/rust/issues/60294 Admin
Andreas Baumann commented on 22.08.2019 10:10

Fedora 31 will also complain, so there is a chance Rust people are actually doing something
and not just ignoring us:

https://bugzilla.redhat.com/show_bug.cgi?id=1723064 Admin
Andreas Baumann commented on 08.09.2019 14:29

Asked upstream about how rust is supposed to be built on a machine with 32-bit
address space:

https://github.com/rust-lang/rust/issues/60294

–debuginfo-level-std=1

in config.toml

works over the first out of memory situations.

Now I get:

error: failed to run custom build command for `backtrace-sys v0.1.27`

Caused by:

process didn’t exit successfully: `/build/rust/src/rustc-1.37.0-src/build/i686-unknown-linux-gnu/stage2-std/release/build/backtrace-sys-e11a26709e2be131/build-script-build` (exit code: 101)

— stdout

command did not execute successfully: “/usr/bin/cargo” “build” “–target” “x86_64-unknown-linux-gnu” “-j” “1” “–release” “–frozen” “–features” “panic-unwind backtrace profiler” “–manifest-path” “/build/rust/src/rustc-1.37.0-src/src/libstd/Cargo.toml” “–message-format” “json” expected success, got: exit code: 101

‘, /build/rust/src/rustc-1.37.0-src/vendor/cc/src/lib.rs:2398:5
stack backtrace:

0: std::panicking::default_hook::closure 1: std::panicking::default_hook
2: std::panicking::rust_panic_with_hook
3: std::panicking::continue_panic_fmt
4: std::panicking::begin_panic_fmt
5: cc::fail

         at /build/rust/src/rustc-1.37.0-src/vendor/cc/src/lib.rs:2398

6: cc::Build::compile

         at /build/rust/src/rustc-1.37.0-src/vendor/cc/src/lib.rs:951

7: build_script_build::main

         at ./build.rs:107

8: std::rt::lang_start::closure 8: std::rt::lang_start::closure

         at /rustc/eae3437dfe991621e8afdc82734f4a172d7ddf9b/src/libstd/rt.rs:64

note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I’m personally quite fed up with the quality and documentation of this compiler..
Admin
Andreas Baumann commented on 09.09.2019 06:43

cargo:warning=cc1: sorry, unimplemented: 64-bit mode not compiled in

Does this mean that the architecture triplet is wrong?
Admin
Andreas Baumann commented on 09.09.2019 18:03

Indeed. Fixed config.toml, which was completely wrong ([build] had a amd64 target,
building for two architectures instead one (i686)..
Admin
Andreas Baumann commented on 12.09.2019 07:13

pentium4 went through, trying now the sed trick above on the i686 version..
Admin
Andreas Baumann commented on 29.09.2019 18:12

error[E0428]: the name `U1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.37.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-895469ec3d111e10/out/consts.rs:2112:5

|
2110 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

   |     ------------------------------------------------------------------------------------------------------------------------------------- previous definition of the type `U1024` here

2111 | pub type P1024 = PInt; pub type N1024 = NInt;
2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;

   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this module

error[E0428]: the name `P1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.37.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-895469ec3d111e10/out/consts.rs:2113:5

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ----------------------------- previous definition of the type `P1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this module

error[E0428]: the name `N1024` is defined multiple times

  1. -&gt; /build/rust/src/rustc-1.37.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-895469ec3d111e10/out/consts.rs:2113:35

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ----------------------------- previous definition of the type `N1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this module

error: aborting due to 3 previous errors

For more information about this error, try `rustc –explain E0428`.

 Compiling strip-ansi-escapes v0.1.0

error: Could not compile `typenum`.

Admin
Andreas Baumann commented on 02.10.2019 19:32

There is no documentation how to use x.py properly, what the build does, what
the bootstrapping does. And life-patching of typenum is just the really last
straw (currently failing)..

Currently blocking:
- librsvg2 on i686 (rust-bin generates SSE2-code)
- firefox, thunderbird and friends on i686
- some random software on i686 like newsboat
Admin
Andreas Baumann commented on 03.10.2019 05:39

We should try to understand x.py

https://github.com/rust-lang/rust/blob/master/src/bootstrap/README.md

To me it looks like we can have a PKGBUILD calling each stage individually and do
the necessary patching in-between.
Admin
Andreas Baumann commented on 04.10.2019 08:06

Ok, I see several issues here:

rustc –target i686-unknown-linux-gnu –print cfg

says:

target_feature=”sse” target_feature=”sse2”

rustc –target i586-unknown-linux-gnu –print cfg

has no SSE/SSE2, so we pick:
- i686-unknown-linux-gnu for our pentium4 and
- i586-unknown-linux-gnu for our i486 and i686

see also some interesting notes in:
- https://github.com/rust-lang/rust/issues/54740 - https://internals.rust-lang.org/t/is-pentium4-still-an-appropriate-base-cpu-for-i686/7353/6

The current config.toml.patch doesn’t apply correctly and silently fails:

patching file config.toml
Hunk #1 FAILED at 2.
Hunk #2 succeeded at 21 with fuzz 2 (offset 2 lines).
1 out of 2 hunks FAILED – saving rejects to file config.toml.rej

This needs proper treatment in the build scripts, as we cannot continue building
if patches apply partially!
Admin
Andreas Baumann commented on 05.10.2019 08:57

Now I get the same typenum error also in stage2 of cargo on pentium4.

Trying the stage 2 –keep-stage 1 trick..
Admin
Andreas Baumann commented on 05.10.2019 09:11

Some internal documentation on x.py:

https://rust-lang.github.io/rustc-guide/how-to-build-and-run.html Admin
Andreas Baumann commented on 05.10.2019 12:46

Cool, so the conflicting consts.rs of typenum appears out of the blue in the middle of a stage.
So this multi-layered building will also not work.
Admin
Andreas Baumann commented on 05.10.2019 14:06

Trying an inotifywait approach watching for consts.rs to appear and calling a sed on it then:

inotifywait -mrq -e create –format %w%f $srcdir | while read -r FILE; do

case "$$FILE" in
  *consts.rs)
    echo "--&gt; patching $$FILE"
    sed -i '/pub type U1024/d;/pub type P1024/d' $FILE
esac

done

Admin
Andreas Baumann commented on 05.10.2019 17:41

The inotify-trick helped to rebuild 1.38 for pentium4.

So, rust 1.38 can only be built with rust 1.37, not with 1.38 (rebuilding itself),
see:

https://github.com/rust-lang/rust/issues/63911

This means, having a rust package building rust works, if you do it once,
otherwise I would suggest to upstream to have a rust137 and build rust138
which provides rust, so the build can be done more than once (especially
automatically).

When I use rust-bin for 1.37 I cannot build 1.38 again for i686 (out of
memory). This one I’m trying to tackle with debug_level=0 (which seems
to help). Didn’t have this problem with ‘rust’ 1.37.0 on pentium4 for
rebuilding 1.38.0, so maybe rust-bin has some bad internal properties?
Admin
Andreas Baumann commented on 06.10.2019 07:57

inotifywait and sed is in the middle of patching the consts.rs file, so you get
half of a source-file:

error: this file contains an un-closed delimiter

  1. -&gt; /build/rust/src/rustc-1.38.0-src/build/i686-unknown-linux-gnu/stage2-tools/i686-unknown-linux-gnu/release/build/typenum-483ffd21aece8552/out/consts.rs:266:56

Maybe some mandatory file locking helps?

Otherwise, I start considering a “fuse-patching” pseudo-filesystem. :-) Admin
Andreas Baumann commented on 06.10.2019 09:42

flock doesn’t help, the file is now locked, but rust sees it as a sequence of \0.
Admin
Andreas Baumann commented on 19.10.2019 18:17

The following works: wait for inotify event close_write on file consts.rs and patch
it then.
Kill the watcher (which also kills inotifywait).

Now I can rebuild rust 1.38 from 1.37, but I still have problems rebuilding 1.38
with an 1.38 compiler (*sigh*).

As we have to assume that rust 1.37 and 1.36 are broken, let’s bootstrap again a
rust 1.38 from rust-bin 1.37.
Admin
Andreas Baumann commented on 19.10.2019 18:35

Now someting hangs in the middle..
Admin
Andreas Baumann commented on 20.10.2019 14:38

upstream fixed the boostrapping 1.38 with 1.38 issue (seems to be just some
superflous unsafe directives):

# Fix bootstrap to compile with 1.38
patch -Np1 -i ../bootstrap-1.38.patch

Admin
Andreas Baumann commented on 20.10.2019 14:38

Trying again to rebuild 1.38 with 1.38 (both for i686 and pentium4) against my bootstrapped
1.38 version. When this works, I’ll build official version in the regular way..
Admin
Andreas Baumann commented on 20.10.2019 14:41

cat > config.toml <<EOF

EOF

This seems to be a new trend. I don’t like it, as it makes patching really hard..
Admin
Andreas Baumann commented on 20.10.2019 17:13

i686 1.38 rebuild of 1.38 results in:

error: Could not compile `typenum`.
warning: build failed, waiting for other jobs to finish… error: build failed
command did not execute successfully: “/usr/bin/cargo” “build” “–target” “i686-unknown-linux-gnu” “-j” “16” “–release” “–frozen” “–manifest-path” “/build/rust/src/rustc-1.38.0-src/src/tools/cargo/Cargo.toml” “–message-format” “json” expected success, got: exit code: 101
failed to run: /build/rust/src/rustc-1.38.0-src/build/bootstrap/debug/bootstrap install -j16
Build completed unsuccessfully in 0:38:12

no error messages, exit code 101 means what exactly?

Bing Cache

 72 Packages: StableBug ReportMediumLow [mpd] icu version mismatch Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by bill auger - 13.05.2019
Last edited by Andreas Baumann - 28.08.2019
 FS#72  - [mpd] icu version mismatch

$ mpd
mpd: error while loading shared libraries: libicui18n.so.63: cannot open shared object file: No such file or directory

Closed by Andreas Baumann
28.08.2019 16:59
Reason for closing: Fixed
Additional comments about closing:

works for me after the rebuild.

  Comments (2)
  Related Tasks (0/0)

Levi commented on 13.05.2019 20:33

This also affects libreoffice from libreoffice-stable. Run it from a terminal and the splash screen briefly loads before closing, and it spits out to STDERR:
[quote]usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libicuuc.so.63: cannot open shared object file: No such file or directory[/quote]

My icu package is currently at version 64.2-1.0 and from the core repo (nothing in testing, apparently). I’m currently on the pentium4 binary branch, by the way, but I think this issue affects us all at present.

I suspect if the maintainer just rebuilds libreoffice-stable and mpd with icu 64.2 in the environment it may resolve this. Looking at the libreoffice web site, version 6.1.6 is already available for download, while I still have 6.1.5 installed and there’s nothing in the download tubes just yet. Although 6.1.5 is still available on libreoffices download page along with 6.1.6 and 6.2.3, so maybe we don’t get the upgrade till 6.1.5 expires, I’ve not checked before. I also can’t find when anything libreoffice produces got released; their release notes don’t express patch levels and they don’t expose their download folder for my perusal. I did manage to find their announcements for what becomes libreoffice-fresh on their twitter feed, but they only announce the fresh releases there. Presumably 6.1.6 got released following 6.2.3, since presumably it fixes the same bugs backported though.
Admin
Andreas Baumann commented on 28.08.2019 16:58

Should be solved with rebuilding libreoffice, mpd etc.

Google Cache

 73 PackagesBug ReportMediumLow [gajim] fails to launch when (optional) gupnp-igd is in ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by bill auger - 13.05.2019
Last edited by Andreas Baumann - 02.10.2019
 FS#73  - [gajim] fails to launch when (optional) gupnp-igd is installed

$ gajim
No translations found
Dirs searched: [PosixPath(’/usr/local/share’), PosixPath(’/usr/share’), PosixPath(’/usr/share/gdm’), PosixPath(’/var/lib/menu-xdg’)]

(gajim:1588): dbind-WARNING : 15:14:29.481: Couldn’t connect to accessibility bus: Failed to connect to socket /tmp/dbus-Nv1LTXmb8O: Connection refused (gajim:1588): WARNING **: 15:14:29.534: Failed to load shared library ‘libgupnp-igd-1.0.so.4’ referenced by the typelib: libgupnp-1.2.so.0: cannot open shared object file: No such file or directory
/usr/lib/python3.7/site-packages/gajim/common/app.py:281: Warning: cannot retrieve class for invalid (unclassed) type ‘void’

gupnp_igd = GUPnPIgd.SimpleIgd()

Traceback (most recent call last):

File "/usr/lib/python3.7/site-packages/gajim/application.py", line 185, in _startup
  app.detect_dependencies()
File "/usr/lib/python3.7/site-packages/gajim/common/app.py", line 281, in detect_dependencies
  gupnp_igd = GUPnPIgd.SimpleIgd()

TypeError: could not get a reference to type class
Traceback (most recent call last):

File "/usr/lib/python3.7/site-packages/gajim/application.py", line 220, in _activate
  self.interface = Interface()
File "/usr/lib/python3.7/site-packages/gajim/gui_interface.py", line 2615, in __init__
  cfg_was_read = parser.read()
File "/usr/lib/python3.7/site-packages/gajim/common/optparser.py", line 86, in read
  self.update_config(old_version, new_version)
File "/usr/lib/python3.7/site-packages/gajim/common/optparser.py", line 158, in update_config
  caps_cache.capscache.initialize_from_db()

AttributeError: ‘NoneType’ object has no attribute ‘initialize_from_db’ Traceback (most recent call last):

File "/usr/lib/python3.7/site-packages/gajim/application.py", line 269, in do_shutdown
  app.logger.commit()

AttributeError: ‘NoneType’ object has no attribute ‘commit’

Closed by Andreas Baumann
02.10.2019 19:36
Reason for closing: Fixed
Additional comments about closing:

Seems to work on pentium4/stable. Feel free to reopen if you it crashes
for you..

Google Cache

 74 Packages: StableBug ReportMediumLow webkit2gtk requires SSE2 Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 16.05.2019
 FS#74  - webkit2gtk requires SSE2

– Performing Test HAVE_SSE2_EXTENSIONS
– Performing Test HAVE_SSE2_EXTENSIONS - Failed
CMake Error at CMakeLists.txt:115 (message):

SSE2 support is required to compile WebKit

not quite clear yet, what happens, if it gets disabled forcefully..

  Comments (5)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 16.05.2019 18:43

Let’s see, what happens if we just comment out the SSE2 test in CMakeLists.txt.. :-) Admin
Andreas Baumann commented on 17.05.2019 11:54

Rebuilding runs in issues like:

make[2]: *** No rule to make target ‘JavaScriptCore-4.0.gir’, needed by ‘WebKit2-4.0.gir’. Stop.

Using in ‘build’ make JavaScriptCore-4-gir VERBOSE=1 reveils the true nature of the bug:

/usr/lib/gcc/i686-pc-linux-gnu/8.3.0/include/stddef.h:435: syntax error, unexpected identifier in ' float128 max_align_f128 attribute1)));’ at ‘__float128’

So again, the 128-bit alignment hack in glibc spreading everywhere.
Admin
Andreas Baumann commented on 17.05.2019 11:56

Also the make error sounds suspicious, like cmake/make generated files are not really tested.
Admin
Andreas Baumann commented on 17.05.2019 11:59

The 128-alignment issue is hopefully just a warning..
Admin
Andreas Baumann commented on 17.05.2019 12:55

patched build in the queue..

Google Cache

1) aligned(alignof(float128
 75 Packages: Build-listBug ReportMediumLow openjdk8/10/11/12 break with march=pentium4 optimizatio ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 18.05.2019
Last edited by Andreas Baumann - 16.08.2019
 FS#75  - openjdk8/10/11/12 break with march=pentium4 optimization

This blocks ant, needed for building libreoffice.
Closed by Andreas Baumann
16.08.2019 13:55
Reason for closing: Fixed
Additional comments about closing:

fixed for 8, 10, 11 and 12. Not for 7.

  Comments (34)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 18.05.2019 18:18

mmh. java is fine.

java -version
openjdk version “1.8.0_212” OpenJDK Runtime Environment (build 1.8.0_212-b01)
OpenJDK Server VM (build 25.212-b01, mixed mode)

javac
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (os_linux_x86.cpp:291), pid=124, tid=0xf6dc1b40
# fatal error: An irrecoverable SI_KERNEL SIGSEGV has occurred due to unstable signal handling in this distribution.
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b01) (build 1.8.0_212-b01)
# Java VM: OpenJDK Server VM (25.212-b01 mixed mode linux-x86 )
# Core dump written. Default location: /build/libreoffice-still/core or core.124
#
# An error report file with more information is saved as:
# /build/libreoffice-still/hs_err_pid124.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp #
Aborted (core dumped)

ant
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (os_linux_x86.cpp:291), pid=155, tid=0xf6d4fb40
# fatal error: An irrecoverable SI_KERNEL SIGSEGV has occurred due to unstable signal handling in this distribution.
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b01) (build 1.8.0_212-b01)
# Java VM: OpenJDK Server VM (25.212-b01 mixed mode linux-x86 )
# Core dump written. Default location: /build/libreoffice-still/core or core.155
#
# An error report file with more information is saved as:
# /build/libreoffice-still/hs_err_pid155.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp #
Aborted (core dumped)

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x897c76]
V [libjvm.so+0x36392a]
V [libjvm.so+0x71341f] JVM_handle_linux_signal+0x6bf
V [libjvm.so+0x70507f]
C [linux-gate.so.1+0×950] __kernel_rt_sigreturn+0×0

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j java.lang.System.nanoTime()J+0
j java.net.URLClassLoader.defineClass(Ljava/lang/String;Lsun/misc/Resource;)Ljava/lang/Class;+0
j java.net.URLClassLoader.access$100(Ljava/net/URLClassLoader;Ljava/lang/String;Lsun/misc/Resource;)Ljava/lang/Class;+3
j java.net.URLClassLoader$1.run()Ljava/lang/Class;+43
j java.net.URLClassLoader$1.run()Ljava/lang/Object;+1
v ~StubRoutines::call_stub
j java.security.AccessController.doPrivileged(Ljava/security/PrivilegedExceptionAction;Ljava/security/AccessControlContext;)Ljava/lang/Object;+0
j java.net.URLClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;+13
j java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;+70
j sun.misc.Launcher$AppClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;+81
j java.lang.ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;+3
v ~StubRoutines::call_stub
j com.sun.tools.javac.main.Main.(Ljava/lang/String;Ljava/io/PrintWriter;)V+5
j com.sun.tools.javac.main.Main.(Ljava/lang/String;)V+13
j com.sun.tools.javac.Main.compile([Ljava/lang/String;)I+6
j com.sun.tools.javac.Main.main([Ljava/lang/String;)V+1
v ~StubRoutines::call_stub
Admin
Andreas Baumann commented on 18.05.2019 18:19

well. Java errors, hard to debug..
Admin
Andreas Baumann commented on 18.05.2019 18:21

Installing the i686 version in the pentium4 chroot also segfaults..
Admin
Andreas Baumann commented on 18.05.2019 18:25

Java 686 doesn’t segfault on a real i686 installed system. So, I fear, some library in pentium4
is causing java to segfault.
Admin
Andreas Baumann commented on 18.05.2019 18:36

Event: 0.057 Thread 0xf6b07c00 Exception <a> (0xd7b86ea0) thrown at [/build/java8-openjdk/src/jdk8u-jdk8u212-b01/hotspot/src/share/vm/prims/jni.cp
Event: 0.057 Thread 0xf6b07c00 Exception </a><a> (0xd7b87170) thrown at [/build/java8-openjdk/src/jdk8u-jdk8u212-b01/hotspot/src/share/vm/prims/jni.cpp, line 4012]
Event: 0.231 Thread 0xf6b07c00 Exception </a><a> (0xd7cc0498) thrown at [/build/java8-openjdk/src/jdk8u-jdk8u212-b01/hotspot/src/share/vm/prims/jvm.cpp, line 1502]

mmh. this sounds quite internal..
</a>
Admin
Andreas Baumann commented on 18.05.2019 18:50

pentium$:
javac -version
javac 11.0.3

why is libreoffice built with java 8?
Admin
Andreas Baumann commented on 18.05.2019 19:00

weird: on my pentium4 test machine with jdk 8 and 11 installed, I can switch to java 8
and everything is fine.
Admin
Andreas Baumann commented on 18.05.2019 19:03

I remember issues with shared libraries and the way the Jvm is bootstrapping. For
instance not having a /proc causes trouble of this sort. But we have a /proc
(we are using arch-chroot and a bind mount point).
Admin
Andreas Baumann commented on 18.05.2019 19:07

using java 11 and javac 11 on pentium4 works..
Admin
Andreas Baumann commented on 18.05.2019 19:08

..and now we get to “find the 10 differences in this picture”. :-) Admin
Andreas Baumann commented on 18.05.2019 19:14

The only thing I can think of is a different kernel (with more protection enabled):

https://bugs.openjdk.java.net/browse/JDK-8023956 https://bugs.openjdk.java.net/browse/JDK-8181068

This cries for building it on a real Pentium4 or on a properly emulated one, not
in a chroot.
Admin
Erich Eckner commented on 22.05.2019 04:34

&gt; using java 11 and javac 11 on pentium4 works..

why not simply pin the java version to 11, then?
Admin
Andreas Baumann commented on 06.06.2019 18:19

When installing the i686 version of glibc and openjdk8 there is no segfault!
So this sounds more like a new glibc and optimization triggering something in java..
Admin
Andreas Baumann commented on 07.06.2019 16:54

Actually also original SUN java 7 segfaults with this glibc.
Rebuilding glibc didn’t help. So I’m pretty sure it’s some protection thingy
getting into the way of old Java JDKs (because they always pushed their limits
and did funny tricks in the past).
Luke commented on 18.06.2019 18:27

Erich Eckner,
Ant is still broken with pentium4 build of java 11 (i686 works).

$ archlinux-java status
Available Java environments:

java-11-openjdk (default)

Admin
Andreas Baumann commented on 19.06.2019 17:57

19:40 &lt; slacka123&gt; should use “-march=i686 -msse2 -mtune=generic -mfpmath=sse -mstackrealign” instead?
19:54 &lt; slacka123&gt; Yes, it does - https://bugs.documentfoundation.org/show_bug.cgi?id=108619
19:54 &lt; phrik&gt; Title: 108619 – (32bitjavacrash) Java Crash on x86 in jfw_plugin_startJavaVirtualMachine

             w/ recent linux kernels (at bugs.documentfoundation.org)

19:55 &lt; slacka123&gt; Fedora 30 also needs that kernel parameter, “stack_guard_gap=1” to run/build

                 LibreOffice and other java apps

… 19:56 &lt; slacka123&gt; but i686 arch32 also needs it

from the chat protocol: https://mirror.archlinux32.org/irc-logs/%23archlinux32/2019-06-19.html#19:39:59 Admin
Andreas Baumann commented on 21.06.2019 08:29

See: https://src.fedoraproject.org/rpms/glibc/blob/master/f/glibc.spec Admin
Andreas Baumann commented on 21.06.2019 12:23

Thanks slacka123 for the hint. This seems to solve the java/javac crashes.

It’s fixed now in staging and will soon hop into testing.
Admin
Andreas Baumann commented on 11.08.2019 06:03

The segfaults persist through all pentium4 versions of the openjdk.
Additionally now also the 7 version of i686 and pentium4 are segfaulting.
Admin
Andreas Baumann commented on 11.08.2019 07:11

jkd7 also cannot find libattr:

https://patchwork.openembedded.org/patch/110857/ Admin
Andreas Baumann commented on 11.08.2019 07:13

On 64-bit it complains about ant:

error: target not found: apache-ant&gt;=1.8.1

flagged out-of-date upstream, unusable currently for bootstrapping.
Admin
Andreas Baumann commented on 11.08.2019 07:56

https://bugs.archlinux.org/task/63430 Admin
Andreas Baumann commented on 11.08.2019 07:56

configure: Found potential Boot JDK using java© in PATH
configure: Potential Boot JDK found at /usr/lib/jvm/java-8-openjdk is incorrect JDK version (#); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/java-8-openjdk)
configure: Potential Boot JDK found at /usr/lib/jvm/java-8-openjdk is incorrect JDK version (#); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/default-runtime)
configure: Potential Boot JDK found at /usr/lib/jvm/default-runtime is incorrect JDK version (#); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/default)
configure: Potential Boot JDK found at /usr/lib/jvm/default is incorrect JDK version (#); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: Could not find a valid Boot JDK.
configure: This might be fixed by explicitely setting –with-boot-jdk
configure: error: Cannot continue
configure exiting with result code 1
Admin
Andreas Baumann commented on 11.08.2019 18:02

building on i686 (where openjdk8 still works) and using makepkg.conf with pentium4
cflags gives a package with wrong architecture though, but running in a pentium4
chroot if installed.

Though when I try to rebuild it with the ‘cross-compiled’ package in a pentium4
chroot, I get:

checking headful support… include support for both headful and headless
configure: Found potential Boot JDK using configure arguments
configure: Potential Boot JDK found at /usr/lib/jvm/java-8-openjdk is incorrect JDK version (#); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: error: The path given by –with-boot-jdk does not contain a valid Boot JDK configure exiting with result code 1

Inside I have a hs_err_pid3361.log showing again the darn SI_KERNEL SIGSEGV.

This problem is over my head (and skills).
Admin
Andreas Baumann commented on 12.08.2019 15:26

This sounds interesting:

https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3533

related question: is -march=pentium4 changing the stack layout?
Admin
Andreas Baumann commented on 12.08.2019 15:28

Should we force stack alignment globally for all libraries which could potentially be
called from java with -mstack-alignment=16? This could break havock on other software..
Admin
Andreas Baumann commented on 12.08.2019 15:28

Also interesting:

https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3533 Admin
Andreas Baumann commented on 12.08.2019 15:30

Also: -mincoming-stack-boundary=2

https://bugs.gentoo.org/attachment.cgi?id=522650&amp;action=diff Admin
Andreas Baumann commented on 12.08.2019 16:00

So -mstackrealign in the glibc flags helps to realign the stack, so that 4 and 16 byte stacks
can coexist, but Java generates it’s own executable code, which doesn’t respect that?
Why should -mincoming-stack-boundary=2 help then?
I’ll test again a double compilation via working i686 chroot to pentium4 (with -mincoming-stack-boundary=2 in the PKGBUILD of java8-openjdk), then see if it can rebuild itself in a pentium4
chroot.
Admin
Andreas Baumann commented on 13.08.2019 04:48

Apparently this helps, thanks to the Gentoo guys. :-) Admin
Andreas Baumann commented on 13.08.2019 05:05

Now to jdk10, jdk11 and jdk12 (weirdly enough there is no jdk9?).
Admin
Andreas Baumann commented on 15.08.2019 07:32

a working JDK8 for pentium4 hit staging. now for the other versions..
Admin
Andreas Baumann commented on 15.08.2019 11:40

This helps against GOT/PLT errors:

if test ${CARCH} = i686 -o ${CARCH} = pentium4; then
  echo "Removing '-fno-plt' from CFLAGS and CXXFLAGS to prevent build fail with th
  _CFLAGS=${CFLAGS/-fno-plt/}
  _CXXFLAGS=${CXXFLAGS/-fno-plt/}
fi

Admin
Andreas Baumann commented on 15.08.2019 12:03

Finished building targets ‘images docs’ in configuration ‘linux-x86-normal-server-release’ find: &lt;80&gt;&lt;98&gt;../jdk10u-jdk-10.0.2+13/build/linux-i386-normal-server-release/images&lt;80&gt;&lt;99&gt;: No such file or directory
ESC[1mESC[31m==&gt; ERROR:ESC[m^OESC[1m A failure occurred in build().ESC[m^O
ESC[1m Aborting…ESC[m^O
==&gt; ERROR: Build failed, check /var/lib/archbuild/staging-i686/abaumann/build
(END)

needs:

case “${CARCH}” in

x86_64) _JARCH='x86_64';;
i486|i686|pentium4)   _JARCH='x86';;

esac

Google Cache

 76 Packages: StableBug ReportMediumLow libreoffice-fresh needs to be rebuild against icu Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Raphael Scholer - 25.05.2019
 FS#76  - libreoffice-fresh needs to be rebuild against icu

  Comments (1)
  Related Tasks (0/0)

Levi commented on 25.05.2019 18:22

This bug is already captured 90% by https://bugs.archlinux32.org/index.php?do=details&amp;task_id=72 (see my comment underneath it), although to be fair I noted it against libreoffice-stable since that’s what I use.

Google Cache

 77 Packages: Build-listBug ReportMediumLow librsvg doesn't rebuild Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 30.05.2019
 FS#77  - librsvg doesn’t rebuild

  1. -&gt; /build/librsvg/src/librsvg/target/release/build/typenum-ff577e94a786118f/out/consts.rs:2113:5

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ----------------------------- previous definition of the type `P1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this module

error[E0428]: the name `N1024` is defined multiple times

  1. -&gt; /build/librsvg/src/librsvg/target/release/build/typenum-ff577e94a786118f/out/consts.rs:2113:35

|
2111 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ----------------------------- previous definition of the type `N1024` here

2112 | pub type U1024 = UInt, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;, B0&gt;;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;

   |                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this module

error: aborting due to 3 previous errors

For more information about this error, try `rustc –explain E0428`.
error: Could not compile `typenum`.

Caused by:

process didn't exit successfully: `rustc --crate-name typenum /build/.cargo/registry/src/github.com-1ecc6299db9ec823/typenum-1.10.0/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=045a2ce7f5cfaab5 -C extra-filename=-045a2ce7f5cfaab5 --out-dir /build/librsvg/src/librsvg/target/release/deps -L dependency=/build/librsvg/src/librsvg/target/release/deps --cap-lints allow -C target-cpu=pentium3 -C target-feature=-sse2` (exit code: 1)

warning: build failed, waiting for other jobs to finish… error: build failed
make[2]: * [Makefile:1934: /build/librsvg/src/librsvg/target/release/librsvg_internals.a] Error 101
make[2]: Leaving directory ‘/build/librsvg/src/librsvg’ make[1]:
* [Makefile:1438: all-recursive] Error 1
make[1]: Leaving directory ‘/build/librsvg/src/librsvg’ make: *** [Makefile:931: all] Error 2

The same error with typenum as when bootstrapping rust in stage 2.

librsvg is very important as it blocks tons of other stuff (so why
again was it written in Rust?!)

I might have seen a Debian patch for it, but Debian goes a “complete
Rust micro-packaging” way, not sure whether we can apply it here?

  Comments (1)
  Related Tasks (0/0)

Levi commented on 30.05.2019 18:26

Since it looks to me like it’s redefining P1024 and N1024 the same, can’t you just eliminate one of these definitions. Sure, it makes a patch you’d have to maintain henceforth until they fix this upstream, and I don’t understand what kind of preprocessing is ending up with this particular duplication, but deleting a line is about the simplest patch you could maintain.

Google Cache

 78 Packages: StableBug ReportMediumLow The qt5 group contains packages of different versions. Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Erling Hellenäs - 05.07.2019
 FS#78  - The qt5 group contains packages of different versions.

The qt5 group contains a qt5-base which is of a later revision, 5.12.4 instead of 5.12.3. pyside2 is also of a this later revision, but I don’t use it. I guess the group should be fixed.

Workaround: I downgraded qt5-base and it is working again.

I get this error: sddm-greeter[441]: Cannot mix incompatible Qt library (version 0x50c03) with this library (version 0x50c04)
Then systemd dumps core.

Excerpt from my journal: External Link

The group definition as seen when installing the group with pacman: External Link

My architecture is i686.

I consider it critical since QT is not working.

Google Cache

 79 Packages: StableBug ReportMediumLow trojita libstdc++ ABI mismatch Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 06.07.2019
Last edited by Andreas Baumann - 11.08.2019
 FS#79  - trojita libstdc++ ABI mismatch

trojita
trojita: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.26’ not found (required by /usr/lib/libQt5WebKit.so.5)
Closed by Andreas Baumann
11.08.2019 06:01
Reason for closing: Not a bug
Additional comments about closing:

Temporary glitch, glibc got published, trojita didn’t get rebuild.

  Comments (1)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 06.07.2019 09:17

This goes into the same ABI mismatches as Qt5. The problem here is: qt5-webkit refuses
to build on machines without SSE2 currently, but glibc is supposed to be backwards compatible,
but not libstdc++).

Google Cache

 80 Packages: Build-listBug ReportMediumLow kate refuses to build due to some broken shared ... Closed
100%
Task Description

07.07.2019 -  FS#80  - kate refuses to build due to some broken shared library dependencies. /usr/bin/ld: warning: libgit2.so.27, needed by …

 81 Packages: StableBug ReportMediumLow KDE/Plasma crashes on startup (i686) Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 07.07.2019
 FS#81  - KDE/Plasma crashes on startup (i686)

Application: ksplashqml (ksplashqml), signal: Aborted
Using host libthread_db library “/usr/lib/libthread_db.so.1”.
[Current thread is 1 (Thread 0xb21d5900 (LWP 427))]

Thread 3 (Thread 0xaa75cb40 (LWP 429)):
#0 0xb4b95418 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#1 0xb4b959f7 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0xb4b95be6 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3 0xb6e75ce5 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5
#4 0xb6e18ef5 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5
#5 0xb6c5fe1a in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6 0xb66317c3 in ?? () from /usr/lib/libQt5Qml.so.5
#7 0xb6c611cc in ?? () from /usr/lib/libQt5Core.so.5
#8 0xb5e34018 in start_thread () from /usr/lib/libpthread.so.0
#9 0xb697c25a in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0xb1a18b40 (LWP 428)):
#0 0xb7f6a82d in kernel_vsyscall ()
#1 0xb6972873 in poll () from /usr/lib/libc.so.6
#2 0xb550c6ce in ?? () from /usr/lib/libxcb.so.1
#3 0xb550e864 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#4 0xb1bad3da in ?? () from /usr/lib/libQt5XcbQpa.so.5
#5 0xb6c611cc in ?? () from /usr/lib/libQt5Core.so.5
#6 0xb5e34018 in start_thread () from /usr/lib/libpthread.so.0
#7 0xb697c25a in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0xb21d5900 (LWP 427)):
[KCrash Handler]
#6 0xb7f6a82d in
kernel_vsyscall ()
#7 0xb68c4376 in raise () from /usr/lib/libc.so.6
#8 0xb68ae299 in abort () from /usr/lib/libc.so.6
#9 0xb6c1f873 in QMessageLogger::fatal(char const*, …) const () from /usr/lib/libQt5Core.so.5
#10 0xb6387c44 in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /usr/lib/libQt5Qml.so.5
#11 0xb64298d6 in QJSEngine::QJSEngine(QJSEnginePrivate&amp;, QObject*) () from /usr/lib/libQt5Qml.so.5
#12 0xb6575fcd in QQmlEngine::QQmlEngine(QObject*) () from /usr/lib/libQt5Qml.so.5
#13 0xb6888bc4 in KDeclarative::QmlObjectSharedEngine::QmlObjectSharedEngine(QObject*) () from /usr/lib/libKF5Declarative.so.5
#14 0xb7f0fb00 in KQuickAddons::QuickViewSharedEngine::QuickViewSharedEngine(QWindow*) () from /usr/lib/libKF5QuickAddons.so.5
#15 0x0040a29b in ?? ()
#16 0x00408e7a in ?? ()
#17 0x004095a2 in ?? ()
#18 0x004081de in ?? ()
#19 0xb68af7b9 in __libc_start_main () from /usr/lib/libc.so.6
#20 0x004082e5 in _start ()
[Inferior 1 (process 427) detached]

Google Cache

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

 83 Packages: StableBug ReportMediumLow kdeinit5 is filling the systemd journal with nonsensica ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 13.07.2019
 FS#83  - kdeinit5 is filling the systemd journal with nonsensical messages

Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: ()
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: ()
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: ()
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: ()
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: (QUrl(”tags:/”))
Jul 13 20:12:45 arch32-stable-pentium4 kdeinit5[1037]: ()

225 root      20   0  359832 225172 224128 S  24.5  29.5   0:45.52 systemd-journal 

Upstream too? Or is it fast enough if one core is dedicated to output
nonsensical output.. :-&gt;

Google Cache

 84 PackagesBug ReportMediumLow Unknown bug FS#84 Closed
100%
Task Description

no task description

 85 Packages: StableBug ReportMediumLow [wireguard-arch] Package not being updated alongside ke ...Closed
100%
Task Description

The last update to this package was August 25, despite several new kernel builds since this. As a result, the package does not work and users must use …

 86 Packages: StableBug ReportMediumLow newsboat contains SSE2 instuctions Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 14.09.2019
Last edited by Andreas Baumann - 14.09.2019
 FS#86  - newsboat contains SSE2 instuctions

shell&gt; newsboat

Program received signal SIGILL, Illegal instruction.
0x005f5cd9 in ?? ()
=&gt; 0x005f5cd9: f2 0f 10 06 movsd (%esi),%xmm0
(gdb) bt
#0 0x005f5cd9 in ?? ()
#1 0x005f40fa in ?? ()
#2 0x005f3f3b in ?? ()
#3 0x0072e9fd in ?? ()
#4 0×00661600 in ?? ()
#5 0×00659435 in ?? ()
#6 0x0061fe88 in ?? ()
#7 0x0065770c in ?? ()
#8 0x005ea416 in ?? ()
#9 0x0044ca68 in ?? ()
#10 0xb76f9859 in __libc_start_main () from /usr/lib/libc.so.6
#11 0x0044da75 in ?? ()

This actually looks like glibc got a SSE2 infection on i686.

Google Cache

 87 PackagesBug ReportMediumLow firefox doesn't rebuild Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 21.09.2019
Last edited by Andreas Baumann - 21.09.2019
 FS#87  - firefox doesn’t rebuild

OOM when build gkrust:

patching out debug_level=2 in moz.configure/toolchain.configure

thanks BoidLinux for the hint.

  Comments (3)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 21.09.2019 17:05

A test is executed testing the generated Gecko rust library (a static library), whether
it contains references to networking functions, this fails on IA32:

https://hg.mozilla.org/mozilla-central/rev/47cd8671b12c

$(call py_action,check_binary,–target –networking $@)

Solution is just not to execute this check in config/makefiles/rust.mk
Admin
Andreas Baumann commented on 21.09.2019 17:08

187:52.88 toolkit/library/libxul.so
190:00.47 readelf: Error: Unable to seek to 0x801db328 for section headers
190:01.36 out of memory allocating 3761314508 bytes after a total of 1595923192 bytes
190:01.47 File “/build/firefox/src/firefox-69.0.1/python/mozbuild/mozbuild/action/check_binary.py”, line 361, in

=&gt; python/readelf combo reads whole generated libxul.so into memory in order to do
some ELF fidding.

190:01.48 make[4]: *** [/build/firefox/src/firefox-69.0.1/config/rules.mk:661: libxul.so] Error 1

shows us:

$(SHARED_LIBRARY): $(OBJS) $(RESFILE) $(RUST_STATIC_LIB) $(STATIC_LIBS) $(EXTRA_DEPS) $(GLOBAL_DEPS)

      $(REPORT_BUILD)

ifndef INCREMENTAL_LINKER

      $(RM) $@

endif

      $(MKSHLIB) $($@_$(OBJS_VAR_SUFFIX)) $(RESFILE) $(LDFLAGS) $(STATIC_LIBS) $(RUST_STATIC_LIB) $(SHARE
      $(call py_action,check_binary,--target $@)

Trying to comment that out too (the python check).
Admin
Andreas Baumann commented on 22.09.2019 07:46

Now libxul.so misses some libraries, like libmozsandbox.so, liblgpllibs.so, … The libraries exists, but most likely libxul.so cannot find them (rpath ELF fiddling?).

As a workaround I’ll set LD_LIBRARY_PATH=/usr/lib/firefox in the startup wrapper
scripts /usr/bin/firefox.

Google Cache

 88 PackagesBug ReportMediumLow Unknown Bug FS#88 Closed
100%
Task Description

no task description

 89 PackagesBug ReportMediumLow Unknown Bug FS#89 Closed
100%
Task Description

no task description

 90 PackagesBug ReportMediumLow Unknown Bug FS#90 Closed
100%
Task Description

no task description

 91 Packages: StableBug ReportMediumLow [python2]: segfault Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by bill auger - 12.10.2019
 FS#91  - [python2]: segfault

i am trying to build calibre for i686 - using the arch PKGBUILD for v3.48.0, and also the latest 4.1.0 - python2 segfults immediately in build()

possibly related to #20 https://bugs.archlinux32.org/index.php?do=details&amp;task_id=20

“line 86” below depends on the PKGBUILD - it is the command:

LANG=’en_US.UTF-8’ python2 setup.py build

$ makepkg -sr
….
==&gt; Starting build()…

*
* Running build
*

/home/auser/calibre/PKGBUILD: line 86: 7793 Segmentation fault (core dumped) LANG=’en_US.UTF-8’ python2 setup.py build
==&gt; ERROR: A failure occurred in build().

  Aborting...

$ cd src/calibre-3.48.0/
$ LANG=’en_US.UTF-8’ python2 setup.py build

*
* Running build
*

Segmentation fault (core dumped)

Google Cache

 92 PackagesBug ReportMediumLow nfs mounts with sec=krb5 fail with 'stale file handle'  ...Closed
100%
Task Description

Attached to Project: Archlinux32
Opened by Markus Schaaf - 22.10.2019
 FS#92  - nfs mounts with sec=krb5 fail with ‘stale file handle’ for everyone but root

rpc.gssd bug due to missing syscall (setgroups). See https://bugzilla.linux-nfs.org/show_bug.cgi?id=340 `journalctl –unit=rpc-gssd.service` shows:

WARNING: unable to drop supplimentary groups!
WARNING: failed to change identity: Function not implemented

Until a fixed upstream release, use
$ cat abs/packages/nfs-utils/trunk/setgroups32.patch
— nfs-utils-2.4.1/utils/gssd/gssd_proc.c.orig 2019-10-22 11:26:48.059877484 +0200
+++ nfs-utils-2.4.1/utils/gssd/gssd_proc.c 2019-10-22 11:28:03.874553996 +0200
@@ -437,7 +437,7 @@

    int res;
    /* drop list of supplimentary groups first */

- if (syscall(SYS_setgroups, 0, 0) != 0) {
+ if (syscall(SYS_setgroups32, 0, 0) != 0) {

            printerr(0, "WARNING: unable to drop supplimentary groups!");
            return errno;
    }

Google Cache

 94 Packages: TestingBug ReportMediumLow Weechat needs a rebuild Closed
100%
Task Description

Since the uprgade to python from testing, weechat has broken it’s python support, which at least knocks out the plugin I use to keep in touch with my old workmates over slack.

# weechat
|   ___       __         ______________        _____ 
|   __ |     / /___________  ____/__  /_______ __  /_
|   __ | /| / /_  _ \  _ \  /    __  __ \  __ `/  __/
|   __ |/ |/ / /  __/  __/ /___  _  / / / /_/ // /_  
|   ____/|__/  \___/\___/\____/  /_/ /_/\__,_/ \__/  
| WeeChat 2.6 [compiled on Nov 12 2019 13:06:27]
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| Error: unable to load plugin "/usr/lib/weechat/plugins/python.so": libpython3.7m.so.1.0: cannot open shared object file:
| No such file or directory

Inside /usr/lib/weechat/plugins there is a file named python.so, but its not any kind of link. I expect it to be fixed up if it were to be rebuilt.

 98 Packages: TestingBug ReportMediumLow swap encryption fails Closed
100%
Task Description

I tried to get encrypted swap following the guide in the wiki.

However, ultimately,

/usr/lib/systemd/systemd-cryptsetup attach 'swap' '/dev/disk/by-uuid/13b0e159-8573-40f8-a308-b34f1bbf1a6f' '/dev/urandom' 'swap,offset=2048'

fails, which works on upstream archlinux. It gives:

Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/disk/by-uuid/13b0e159-8573-40f8-a308-b34f1bbf1a6f.
device-mapper: reload ioctl on   failed: No such file or directory
Failed to activate with key file '/dev/urandom'. (Key file missing?)
Please enter passphrase for disk Ultra_Line (swap): 
Loading of cryptographic parameters failed: Invalid argument

In the middle, it asks for a passphrase. On archlinux, the output is:

Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/loop0.

are we missing ciphers here somewhere (where?)?

As usual (for my boxes), everything is up-to-date on that machine:
cryptsetup 2.2.2-1.0
linux 5.1.15.arch1-1.0
systemd 243.162-2.0

Cheers,
Erich

Showing tasks 51 - 100 of 350 Page 2 of 7 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing