emerging nano fails with utf-8 error

mystified · l33t Joined: 14 Feb 2004 Posts: 748

I did an update world and the nano ebuild failed on me with the following:

IvanYosifov · l33t Joined: 15 Oct 2004 Posts: 778 Location: Bulgaria

Did you change useflags lately ?
If so, run emerge --deep --newuse world and try again.

Seems the package wants utf support in ncurses/libc, which ( I think ) has to enabled with a use flag + rebuild.

mystified · l33t Joined: 14 Feb 2004 Posts: 748

No I didn't change my USE flags but I tried the command anyway and it didn't work. Thanks for the help.

IvanYosifov · l33t Joined: 15 Oct 2004 Posts: 778 Location: Bulgaria

Ok, try adding 'unicode' to USE, run the commands again, and try again.

kimptoc · n00b Joined: 28 May 2004 Posts: 36

Hi,

The --newuse option did not help me at first - I had to manually re-emerge ncurses.

Thanks,
Chris

IvanYosifov · l33t Joined: 15 Oct 2004 Posts: 778 Location: Bulgaria

Did you use --deep ? If not portage will only consider packages in your world file - the ones you explicitly installed,not their deps.

If you do emerge X, only X will go in the world file, not it's deps.

mystified · l33t Joined: 14 Feb 2004 Posts: 748

reemerging ncurses worked. Thanks for the help!

leifbk · Posted: Mon Jun 06, 2005 8:40 am Post subject:

gentoo_dude · Posted: Tue Jun 07, 2005 12:33 pm Post subject:

re-emerging ncurses solved the problem for me too.
Thanks a lot for this post.

pumbaa · Posted: Mon Jun 13, 2005 2:19 pm Post subject:

Same here ... re-emerging ncurses solved the problem...

Merlin8000 · n00b Joined: 26 Jan 2005 Posts: 29 Location: Louisiana

I'm having the same issue, although for me

dl7und · n00b Joined: 08 Nov 2003 Posts: 13

I am not that lucky. I have had "unicode" in my USE flags all the time and ncurses and slang are both labeled as built with that flag. Nano 1.3.7 however claims during the initial tests that both are lacking utf-8 support.

I re-emerged both packages, even glibc, since it too was mentioned by the error message (though glibc does not have any unicode flag). But I'm still stuck, nano still refuses to emerge, claiming ncurses and slang both do not have utf-8 support...

Cintra · Advocate Joined: 03 Apr 2004 Posts: 2111 Location: Norway

I seem to remember having to do 'revdep-rebuild -p' in connection with the unicode update..
Mvh
_________________
"I am not bound to please thee with my answers" W.S.

dl7und · n00b Joined: 08 Nov 2003 Posts: 13

I found it, finally.

This is one of the problems where the error message not necessarily tells you where to look for the cause. As I said, nano complained about slang and ncurses not having utf-8 support, although both clearly had. I had been using unicode right from the beginning, so there couldn't be a problem with packages not having utf-8 support.

However, I noticed that nano didn't have the "ncurses" flag set. And that was the solution: I added ncurses right into make.conf and at once nano compiled without further complaints.