emerging nano fails with utf-8 error

Message

mystified · Post by **mystified** » Fri Jun 03, 2005 4:50 pm

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

configure: error:
*** UTF-8 support was requested, but insufficient UTF-8 support was
*** detected in your curses and/or C libraries.  Please verify that your
*** slang was built with UTF-8 support or your curses was built with
*** wide character support, and that your C library was built with wide
*** character support.

any ideas?

TIA

IvanYosifov · Post by **IvanYosifov** » Fri Jun 03, 2005 8:00 pm

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 · Post by **mystified** » Fri Jun 03, 2005 8:24 pm

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

IvanYosifov · Post by **IvanYosifov** » Sat Jun 04, 2005 10:15 am

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

kimptoc · Post by **kimptoc** » Sat Jun 04, 2005 2:04 pm

Hi,

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

Thanks,
Chris

IvanYosifov · Post by **IvanYosifov** » Sat Jun 04, 2005 2:38 pm

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 · Post by **mystified** » Sat Jun 04, 2005 3:39 pm

reemerging ncurses worked. Thanks for the help!

leifbk · Post by **leifbk** » Mon Jun 06, 2005 8:40 am

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

Having recently added the unicode use flag to /etc/make.conf, I ran into exactly the same problem. I can confirm that an "emerge -avuD world" does not list ncurses as a dependency for nano. You have to rebuild ncurses manually.

BTW, as the error message from configure suggested, I first rebuilt slang with unicode support.

gentoo_dude · Post by **gentoo_dude** » Tue Jun 07, 2005 12:33 pm

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

pumbaa · Post by **pumbaa** » Mon Jun 13, 2005 2:19 pm

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

Merlin8000 · Post by **Merlin8000** » Tue Jun 14, 2005 12:01 pm

I'm having the same issue, although for me

Code: Select all

emerge -puD --newuse world

listed ncurses first on the list of packages to be emerged

dl7und · Post by **dl7und** » Tue Dec 20, 2005 1:17 am

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 · Post by **Cintra** » Tue Dec 20, 2005 5:52 am

I seem to remember having to do 'revdep-rebuild -p' in connection with the unicode update..
Mvh

dl7und · Post by **dl7und** » Tue Dec 20, 2005 7:16 am

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.