Github messages for voidlinux
 help / color / mirror / Atom feed
From: BikyAlex <BikyAlex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [LOW PRIORITY] Libreoffice 7.2.3.2 template compilation issue
Date: Wed, 02 Feb 2022 07:10:17 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35352@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

New issue by BikyAlex on void-packages repository

https://github.com/void-linux/void-packages/issues/35352

Description:
### System
Void Linux glibc aarch64 - Raspberry Pi 4

* xuname:  
  Void 5.10.52_1 aarch64 Unknown uptodate rF
* package:  
  *affected package(s) including the version*: ``LibreOffice 7.2.3.2 template from void-packages/srcpkgs ``

### Expected behavior
  compile successfully

### Actual behavior
  fail to compile

### Steps to reproduce the behavior
```
  cd void-packages
  git pull --rebase upstream master
  ./xbps-src binary-bootstrap
  ./xbps-src pkg libreoffice  
```

### Output:
```
[build RDB] services
[build PKG] svx_gengal
[build CXX] svx/source/gengal/gengal.cxx
[build LNK] Executable/gengal.bin
[build GAL] backgrounds
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
make[1]: *** [/builddir/libreoffice-7.2.3.2/solenv/gbuild/Gallery.mk:56: /builddir/libreoffice-7.2.3.2/workdir/Gallery/backgrounds.done] Error 1
make: *** [Makefile:287: build] Error 2
=> ERROR: libreoffice-7.2.3.2_2: do_build: 'make ${makejobs} ${make_build_target}' exited with 2
=> ERROR:   in do_build() at srcpkgs/libreoffice/template:523
```


---

My question would be, where is "${makejobs}" defined in the template, because it only appears twice and in neither cases is it declared, unless xbps-src has this as an env variable somewhere. "${make_build_target}" is defined though. 

I did clean the hostdir/builddir folder once after the first failure, but that didn't seem to help. 

As a background, if that interests anyone, I'm using the Raspberry Pi 4 as my main PC (been my main for more than 8 months now), but libreoffice is not present in the aarch64 repo. I am assuming that's because libreoffice doesn't work with cross-compilation, so I have to compile it myself natively. I don't mind that, but I can't decode the xbps-src template myself and fix it. Does it work to compile on x86? I don't have an x86 system to test the template there. And I also cannot decode how buildbot works, so I can check the status of LO.

             reply	other threads:[~2022-02-02  6:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  6:10 BikyAlex [this message]
2022-02-02  9:48 ` ericonr
2022-02-02 12:58 ` BikyAlex
2022-02-04  3:23 ` BikyAlex
2022-02-05  6:54 ` BikyAlex
2022-06-23  2:15 ` github-actions
2022-06-23  4:08 ` ericonr
2022-06-23 11:25 ` BikyAlex
2022-06-24 22:27 ` BikyAlex
2022-06-25  0:35 ` ericonr
2022-09-23  2:14 ` github-actions
2022-12-23  1:56 ` aarch64: " github-actions
2022-12-23  2:01 ` classabbyamp
2022-12-23  2:15 ` BikyAlex
2022-12-23  2:33 ` BikyAlex
2022-12-23 11:23 ` classabbyamp
2022-12-23 11:58 ` BikyAlex
2022-12-23 12:22 ` BikyAlex
2023-02-10  5:03 ` aarch64: Libreoffice " BikyAlex
2023-02-10  5:03 ` [ISSUE] [CLOSED] " BikyAlex

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35352@inbox.vuxu.org \
    --to=bikyalex@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).