Github messages for voidlinux
 help / color / mirror / Atom feed
From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: greenclip-3.4
Date: Wed, 13 Jan 2021 00:13:26 +0100	[thread overview]
Message-ID: <20210112231326.cAemM1PeulSQCNRJplH-qABxqs9tV5XuWNEH7bkJjHI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27832@inbox.vuxu.org>

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

New comment by kawaiiamber on void-packages repository

https://github.com/void-linux/void-packages/pull/27832#issuecomment-758217844

Comment:
On some archs, it fails with:
```
--  While building package X11-1.9.2 (scroll up to its section to see the error) using:
      /tmp/stack-4206a322125a5924/X11-1.9.2/.stack-work/dist/x86_64-linux/Cabal-3.0.1.0/setup/setup --builddir=.stack-work/dist/x86_64-linux/Cabal-3.0.1.0 configure --user --package-db=clear --package-db=global --package-db=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/pkgdb --libdir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/lib --bindir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/bin --datadir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/share --libexecdir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/libexec --sysconfdir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/etc --docdir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/doc/X11-1.9.2 --htmldir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/doc/X11-1.9.2 --haddockdir=/builddir/greenclip-3.4/.stack/snapshots/x86_64-linux/3840f607810bca29e8c4f3fb38a11fff24b1a0f241b8b4aa1607d8ca5a10ac7a/8.8.4/doc/X11-1.9.2 --dependency=base=base-4.13.0.0 --dependency=data-default=data-default-0.7.1.1-5cjrhz8y8DG881Qqkxq9GB --exact-configuration --ghc-option=-fhide-source-paths
    Process exited with code: ExitFailure 77
```
I wonder if I need to do something like:
```
case "${XBPS_TARGET_MACHINE}" in
    aarch64*)
    <compile options>
    ;;
    armv6l* | armv7l*)
    <compile options>
    ;;
esac
```
in `do_install` as, for those archs, the build flags / options have issues with the `X11` headers? I'm not too familiar with the archs that it's failing on. I wonder if it's also worth just saying `archs="x86_64* i686"`.

  parent reply	other threads:[~2021-01-12 23:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 20:42 [PR PATCH] " kawaiiamber
2021-01-11 20:56 ` kawaiiamber
2021-01-11 21:00 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-11 21:02 ` kawaiiamber
2021-01-12  2:43 ` kawaiiamber
2021-01-12 23:01 ` kawaiiamber
2021-01-12 23:12 ` kawaiiamber
2021-01-12 23:13 ` kawaiiamber [this message]
2021-01-12 23:53 ` kawaiiamber
2021-01-13  0:07 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-13  0:08 ` kawaiiamber
2021-01-13  1:02 ` kawaiiamber
2021-01-18 21:12 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-02 21:51 ` FollieHiyuki
2021-05-03  7:33 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-03  7:35 ` New package: greenclip-4.0 kawaiiamber
2021-06-07 13:07 ` FollieHiyuki
2021-06-12  9:33 ` [PR PATCH] [Updated] " kawaiiamber
2021-06-12  9:34 ` New package: greenclip-4.2 kawaiiamber
2021-06-12 10:03 ` [PR PATCH] [Updated] " kawaiiamber
2021-06-13  2:10 ` kawaiiamber
2022-05-02  2:16 ` github-actions
2022-05-17  2:13 ` [PR PATCH] [Closed]: " github-actions
2022-05-17  9:07 ` kawaiiamber

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=20210112231326.cAemM1PeulSQCNRJplH-qABxqs9tV5XuWNEH7bkJjHI@z \
    --to=kawaiiamber@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).