• Status Assigned
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Packages
  • Assigned To
    Andreas Baumann
  • Operating System pentium4
  • Severity Low
  • Priority Medium
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Andreas Baumann - 21.02.2021

FS#163 - sphinx_rtd_theme is used everywhere to build documentation but doesn't build

build
running build_py
npm WARN npm npm does not support Node.js v15.9.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.
npm WARN npm You can find the latest version at https://nodejs.org/

> sphinx_rtd_theme@0.5.1 preinstall /build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1
> bin/preinstall.js

Traceback (most recent call last):
  File "/build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1/setup.py", line 86, in <module>
    setup(
  File "/usr/lib/python3.9/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/build/python-sphinx_rtd_theme/src/sphinx_rtd_theme-0.5.1/setup.py", line 22, in run
    subprocess.run(['npm', 'install'], check=True)
  File "/usr/lib/python3.9/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['npm', 'install']' died with <Signals.SIGSEGV: 11>.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/staging-pentium4/abaumann/build
Admin
Andreas Baumann commented on 21.02.2021 08:41

It needs npm, npm has it's own problems:

rm -rf node_modules .cache public/*js public/*json public/404* public/page-data public/manifest*

> sharp@0.23.4 install /build/npm/src/cli-6.14.11/docs/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

ERR! sharp Intel Architecture 32-bit systems require manual installation of libvips >= 8.8.1

Manual installation of libvips? pardon me?

../src/common.cc:25:10: fatal error: vips/vips8: No such file or directory
   25 | #include <vips/vips8>
      |          ^~~~~~~~~~~~
compilation terminated.

Curiously the package exists:

-rw-rw-rw- 1 http http     566 May 14  2020 pool/libvips-8.9.2-3.0-pentium4.pkg.tar.zst.sig
-rw-rw-rw- 1 http http 1620564 May 14  2020 pool/libvips-8.9.2-3.0-pentium4.pkg.tar.zst
-rw-rw-rw- 1 http http     310 May 14  2020 pool/libvips-8.9.2-3.0-i686.pkg.tar.zst.sig
-rw-rw-rw- 1 http http 1628692 May 14  2020 pool/libvips-8.9.2-3.0-i686.pkg.tar.zst
Admin
Andreas Baumann commented on 21.02.2021 09:10

This library is gladly optional:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
Admin
Andreas Baumann commented on 21.02.2021 09:26
# libvips: for sharp (doc build) (disabled as current version of gatsby imports a broken sharp)

Something went wrong installing the "sharp" module

libMagickCore-7.Q16HDRI.so.7: cannot open shared object file: No such file or directory

appanetly we have to use libvips again, because it needs to build it.

This is the correct shared library:

/usr/lib/libMagickCore-7.Q16HDRI.so.9.0.0

We see here https://www.archlinux32.org/packages/pentium4/community/libvips/ that there is a broken links, so let's rebuild libvips and make it links
against the current version if ImageMagick.

Admin
Andreas Baumann commented on 21.02.2021 09:55
makedepends+=(libvips)

yields the error in Gatsby:

 ERROR #11321  PLUGIN
Input file contains unsupported image format
  Error: Input file contains unsupported image format

/build/.npm/_logs/2021-02-21T09_52_14_537Z-debug.log:

1 verbose cli [
1 verbose cli   '/usr/bin/node',
1 verbose cli   '/build/npm/src/cli-6.14.11/bin/npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build:static',
1 verbose cli   'echo'
1 verbose cli ]
2 info using npm@6.14.11
3 info using node@v15.9.0
4 verbose run-script [ 'prebuild:static', 'build:static', 'postbuild:static' ]
5 info lifecycle npm-cli-docs@0.1.0~prebuild:static: npm-cli-docs@0.1.0
6 info lifecycle npm-cli-docs@0.1.0~build:static: npm-cli-docs@0.1.0
7 verbose lifecycle npm-cli-docs@0.1.0~build:static: unsafe-perm in lifecycle true
8 verbose lifecycle npm-cli-docs@0.1.0~build:static: PATH: /build/npm/src/cli-6.14.11/node_modules/npm-lifecycle/node-gyp-bin:/build/npm/src/cli-6.14.11/docs/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
9 verbose lifecycle npm-cli-docs@0.1.0~build:static: CWD: /build/npm/src/cli-6.14.11/docs
10 silly lifecycle npm-cli-docs@0.1.0~build:static: Args: [ '-c', 'GATSBY_IS_STATIC=true gatsby build --prefix-paths "echo"' ]
11 silly lifecycle npm-cli-docs@0.1.0~build:static: Returned: code: 1  signal: null
12 info lifecycle npm-cli-docs@0.1.0~build:static: Failed to exec build:static script
13 verbose stack Error: npm-cli-docs@0.1.0 build:static: `GATSBY_IS_STATIC=true gatsby build --prefix-paths "echo"`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/build/npm/src/cli-6.14.11/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (node:events:378:20)
13 verbose stack     at ChildProcess.<anonymous> (/build/npm/src/cli-6.14.11/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (node:events:378:20)
13 verbose stack     at maybeClose (node:internal/child_process:1067:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
14 verbose pkgid npm-cli-docs@0.1.0
15 verbose cwd /build/npm/src/cli-6.14.11/docs
16 verbose Linux 5.10.16-arch1-1
17 verbose argv "/usr/bin/node" "/build/npm/src/cli-6.14.11/bin/npm-cli.js" "run" "build:static" "echo"
18 verbose node v15.9.0
19 verbose npm  v6.14.11
20 error code ELIFECYCLE
21 error errno 1
22 error npm-cli-docs@0.1.0 build:static: `GATSBY_IS_STATIC=true gatsby build --prefix-paths "echo"`
22 error Exit status 1
23 error Failed at the npm-cli-docs@0.1.0 build:static script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Admin
Andreas Baumann commented on 21.02.2021 10:02

Hacking around and removing some checks in sharp later shows a C++ exepction

"Input file contains unsupported image format"

Ignoring that one in the code yields:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! npm-cli-docs@0.1.0 build:static: `GATSBY_IS_STATIC=true gatsby build --prefix-paths "echo"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the npm-cli-docs@0.1.0 build:static script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

during install.

This is a mess!

Admin
Andreas Baumann commented on 21.02.2021 10:04

It might be easier just to hack out all documentation builds using sphinx than to actually
fix this mess in npm..

Admin
Andreas Baumann commented on 21.02.2021 14:22

So, now we get a much nicer crash without the "NPM too old" warnings..

NPM is still segfaulting.

Admin
Andreas Baumann commented on 21.02.2021 17:02

nodejs compilation with ./configure –dest-cpu ia32 didn't help.

The interpreter looks ok though on first sight.

Admin
Andreas Baumann commented on 21.02.2021 19:35

Affected:

buildbot
coq
dbus-python
gnome-builder
hid-tools
libratbag
linux
linux-docs
linux-hardened
linux-lts
linux-zen
mopidy
prjtrellis
pybind11
python-commonmark
python-jedi
python-libevdev
python-lxml
python-nose2
python-pyadi-iio
python-sphinx_rtd_theme
python-virtualenv
quodlibet

Linux has priority.

Admin
Andreas Baumann commented on 21.02.2021 19:41

I'm doing a temporary workaround by disabling documentation building where possible..

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing