1 |
* Fernando Rodriguez <frodriguez.developer@×××××××.com> [150831 20:35]: |
2 |
[..SNIP..] |
3 |
> Hmm, I keyworded ncurses and this is what portage wants to do: |
4 |
> |
5 |
> [ebuild r U ~] sys-libs/ncurses-6.0-r1:0/6::gentoo [5.9-r5:0/5::fernan] |
6 |
> USE="cxx doc gpm tinfo unicode -ada -debug -minimal -profile -static-libs {- |
7 |
> test%} -threads% -trace" ABI_X86="32 (64) -x32" 3,059 KiB |
8 |
> [ebuild U ~] sys-libs/ncurses-5.9-r101:5::gentoo [5.9-r99:5::gentoo] |
9 |
> USE="gpm tinfo unicode (-ada%) (-cxx%*) (-static-libs%)" ABI_X86="32 (64) - |
10 |
> x32" 0 KiB |
11 |
> [ebuild rR ~] sys-devel/gdb-7.10::gentoo USE="client expat python server |
12 |
> zlib -lzma -multitarget -nls {-test} -vanilla" PYTHON_SINGLE_TARGET="python2_7 |
13 |
> -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB |
14 |
> [ebuild rR ] app-misc/screen-4.3.1::gentoo USE="pam -debug -multiuser - |
15 |
> nethack -selinux" 0 KiB |
16 |
> [ebuild rR ] app-emulation/wine-1.6.2::gentoo USE="X alsa cups custom- |
17 |
> cflags fontconfig gecko jpeg lcms ldap mp3 ncurses openal opengl perl png |
18 |
> prelink pulseaudio run-exes samba ssl threads truetype udisks v4l xcomposite |
19 |
> xinerama xml -capi -dos -gphoto2 -gsm -gstreamer -mono -nls -odbc -opencl - |
20 |
> osmesa -oss -realtime -scanner -selinux {-test}" ABI_X86="32 64 -x32" |
21 |
> LINGUAS="-ar -bg -ca -cs -da -de -el -en -en_US -eo -es -fa -fi -fr -he -hi -hr |
22 |
> -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk - |
23 |
> sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW" 0 KiB |
24 |
> |
25 |
> |
26 |
> That looks dangerous to me because the first build will upgrade my 5.9 |
27 |
> installation to 6.0 and the second will reinstall 5.9. |
28 |
> |
29 |
> So what happens in between when I have no 5.9 installed but everything is |
30 |
> linked against it? Won't it need bash to build the second one? What if the 2nd |
31 |
> build fails? Will stuff linked against 5.9 work with 6.0? |
32 |
|
33 |
I'm running ~x86 and ~amd64 and update daily so hopefully some of what I'll |
34 |
relate below won't apply to anyone else who doesn't do that. |
35 |
|
36 |
But first when I got ncurses-6.0 I then couldn't build ghc because the |
37 |
binary build tools were linked against ncurses-5.x (this has been fixed |
38 |
now.) At the time I could get around it by installing ncurses-5.0 as |
39 |
the ncurses:5 slot. Since then however ncurses:5 seems to give |
40 |
ncurses-6.0 and ncurses:0 is ncurses-6.1 (though I could be mistaken.) |
41 |
|
42 |
Anyway, ncurses-6.0 and ncurses-5.9 were coinstalled and happy together |
43 |
as you'd expect from a slotted package. |
44 |
|
45 |
However, yesterday there were problems with more ncurses changes and |
46 |
readline. Somehow the build of sys-libs/readline went awry and it |
47 |
produced a .so without some symbols needed by gawk and bc (or more |
48 |
likely, they needed to be rebuilt but couldn't be.) This prevented |
49 |
ncurses from being rebuilt since the build requires awk and prevented my |
50 |
kernel from being rebuilt because it requires bc. But readline couldn't |
51 |
be rebuilt because it required ncurses. I could be off on the actual |
52 |
interdependencies but bottom line is that I couldn't get out of the |
53 |
circular dependencies (and there were no use flags to turn then off.) |
54 |
Even trying to build with --nodeps didn't get me out of the hole. |
55 |
|
56 |
In the end I had to pull a gawk off a stage3 and |
57 |
/{lib,lib64}/libreadline.so.6.3 off other systems to get out of it. |
58 |
|
59 |
Hopefully that was all just because of running ~x86 and ~amd64 (I don't |
60 |
want to call it unstable because it's worked great for me for years and |
61 |
is very stable due to excellent work from Gentoo devs!) and my just |
62 |
catching things in flux. |
63 |
|
64 |
Presented here in case someone experiences readline/ncurses problems in |
65 |
the future unrelated to this original ncurses issue. |
66 |
|
67 |
Todd |