public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: What is the correct version of ncurses on ~amd64 now?
Date: Mon, 31 Aug 2015 16:30:17 -0700	[thread overview]
Message-ID: <20150831163017.01016999@a6> (raw)
In-Reply-To: 55E4D185.5030601@gmail.com

On Tue, 1 Sep 2015 00:13:25 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On 31/08/2015 23:13, walt wrote:

> > Right now emerge tries to install ncurses-6.0-r1 but the 32-bit
> > part of the build fails because emerge never ran make in the
> > work/cross/progs directory, and so the 32-bit tools didn't get
> > compiled.
> > 
> > I hacked around this by running make in that directory manually,
> > which allowed the ebuild install and ebuild package phases to
> > succeed.

 
> This machine was entirely unaffected by all the recent ncurses issues:
> 
> [I] sys-libs/ncurses
>      Available versions:
>      (0)    5.9-r3 (~)5.9-r4 5.9-r5(0/5) (~)6.0-r1(0/6)
>      (5)    5.9-r99(5/5) (~)5.9-r101(5/5) (~)6.0(5/6)
>        {ada +cxx debug doc gpm minimal profile static-libs test
> threads tinfo trace unicode ABI_MIPS="n32 n64 o32" ABI_PPC="32 64"
> ABI_S390="32 64" ABI_X86="32 64 x32"}
>      Installed versions:  6.0-r1(12:52:29 30/08/2015)(cxx gpm threads
> unicode -ada -debug -doc -minimal -profile -static-libs -test -tinfo
> -trace ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64"
> ABI_X86="32 64 -x32")
>      Homepage:            https://www.gnu.org/software/ncurses/
> http://dickey.his.com/ncurses/
>      Description:         console display library
> 
> So 6.0-r1 works completely relaible on at least one Gentoo machine in
> this world :-)

<huge sigh of relief>  I installed my ugly-hack binary package of
6.0-r1 and it seemed to install okay.  The first thing I tried was to
emerge 6.0-r1 the normal way and this time it succeeded :)

Apparently my known-broken install of 6.0 was preventing proper cross
building of the 32-bit files, maybe because the 32-bit part of 6.0 was
what was actually broken.

By way of reckless experiment I will now reboot this machine for the
first time since I rsynced 12 long, nail-biting hours ago...




  reply	other threads:[~2015-08-31 23:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 21:13 [gentoo-user] What is the correct version of ncurses on ~amd64 now? walt
2015-08-31 22:13 ` Alan McKinnon
2015-08-31 23:30   ` walt [this message]
2015-09-01  0:33   ` Fernando Rodriguez
2015-09-01  2:20     ` [gentoo-user] " walt
2015-09-01  2:55       ` Fernando Rodriguez
2015-09-01  3:24         ` Fernando Rodriguez
2015-09-01 12:34     ` [gentoo-user] " Todd Goodman

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=20150831163017.01016999@a6 \
    --to=w41ter@gmail.com \
    --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