Opened 7 years ago

Closed 4 years ago

#7078 closed defect (wontfix)

libncurses, terminfo and alternate install destination

Reported by: eschoeller@… Owned by: developers
Priority: normal Milestone: Features Paradise
Component: packages Version: Trunk
Keywords: Cc:


The terminfo directory is read by many ncurses enabled applications (iftop, nano) in /user/share/terminfo. When installing libncurses to a destination other than root, this terminfo directory isn't read by these ncurses applications and the following errors occur:

# iftop


Error opening terminal: vt102.

The fix:

# ln -s /opt/usr/share/terminfo/ /usr/share/

(where /opt/ is my alternate opkg destination where I installed libncurses)

I'm not sure if this is within the scope of the package maintainers, or even openwrt in general to maintain proper functionality of this package when installing to a separate destination.

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by anonymous

You should use block-extroot then you don't have to deal with such...

comment:2 Changed 7 years ago by nico

  • Milestone changed from Backfire 10.03.1 to Kamikaze Features Paradise

comment:3 Changed 6 years ago by eschoeller@…

Well, I ran into this problem again and found my own ticket =) The solution proposed would certainly work, but I'd rather not rely on a removable flash device for my rootfs. Even though I'm running on devices that have a 16MB flash, libncurses is an absolute pig and isn't required for core functionality of the device, hence the reason to install the package on volatile off-ram storage.

I'll continue using the symlink method to pull this off, but I figure a better long-term solution should eventually be found.

comment:4 Changed 4 years ago by nbd

  • Resolution set to wontfix
  • Status changed from new to closed

installing to alternate locations is not (and will not be) supported

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.