Bug #2317
build issue on i686: cannot build libretools
Status:
fixed
Priority:
bug
Assignee:
% Done:
0%
Description
$ makepkg
==> Making package: libretools 20181004-1 (ven. 17 mai 2019 01:06:15 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found libretools-20181004.tar.gz
-> Found libretools-20181004.tar.gz.sig
==> Validating source files with sha256sums...
libretools-20181004.tar.gz ... Passed
libretools-20181004.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
libretools-20181004.tar.gz ... Passed
==> Extracting sources...
-> Extracting libretools-20181004.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
cat src/abslibre-tools/createworkdir.pot src/abslibre-tools/diff-unfree.pot src/abslibre-tools/libreaddiff.pot src/abslibre-tools/libredbdiff.pot src/abslibre-tools/librerelease.pot src/abslibre-tools/librestage.pot | msguniq -Fi --to-code=UTF-8 > 'src/abslibre-tools/dir.pot'
m4 -Isrc/chroot-tools -P src/chroot-tools/chcleanup.in | sed -e 's|^#!\s*/bin/bash|#!/usr/bin/env bash|' -e 's|m4_include(lib/\(.*\))|. "$(librelib \1)"|' | install -m755 /dev/stdin src/chroot-tools/chcleanup
cd src/chroot-tools && /home/gnutoo/work/projects/parabola/abslibre/libre/libretools/src/libretools-20181004/src/lib/librexgettext makechrootpkg.sh > makechrootpkg.sh.pot
cat src/devtools/checkpkg.pot src/devtools/find-libdeps.pot src/devtools/finddeps.pot src/devtools/lddd.pot | msguniq -Fi --to-code=UTF-8 > 'src/devtools/dir.pot'
cat src/gitget/gitget.pot src/gitget/libregit.pot | msguniq -Fi --to-code=UTF-8 > 'src/gitget/dir.pot'
ronn --roff --manual='libretools Manual' --organization='Parabola' < 'src/lib/common.sh.3.ronn' > 'src/lib/common.sh.3'
ronn --roff --manual='libretools Manual' --organization='Parabola' < 'src/lib/conf.sh.3.ronn' > 'src/lib/conf.sh.3'
Traceback (most recent call last):
2: from /usr/bin/ronn:23:in `<main>'
1: from /usr/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
/usr/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': can't find gem ronn (>= 0.a) with executable ronn (Gem::GemNotFoundException)
make[1]: *** [build-aux/Makefile.each.tail/20-libretools.mk:58: src/lib/common.sh.3] Error 1
make[1]: *** Deleting file 'src/lib/common.sh.3'
make[1]: *** Waiting for unfinished jobs....
Traceback (most recent call last):
2: from /usr/bin/ronn:23:in `<main>'
1: from /usr/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
/usr/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': can't find gem ronn (>= 0.a) with executable ronn (Gem::GemNotFoundException)
make[1]: *** [build-aux/Makefile.each.tail/20-libretools.mk:58: src/lib/conf.sh.3] Error 1
make[1]: *** Deleting file 'src/lib/conf.sh.3'
make: *** [GNUmakefile:13: default] Error 2
==> ERROR: A failure occurred in build().
Aborting...
If I try to run ronn I get:
$ ronn
Traceback (most recent call last):
2: from /usr/bin/ronn:23:in `<main>'
1: from /usr/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
/usr/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': can't find gem ronn (>= 0.a) with executable ronn (Gem::GemNotFoundException)
$ pacman -Q -o ronn /usr/bin/ronn is owned by ruby-ronn 0.7.3-7.0
History
Updated by GNUtoo almost 5 years ago
- Subject changed from build issue: cannot build libretools to build issue on i686: cannot build libretools
ronn works on x86_64
Updated by GNUtoo almost 5 years ago
Building ruby-ronn 0.7.3-8.0 from git://git.archlinux.org/svntogit/community.git and installing it makes it work.
So we need to forward that upstream to archlinux32.
Note that x86_64 has 0.7.3-8.0 while i686 has 0.7.3-7.0, and the package architecture is 'any', so it should really be easy for upstream to fix that as the package revision will increase and it already supports i686 out of the box.
Updated by GNUtoo almost 5 years ago
As I'm not very familiar with libretools I've sent the patch to the mailing list to be reviewed.
Updated by GNUtoo almost 5 years ago
- Assignee set to GNUtoo
The architecture of the package is any, so it can also be built on x86_64 in the worst case.