From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vim: add options for different build variants.
Date: Fri, 09 Jul 2021 16:45:52 +0200 [thread overview]
Message-ID: <20210709144552.JZWkw3fQa178gixaVMuVFsScPHlLRmimJ6x8h19c774@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31871@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/pull/31871#issuecomment-877241704
Comment:
I tried builds with all flags, no flags, just huge, and cross versions.
cross with huge seems to work with a few touch ups:
```
=> vim-huge-8.2.2874_2: running pre-pkg hook: 04-generate-runtime-deps ...
SONAME: libSM.so.6 <-> libSM>=1.1.0_1
SONAME: libICE.so.6 <-> libICE>=1.0.5_1
SONAME: libXt.so.6 <-> libXt>=1.0.5_1
SONAME: libX11.so.6 <-> libX11>=1.2_1
SONAME: libm.so.6 <-> glibc>=2.32_1
SONAME: libncursesw.so.6 <-> ncurses-libs>=5.8_1
SONAME: libacl.so.1 <-> acl>=2.2.47_1
SONAME: libdl.so.2 <-> glibc>=2.32_1
SONAME: liblua5.3.so.5.3 <-> lua53>=5.3.5_4
SONAME: libperl.so.5.32 <-> perl>=5.32.0_1
SONAME: libpthread.so.0 <-> glibc>=2.32_1
SONAME: libpython3.9.so.1.0 <-> python3>=3.9.2_2
SONAME: libruby.so.2.7 <-> ruby>=2.7.2_3
SONAME: libc.so.6 <-> glibc>=2.32_1
SONAME: ld-linux-aarch64.so.1 <-> glibc>=2.32_1
```
next prev parent reply other threads:[~2021-07-09 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 14:23 [PR PATCH] " leahneukirchen
2021-07-09 14:24 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 14:29 ` ericonr
2021-07-09 14:45 ` leahneukirchen [this message]
2021-07-09 15:43 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 15:43 ` [PR PATCH] [Closed]: " leahneukirchen
2021-07-09 15:45 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 15:46 ` leahneukirchen
2021-07-09 20:43 ` Piraty
2021-07-16 19:15 ` [PR PATCH] [Merged]: " leahneukirchen
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=20210709144552.JZWkw3fQa178gixaVMuVFsScPHlLRmimJ6x8h19c774@z \
--to=leahneukirchen@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).