Github messages for voidlinux
 help / color / mirror / Atom feed
From: ametisf <ametisf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: New package: matterhorn-50200.7.0
Date: Mon, 16 Mar 2020 20:10:01 +0100	[thread overview]
Message-ID: <20200316191001.QNsg_AYBzDNvJW6CUhfPUN__fRQD8Pgj5jsP-BsBpO4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20136@inbox.vuxu.org>

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

New comment by ametisf on void-packages repository

https://github.com/void-linux/void-packages/pull/20136#issuecomment-599706556

Comment:
I don't see the whole error in your last comment so I can't tell exactly but Stack doesn't have to have the package you're trying to build it has to have all it's dependencies and it's not the case for matterhorn anyway so that won't work.

The error you get with cabal is caused by building it as a dynamically linked binary, all the haskell libraries are linked dynamicaly, and then you don't include them in the package, xbps goes to search for them and tells you it couldn't find any package providing those libraries. The solution is (since those libraries wouldn't be useful for anything else) to link the binary statically.

This made it build properly
```
diff --git a/srcpkgs/matterhorn/template b/srcpkgs/matterhorn/template
index 83dbcd0aac..95681b649c 100644
--- a/srcpkgs/matterhorn/template
+++ b/srcpkgs/matterhorn/template
@@ -16,7 +16,7 @@ nopie_files="/usr/bin/matterhorn"
 do_build() {
        rm -f cabal.project
        cabal new-update
-       cabal new-build -j --enable-shared --enable-executable-dynamic --ghc-options=-dynamic
+       cabal new-build --jobs="${XBPS_MAKEJOBS}" --disable-executable-dynamic
 }

 do_install() {
```
but there are more things that should be fixed about your template, definitely installing with `vbin "$(find ...)"` is a bad idea, either change it to the exact location of the output binary or better use the `cabal new-install` subcommand if it's possible to give it a `$DESTDIR`.

  parent reply	other threads:[~2020-03-16 19:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20136@inbox.vuxu.org>
2020-03-16 15:23 ` Eluminae
2020-03-16 16:55 ` Eluminae
2020-03-16 18:56 ` ametisf
2020-03-16 19:10 ` ametisf [this message]
2020-03-16 19:10 ` ametisf
2020-03-16 19:10 ` ametisf
2020-03-16 19:53 ` Eluminae
2020-03-16 20:16 ` ametisf
2020-04-01 11:53 ` [PR PATCH] [Updated] " Eluminae
2020-04-01 12:54 ` Eluminae
2020-04-16  7:30 ` Eluminae
2022-04-16  2:02 ` github-actions
2022-04-30  2:13 ` [PR PATCH] [Closed]: " github-actions

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=20200316191001.QNsg_AYBzDNvJW6CUhfPUN__fRQD8Pgj5jsP-BsBpO4@z \
    --to=ametisf@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).