no task description

It is an i686-system.

steps to reproduce:

    1) # pacman -Syyuu base
    2) # pacman -S gmtp
    3) $ gmtp

expected result:

    Start screen of gmtp appears.

actual result:

    $ gmtp
    gmtp: error while loading shared libraries: libFLAC.so.8: cannot open shared object file: No such file or directory

gmtp in extra-staging works though

$ mc
mc: symbol lookup error: mc: undefined symbol: g_string_new_take

$ mcedit
mcedit: symbol lookup error: mcedit: undefined symbol: g_string_new_take

it is not possible to enable staging

$ sudo pacman -Syuu
:: Synchronizing package databases...
 core-staging is up to date
 core is up to date
 extra-staging                      2.5 MiB  2.22 MiB/s 00:01 [##################################] 100%
 extra is up to date
 community-staging is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
:: There are 2 providers available for dbus-units:
:: Repository core-staging
   1) dbus-broker-units  2) dbus-daemon-units

Enter a number (default=1): 
looking for conflicting packages...
:: cryptsetup and mkinitcpio are in conflict. Remove mkinitcpio? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'initramfs' required by linux

[tutorial ] Saved pickle file: citations.pickle
[tutorial ] Exception occurred:
[tutorial ] File “/usr/lib/python2.7/site-packages/sphinx/environment/init.py”, line 152, in dump
[tutorial ] pickle.dump(env, f, pickle.HIGHEST_PROTOCOL)
[tutorial ] MemoryError
[tutorial ] The full traceback has been saved in /tmp/sphinx-err-kSNZ9A.log, if you want to report the issue to the developers.
[tutorial ] Please also report this if it was a user error, so that a better error message can be provided next time.
[tutorial ] A bug report can be filed in the tracker at . Thanks!
Build finished. The built documents can be found in /build/sagemath-doc/src/sage-8.1/src/doc/html/ja/tutorial
/startdir/PKGBUILD: line 79: 2540 Segmentation fault (core dumped) python2 sage_setup/docbuild –no-pdf-links -k all html
==> ERROR: A failure occurred in build().

  Aborting...

==> ERROR: Build failed, check /data/archbuild/staging-i686/copy/build

Bing Cache

Starting check()… WARNING [pifpaf.drivers] `psutil.Popen(pid=2683, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2671, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2669, status=’terminated’)` is already gone, sending SIGKILL to its process group
ERROR [pifpaf] Error while running command: [b’/usr/bin/pg_ctl’, ‘-w’, ‘-o’, ‘-k /tmp/tmp5_5e9_hy -p 5432 -h “127.0.0.1”‘, ‘start’]
createdb: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/run/postgresql/.s.PGSQL.5432”? ERROR: A failure occurred in check().
Aborting…
ERROR: Build failed, check /data/archbuild/staging-i686/arch32/build

Disabling tests for now.

  Comments (1)
  Related Tasks (0/0)

Admin
Andreas Baumann commented on 15.02.2018 16:56

Didn’t pifpaf itself had problems building? Maybe it’s a pifpaf issue..

Bing cache

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’ …

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

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 >, std::allocator, std::allocator > > > const&, std::vector, std::allocator >, std::allocator, std::allocator > > > const&) ()
#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

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 -> 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->descsz < 8 || (note->descsz % align_size) != 0)

  {

bad_size:

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

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

Apparently it’s supposed to be >= 8 and divisible by 4:

unsigned int align_size = bed->s->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

All versions of mldonkey crash in arch32 updated. (segmentation fault and core dumped)

experienced when building buildbot-www

/bin/sh: line 1: 4744 Segmentation fault (core dumped) yarn install –pure-lockfile

Attached to Project: Archlinux32
Opened by Andreas Baumann - 14.04.2018
Last edited by Andreas Baumann - 16.04.2018
FS#36 - texlive-core: SSE2 required

(4/5) Updating TeXLive format files… PANIC: unprotected error in call to Lua API (CPU with SSE2 required)
fmtutil [ERROR]: running `luajittex -ini -jobname=luajittex -progname=luajittex luatex.ini /null’ return status 1
fmtutil [ERROR]: return error due to options –strict
error: command failed to execute correctly
(5/5) Updating TeXLive font maps…

So, the problem seems to be in lua itself?

Bing Cache

RC4 support not found
The following options are missing in the kernel:

CONFIG_CRYPTO_USER_API_SKCIPHER
CONFIG_CRYPTO_ECB
CONFIG_CRYPTO_ARC4

gzip comes with asm code, if enabled, built a TEXTREL which gets bloqued on boot, so systemd don’t set keymap
A lot of tricks in forums, old thread more complete here $506 An old problem. Work around while asm gets fixed is call configure with DEFS=”NO_ASM” like this:

...
export DEFS="NO_ASM"
./configure ....

or,

./configure DEFS="NO_ASM" ....

I have not tested it, but gentoo on x32 have gzip like this and no TEXTRELS here.
No matter i486, i686 or pentium.

Hope it helps.

Best regards.

[linux and linux-zen] 5.16.12 needs a rebuild with gcc 11.2 so DKMS packages will work

get errors when dkms installing in make log

cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so

python-setuptools-scm 7.1.0-4.1 as found in the repo is missing the dependencies python-packaging and python-setuptools, which breaks the build of many other packages.

The linux kernel seems to be stuck at version 6.1.12.arch1-1.0. The build log of the latest stable kernel (linux-6.6.4.arch1-1.0) shows the following error:

=⇒ ERROR: Integrity checks (sha256) differ in size from the source array.
erich@rechenknecht

on fresh install file /usr/lib/libbfd.so lacks header “/* GNU ld script */” so I see complains on terminal

yes, confirmed, that’s because python 3.11 is the only package building and being
published to stable, the python modules need bootstrapping (since months).

When running qtile I get the following error message:

[qtile] importlib.metadata.PackageNotFoundError: No package metadata was found for qtile

Running qtile on Arch Linux works as expected.

$ qtile start
Traceback (most recent call last):
  File "/usr/bin/qtile", line 33, in <module>
    sys.exit(load_entry_point('qtile==0.18.1', 'console_scripts', 'qtile')())
  File "/usr/bin/qtile", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 957, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 548, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for qtile

$ pacman -Qi qtile
Name            : qtile
Version         : 0.18.1-3.0
Description     : A full-featured, pure-Python tiling window manager
Architecture    : pentium4
URL             : http://www.qtile.org
Licenses        : MIT
Groups          : None
Provides        : None
Depends On      : gdk-pixbuf2  glibc  libnotify  librsvg  pango  python-cairocffi  python-cffi  python-xcffib  python-gobject  python-setuptools
Optional Deps   : alsa-utils: for volume widget
                  canto-daemon: for canto widget
                  cmus: for cmus widget
                  jupyter_console: for interaction with qtile via Jupyter
                  khal: for khal_calendar widget
                  libpulse: for pulse_volume and pulseaudio_ffi widget [installed]
                  lm_sensors: for sensors widget [installed]
                  moc: for moc widget
                  python-dbus-next: for utils, notifications and several widgets
                  python-iwlib: for wlan widget
                  python-keyring: for imapwidget widget
                  python-mpd2: mpd2widget widget
                  python-psutil: graph, net and memory widget [installed]
                  python-pywlroots: for experimental wayland support
                  python-setproctitle: change process name to qtile
                  python-xdg: launchbar widget
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 3.25 MiB
Packager        : Andreas Baumann <mail@andreasbaumann.cc>
Build Date      : Mon 04 Oct 2021 12:02:58
Install Date    : Mon 26 Sep 2022 13:33:45
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : Signature

$ sudo pacman -Syu
:: Synchronizing package databases...
 core downloading...
 extra downloading...
 community downloading...
:: Starting full system upgrade...
 there is nothing to do

Starting terminus gives following error:

from ._cairo import *  # noqa: F401,F403
ImportError: /usr/lib/python3.10/site-packages/cairo/_cairo.cpython-310-i386-linux-gnu.so: undefined symbol: cairo_tee_surface_index

Bug seens to be related to

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

There is generall mess on cairo related files for different architectures (pentium4, i486, i686) - some packages for one architecture are outdated, while for other archictectures are up to date, for instance:

• python-cairo i486/extra : 1.21.0-1.0
• python-cairo i686/extra : 1.23.0-3.0
• python-cairo pentium4/extra : 1.23.0-3.0

The current version of sddm (0.19.0-9.0) depends on the previous version of Qt (5.15.8). After updating Qt, sddm crashes with an incompatible Qt library error.

Very easy to reproduce. lldb version 10.0.0, just try to run any binary.

[aeden@arch32 bin]$ lldb $(which date)
(lldb) target create “/usr/bin/date” Current executable set to ‘/usr/bin/date’ (i386).
(lldb) run
error: failed to launch or debug process
(lldb)

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

From a fresh install just now:

The /usr/lib/python3.10/site-packages folder is full of dozens of files, but there is little in the 3.11 folder. Some examples: gajim yt-dlp zippy samba.

This seems to affect most new packages that I install, so it is by no means limited to just the examples.