Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: dino-0.1.0
Date: Tue, 04 Feb 2020 11:20:53 +0100	[thread overview]
Message-ID: <20200204102053.niWYenX0aqB3dqbMKmqgc-s2qcCxboWj3b21CK0630w@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: 3644 bytes --]

New comment by toogley on void-packages repository

https://github.com/void-linux/void-packages/pull/18648#issuecomment-581838791

Comment:
I think i have managed to build dino directly some weeks ago (that means: not as void linux package and instead as a binary directly from the dino repository).

I think i have used this command at that time: `./configure --enable-plugin=omemo && make`
However, that fails at the moment with this error:

```
FAILED: plugins/omemo.so 
: && /bin/cc -fPIC -fdiagnostics-color -Wall -Wextra -Werror=format-security -Wno-duplicate-decl-specifier -g -O2 -g -DNDEBUG   -shared -Wl,-soname,omemo.so -o plugins/omemo.so plugins/omemo/CMakeFiles/omemo.dir/src/plugin.c.o plugins/omemo/CMakeFiles/omemo.dir/src/register_plugin.c.o plugins/omemo/CMakeFiles/omemo.dir/src/trust_level.c.o plugins/omemo/CMakeFiles/omemo.dir/src/file_transfer/file_decryptor.c.o plugins/omemo/CMakeFiles/omemo.dir/src/file_transfer/file_encryptor.c.o plugins/omemo/CMakeFiles/omemo.dir/src/jingle/jingle_helper.c.o plugins/omemo/CMakeFiles/omemo.dir/src/jingle/jet_omemo.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/database.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/encrypt_state.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/manager.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/pre_key_store.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/session_store.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/signed_pre_key_store.c.o plugins/omemo/CMakeFiles/omemo.dir/src/logic/trust_manager.c.o plugins/omemo/CMakeFiles/omemo.dir/src/protocol/bundle.c.o plugins/omemo/CMakeFiles/omemo.dir/src/protocol/message_flag.c.o plugins/omemo/CMakeFiles/omemo.dir/src/protocol/stream_module.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/account_settings_entry.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/account_settings_widget.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/contact_details_provider.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/contact_details_dialog.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/device_notification_populator.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/own_notifications.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/encryption_list_entry.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/manage_key_dialog.c.o plugins/omemo/CMakeFiles/omemo.dir/src/ui/util.c.o plugins/omemo/CMakeFiles/omemo.dir/resources/resources.c.o  -Wl,-rpath,/home/toogley/src/dino/build:  libdino.so.0.0  plugins/signal-protocol/libsignal-protocol-vala.a  plugins/crypto-vala/libcrypto-vala.a  libxmpp-vala.so.0.1  /usr/lib/libicuuc.so  /usr/lib/libicudata.so  libqlite.so.0.1  /usr/lib/libsqlite3.so  -lsignal-protocol-c  -lm  -lgcrypt  /usr/lib/libgee-0.8.so  /usr/lib/libgmodule-2.0.so  /usr/lib/libgtk-3.so  /usr/lib/libgdk-3.so  /usr/lib/libpangocairo-1.0.so  /usr/lib/libpango-1.0.so  /usr/lib/libatk-1.0.so  /usr/lib/libcairo-gobject.so  /usr/lib/libcairo.so  /usr/lib/libgdk_pixbuf-2.0.so  /usr/lib/libsoup-2.4.so  /usr/lib/libgio-2.0.so  /usr/lib/libgobject-2.0.so  /usr/lib/libglib-2.0.so  /usr/lib/libqrencode.so && :
/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
/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
make: *** [Makefile:2: default] Error 1
```

I tought it would make sense to get dino working that way before packaging it into void to understand how the build script has to look inside voidlinux. Still investigating.

  parent reply	other threads:[~2020-02-04 10:20 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
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 [this message]
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=20200204102053.niWYenX0aqB3dqbMKmqgc-s2qcCxboWj3b21CK0630w@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).