Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5204] New: Missing terminfo file(s) for GNU screen terminal type
Date: Mon,  7 May 2012 08:54:41 +0000 (UTC)	[thread overview]
Message-ID: <bug-5204-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=5204

           Summary: Missing terminfo file(s) for GNU screen terminal type
           Product: buildroot
           Version: 2012.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: zkdigisec at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When GNU screen is selected for inclusion in Buildroot, none of its terminal
files (screen*) are installed.

The problem is due to the Buildroot screen makefile only using the
"install-bin" target of screen, which is a subset of the full installation
target called "install".

A fix could be to change screen.mk in Buildroot to use "install". Another fix
could be to export the screen terminfo file(s) from the staging area in the
build of ncurses.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-05-07  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  8:54 bugzilla at busybox.net [this message]
2012-05-07 21:19 ` [Buildroot] [Bug 5204] Missing terminfo file(s) for GNU screen terminal type bugzilla at busybox.net

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=bug-5204-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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