From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: dino-0.1.0
Date: Sat, 01 Feb 2020 03:58:04 +0100 [thread overview]
Message-ID: <20200201025804.Wb3sBUvF3AdU20hLOS57kmQB4TQnV75AGS-l0R4d3DI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18648@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
New comment by anjandev on void-packages repository
https://github.com/void-linux/void-packages/pull/18648#issuecomment-580983812
Comment:
> @anjandev doing `./configure --with-libsignal-in-tree` worked for me, but i suppose it doesn't make sense in a package
Im sorry, that didnt work for me. Would you mind posting the full template? Also, what are the implications of `--with-libsignal-in-tree`?
@faulesocke
I tried running this template and it didnt work.
The main issue with my template is the make file breaks at
```
[ 11%] Built target xmpp-vala-vapi
make[2]: Leaving directory '/builddir/dino-0.1.0/build'
make[1]: *** [CMakeFiles/Makefile2:511: main/CMakeFiles/dino.dir/rule] Error 2
make[1]: Leaving directory '/builddir/dino-0.1.0/build'
make: *** [Makefile:255: dino] Error 2
=> ERROR: dino-0.1.0_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/cmake.sh:73
```
If I run `./xbps-src pkg dino` again after it fails at 11%, my template will compile dino completely but fail at 100%.
```
[100%] Linking C shared library ../omemo.so
/usr/bin/ld: /usr/lib/gcc/x86_64-unknown-linux-gnu/9.2.0/../../../../lib/libsignal-protocol-c.a(curve.c.o): relocation R_X86_64_PC32 against symbol `ec_public_key_destroy' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [plugins/omemo/CMakeFiles/omemo.dir/build.make:626: plugins/omemo.so] Error 1
make[2]: Leaving directory '/builddir/dino-0.1.0/build'
make[1]: *** [CMakeFiles/Makefile2:731: plugins/omemo/CMakeFiles/omemo.dir/all] Error 2
make[1]: Leaving directory '/builddir/dino-0.1.0/build'
make: *** [Makefile:130: all] Error 2
=> ERROR: dino-0.1.0_1: do_install: '${make_cmd} DESTDIR=${DESTDIR} ${make_install_args} ${make_install_target}' exited with 2
=> ERROR: in do_install() at common/build-style/cmake.sh:101
```
There is a `dino` binary in `masterdir/builddir/dino-0.1.0/build/` that runs but I have no idea why xbps-src fails to get to the install phase.
next prev parent reply other threads:[~2020-02-01 2:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 2:34 [PR PATCH] " voidlinux-github
2020-01-30 3:11 ` [PR PATCH] [Updated] [WIP] " voidlinux-github
2020-01-30 3:18 ` voidlinux-github
2020-01-30 3:49 ` voidlinux-github
2020-01-30 5:39 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-30 5:46 ` voidlinux-github
2020-01-30 5:50 ` voidlinux-github
2020-01-30 6:59 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-30 7:01 ` voidlinux-github
2020-01-30 7:03 ` voidlinux-github
2020-01-30 21:31 ` voidlinux-github
2020-01-31 4:13 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-31 15:32 ` voidlinux-github
2020-02-01 2:58 ` voidlinux-github [this message]
2020-02-01 22:38 ` voidlinux-github
2020-02-01 22:40 ` voidlinux-github
2020-02-01 22:53 ` voidlinux-github
2020-02-03 10:05 ` voidlinux-github
2020-02-03 16:49 ` voidlinux-github
2020-02-04 0:44 ` voidlinux-github
2020-02-04 2:20 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-04 2:29 ` voidlinux-github
2020-02-04 2:55 ` voidlinux-github
2020-02-04 3:03 ` voidlinux-github
2020-02-04 10:19 ` voidlinux-github
2020-02-04 10:20 ` voidlinux-github
2020-02-04 10:22 ` voidlinux-github
2020-02-04 10:24 ` voidlinux-github
2020-02-04 10:25 ` voidlinux-github
2020-02-04 20:42 ` voidlinux-github
2020-02-05 21:09 ` voidlinux-github
2020-02-06 5:44 ` [PR PATCH] [Closed]: " voidlinux-github
2020-02-06 5:44 ` voidlinux-github
2020-02-06 5:44 ` voidlinux-github
2020-02-06 9:06 ` voidlinux-github
2020-02-06 9:08 ` voidlinux-github
2020-02-06 9:37 ` voidlinux-github
2020-02-06 9:49 ` voidlinux-github
2020-02-06 19:33 ` voidlinux-github
2020-02-07 22:21 ` voidlinux-github
2020-02-07 22:32 ` voidlinux-github
2020-02-07 22:33 ` [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=20200201025804.Wb3sBUvF3AdU20hLOS57kmQB4TQnV75AGS-l0R4d3DI@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).