From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Samba aborts on Raspberry Pi 3B
Date: Thu, 31 Dec 2020 18:44:09 +0100 [thread overview]
Message-ID: <20201231174409.PAF9BFzT_u_faxEv5zM9cIRQkzBpH4kZyVPeK2KFr3A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27565@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/27565#issuecomment-753014350
Comment:
@hortimech By "rework", I mean add more private libraries to the list of "built-in" libraries. The tendency for Samba to create a metric fuckton of "*-samba4.so" unversioned libraries is a total nightmare for XBPS, which tries to track shared library dependencies. The more of these libraries can be "built in" to the versioned libraries intended for public consumption, the better. However, some private libraries refuse to compile as built-ins, and I wonder if a few of the additions to the built-in list made between `4.13.2_1` and `4.13.2_3` somehow compile but cause issues.
I have no problems on `x86_64` and would like confirmation from @Anachron that these changes don't break on `aarch64`.
See https://github.com/void-linux/void-packages/blob/master/srcpkgs/samba/template#L42-L58
next prev parent reply other threads:[~2020-12-31 17:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 0:01 [ISSUE] " wangp
2020-12-31 3:56 ` ahesford
2020-12-31 5:39 ` ericonr
2020-12-31 14:10 ` Anachron
2020-12-31 14:11 ` Anachron
2020-12-31 15:56 ` ahesford
2020-12-31 17:18 ` hortimech
2020-12-31 17:44 ` ahesford [this message]
2021-01-01 7:54 ` wangp
2021-01-01 7:57 ` wangp
2021-01-01 13:53 ` Anachron
2021-01-01 13:58 ` ahesford
2021-01-01 14:03 ` hortimech
2021-01-01 14:15 ` Anachron
2021-01-01 14:27 ` ahesford
2021-01-01 18:30 ` Anachron
2021-01-01 18:40 ` hortimech
2021-01-02 0:28 ` wangp
2021-01-02 0:41 ` ericonr
2021-01-02 0:42 ` ericonr
2021-01-02 11:12 ` andry-dev
2021-01-02 13:12 ` wangp
2021-01-02 19:06 ` ahesford
2021-01-05 3:42 ` [ISSUE] [CLOSED] " ahesford
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=20201231174409.PAF9BFzT_u_faxEv5zM9cIRQkzBpH4kZyVPeK2KFr3A@z \
--to=ahesford@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).