On 21/08/2015 04:41, wraeth wrote:
On 21/08/15 11:49, Alan Grimes wrote:
tortoise ~ # emerge --info ... Repositories:
You have a fair number of overlays. It probably doesn't need to be
said, but you should watch out for packages being pulled in from an
overlay instead of the default Gentoo
On Thursday, August 20, 2015 6:31:48 PM Alan Grimes wrote:
Fernando Rodriguez wrote:
The ncurses ebuild is indeed broken, I ran into the same problem before.
But you received good advice on your last thread (build libtinfo on
another
system and copy it or just try symlinking it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/08/15 08:31, Alan Grimes wrote:
Fernando Rodriguez wrote:
The ncurses ebuild is indeed broken, I ran into the same problem
before.
But you received good advice on your last thread (build libtinfo
on another system and copy it or just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/08/15 11:49, Alan Grimes wrote:
tortoise ~ # emerge --info ... Repositories:
You have a fair number of overlays. It probably doesn't need to be
said, but you should watch out for packages being pulled in from an
overlay instead of the
tortoise ~ # emerge --info
Portage 2.2.20.1 (python 3.4.3-final-0,
default/linux/amd64/13.0/desktop, gcc-4.9.3, glibc-2.21-r1, 4.1.6 x86_64)
=
System uname:
Linux-4.1.6-x86_64-AMD_Phenom-tm-_II_X6_1090T_Processor-with-gentoo-2.2
KiB
Seeing segfaults in a compile like that makes me question your hardware
rather than the gentoo tools. Are you sure your hardware is in a
functional state? I update my world fairly often and am running ~amd64 and
have not experienced the issue you are experiencing. :(
On Thu, Aug 20, 2015 at
On 20 August 2015 at 22:37, Alan McKinnon alan.mckin...@gmail.com wrote:
Ranting on the list might make you feel better, but is not likely to fix
your problem. Just saying.
Don't worry, in his previous thread, named with the insightful subject
, the OP just didn't care to reply after
On Thursday, August 20, 2015 4:26:08 PM Alan Grimes wrote:
My five year old CPU has been working it's ass off the last few days
doing a full --emptytree world to try to purge the system of the ncurses
clusterfuck.
Here is the list of FAIL. A few of these might be stale listings because
I
My five year old CPU has been working it's ass off the last few days
doing a full --emptytree world to try to purge the system of the ncurses
clusterfuck.
Here is the list of FAIL. A few of these might be stale listings because
I didn't purge the directory before running this. Also a few of these
Let me describe what I see.
This can't be a clusterfuck, as it is affecting only you. No-one else to
my knowledge is reporting problems caused by ncurses.
So, it is then highly likely that you have a setup that the devs did not
consider, and it is rare (if not unique).
So, what exactly did you
Fernando Rodriguez wrote:
The ncurses ebuild is indeed broken, I ran into the same problem before.
But you received good advice on your last thread (build libtinfo on another
system and copy it or just try symlinking it to ncurses), if you'd followed
it
you would a got your system back up
11 matches
Mail list logo
