From: tastytea <gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ncurses; I think I wrecked my fresh install
Date: Mon, 28 Dec 2020 23:52:21 +0100 [thread overview]
Message-ID: <20201228235221.54a4e7d5@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <X+pP87ML1gEdhUnB@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
On 2020-12-28 16:36-0500 "Walter Dnes" <waltdnes@waltdnes.org> wrote:
> The previous couple of attempts, the install on my XPS 8940 died on
> rebuilding ncurses when I copied over my full USE string from my
> current desktop and updated world. This time around, I did it in
> pieces. I added some variables, and emerged update,
> rinse-lather-repeat.. This time the problem happened when I added...
>
> "-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower
> -xinerama"
>
> to the USE string. The ncurses build died, followed immediately by
> bash.
>
> […]
>
> livecd /mnt/gentoo # chroot /mnt/gentoo /bin/bash
> /bin/bash: error while loading shared libraries: libtinfow.so.6:
> cannot open shared object file: No such file or directory
Both the tinfo and the unicode use-flags are necessary if you need
libtinfow.so. From the ebuild:
if multilib_is_native_abi ; then
gen_usr_ldscript -a \
"${NCURSES_TARGETS[@]}" \
$(use tinfo && usex unicode 'tinfow' '') \
$(usev tinfo)
fi
Bash depends on readline. If readline was built with USE="unicode" it
depends on ncurses[unicode]. Try `chroot /mnt/gentoo /bin/busybox sh`.
Busybox doesn't depend on readline so that should work. However,
portage uses bash for ebuilds if I'm not mistaken. If you have a
computer with a compatible CPU and unicode disabled you could quickpkg
bash there and try to install it on the new computer. Or maybe copying
/bin/bash over is enough.
unicode is one of the useflags that are a real pain to disable after
install. :-(
Kind regards, tastytea
--
Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at
<https://tastytea.de/tastytea.asc>.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-12-28 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 21:36 [gentoo-user] ncurses; I think I wrecked my fresh install Walter Dnes
2020-12-28 21:48 ` Arve Barsnes
2020-12-28 21:55 ` Dale
2020-12-28 22:52 ` tastytea [this message]
2020-12-29 2:54 ` Walter Dnes
2021-01-19 2:21 ` Walter Dnes
2021-01-19 13:15 ` Andreas K. Hüttel
2020-12-29 15:11 ` Andreas K. Huettel
2020-12-29 21:17 ` [gentoo-user] " Grant Edwards
2020-12-29 23:01 ` [gentoo-user] " Walter Dnes
2020-12-30 1:04 ` [gentoo-user] " Grant Edwards
2020-12-30 9:23 ` Wols Lists
2020-12-30 16:35 ` [gentoo-user] " Andreas K. Huettel
2020-12-30 17:42 ` antlists
2020-12-30 17:30 ` Andreas K. Huettel
2020-12-30 18:01 ` antlists
2020-12-30 18:14 ` Andreas K. Huettel
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=20201228235221.54a4e7d5@ventiloplattform.tastytea.de \
--to=gentoo@tastytea.de \
--cc=gentoo-user@lists.gentoo.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