All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 133] New: Modify ncurses5-config to get correct include path
Date: Fri, 27 Feb 2009 09:24:08 +0000 (UTC)	[thread overview]
Message-ID: <bug-133-163@https.bugs.busybox.net/> (raw)

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

              Host: PC SuSe 11.1
            Target: ARM
           Summary: Modify ncurses5-config to get correct include path
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: henry.margies at gmx.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=77)
 --> (https://bugs.busybox.net/attachment.cgi?id=77)
Patch for ncurses

Some tools (e.g. alsamixer) are using ncurses5-config --cflags --libs to get
the include and library path needed for ncurses. With ncurses6 installed on
your host system, ncurses5-config --cflags returns -I/usr/include/ncurses which
will break your build.

This patch will modify the prefix setting to point to the staging dir.

Let me know what you think.

Best regards,

Henry


-- 
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:[~2009-02-27  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  9:24 bugzilla at busybox.net [this message]
2009-03-01 22:36 ` [Buildroot] [Bug 133] Modify ncurses5-config to get correct include path 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-133-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.