Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [do not merge ] Samba4
Date: Fri, 12 Jul 2019 14:38:49 +0200	[thread overview]
Message-ID: <20190712123849.8K-vTNRDSBLtQ7s91BKa9-xgWZXd6G-XAkDWk6L9ASU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-9087@inbox.vuxu.org>

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

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/pull/9087#issuecomment-510785395
Comment:
Thanks for the new commits, I'm building it right now and will test it on my raspberry pi 3 B+.

Edit: 

Cross Compiling errors out currently on my machine:
https://gist.github.com/Anachron/7f9d136ec0ab5c40ae35f40257089e3e#file-samba-log-L75

Found the issue, one needs to copy the answers file to aarch64: `cp armv7l.answers aarch64.answers`.

It's missing some deps `ldb` and `tevent` for ARM. 

Even when one builds those himself (building `ldb` is enough as `tevent is a dep) it still has some `shlib` issue: 
```
 [rpi@rpi3] ~ 8! » sudo xbps-install --repository=samba4 samba4
samba4-4.9.4_1: broken, unresolvable shlib `libnetapi.so.0'
Transaction aborted due to unresolved shlibs.
```

```
 [rpi@rpi3] ~ » sudo xbps-install --repository=samba4 libsamba4 2>&1 | head -n 5libsamba4-4.9.4_1: broken, unresolvable shlib `libCHARSET3-samba4.so'
libsamba4-4.9.4_1: broken, unresolvable shlib `libHDB-SAMBA4-samba4.so'
libsamba4-4.9.4_1: broken, unresolvable shlib `libMESSAGING-SEND-samba4.so'
libsamba4-4.9.4_1: broken, unresolvable shlib `libMESSAGING-samba4.so'
libsamba4-4.9.4_1: broken, unresolvable shlib `libaddns-samba4.so'
...
```

  parent reply	other threads:[~2019-07-12 12:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-9087@inbox.vuxu.org>
2019-05-08 16:34 ` voidlinux-github
2019-07-06 18:06 ` voidlinux-github
2019-07-06 18:06 ` voidlinux-github
2019-07-08  5:04 ` voidlinux-github
2019-07-11  9:16 ` voidlinux-github
2019-07-11 13:47 ` voidlinux-github
2019-07-11 13:55 ` voidlinux-github
2019-07-11 14:07 ` voidlinux-github
2019-07-11 14:09 ` voidlinux-github
2019-07-11 14:10 ` voidlinux-github
2019-07-12  6:07 ` voidlinux-github
2019-07-12  7:44 ` voidlinux-github
2019-07-12 10:02 ` voidlinux-github
2019-07-12 10:35 ` voidlinux-github
2019-07-12 11:40 ` voidlinux-github
2019-07-12 12:38 ` voidlinux-github [this message]
2019-07-12 12:39 ` voidlinux-github
2019-07-12 12:39 ` voidlinux-github
2019-07-12 12:51 ` voidlinux-github
2019-07-12 12:59 ` voidlinux-github
2019-07-12 15:44 ` voidlinux-github
2019-07-12 15:45 ` voidlinux-github
2019-07-12 15:45 ` voidlinux-github
2019-09-21 17:32 ` voidlinux-github
2020-02-17 18:19 ` damadmai
2020-11-01 20:11 ` [PR PATCH] [Closed]: " Gottox
2020-11-01 20:11 ` Gottox

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=20190712123849.8K-vTNRDSBLtQ7s91BKa9-xgWZXd6G-XAkDWk6L9ASU@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).