Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: ddgtk-0.1
Date: Sun, 16 Jun 2019 13:22:53 +0200	[thread overview]
Message-ID: <20190616112253.yLjlNWLU5IApJhAnk3PZBEivS3vHxrlTfdeILxR6RzQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12480@inbox.vuxu.org>

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

New comment by reback00 on void-packages repository

https://github.com/void-linux/void-packages/pull/12480#issuecomment-502443315
Comment:
Having some errors with ARM builds. Anybody has any idea to how I can solve it?

```
...
=> ddgtk-0.1_1: running pre-configure hook: 02-script-wrapper ...
=> ddgtk-0.1_1: running do_configure ...
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/mesonbuild/mesonmain.py", line 122, in run
    return options.run_func(options)
...
  File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'glib-compile-resources': 'glib-compile-resources'
The Meson build system
Version: 0.50.1
...
Found pkg-config: /usr/bin/pkg-config (0.29.2)
WARNING: Could not detect glib version, assuming 2.54. You may get build errors if your glib is older.
=> ERROR: ddgtk-0.1_1: do_configure: '${meson_cmd} --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/libexec --bindir=/usr/bin --sbindir=/usr/bin --includedir=/usr/include --datadir=/usr/share --mandir=/usr/share/man --infodir=/usr/share/info --localedir=/usr/share/locale --sysconfdir=/etc --localstatedir=/var --sharedstatedir=/var/lib --buildtype=plain --auto-features=enabled --wrap-mode=nodownload -Db_lto=true -Db_ndebug=true -Db_staticpic=true ${configure_args} . ${meson_builddir}' exited with 2
=> ERROR:   in do_configure() at common/build-style/meson.sh:108
The command "if [ -z "$XLINT" ]; then docker exec -t void hostrepo/common/travis/build.sh $BOOTSTRAP $ARCH; fi" exited with 1.
...
```
from [https://travis-ci.org/void-linux/void-packages/jobs/546344997](https://travis-ci.org/void-linux/void-packages/jobs/546344997)

  parent reply	other threads:[~2019-06-16 11:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 20:31 [PR PATCH] " voidlinux-github
2019-06-16 10:19 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-16 10:19 ` voidlinux-github
2019-06-16 10:27 ` voidlinux-github
2019-06-16 10:27 ` voidlinux-github
2019-06-16 11:22 ` voidlinux-github [this message]
2019-06-16 11:42 ` voidlinux-github
2019-06-16 16:59 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-16 16:59 ` voidlinux-github
2019-06-16 17:24 ` voidlinux-github
2019-06-16 17:30 ` voidlinux-github
2019-06-16 18:48 ` voidlinux-github
2019-06-16 19:15 ` voidlinux-github
2019-06-17  3:07 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-17  3:07 ` voidlinux-github
2019-06-17 15:23 ` [PR PATCH] [Merged]: " voidlinux-github

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=20190616112253.yLjlNWLU5IApJhAnk3PZBEivS3vHxrlTfdeILxR6RzQ@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).