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 1843] New: Fix libcap build failure
Date: Fri, 28 May 2010 17:43:03 +0000 (UTC)	[thread overview]
Message-ID: <bug-1843-163@https.bugs.busybox.net/> (raw)

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

              Host: i686-linux
            Target: arm-softfloat-linux-uclibcgnueabi
           Summary: Fix libcap build failure
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gustavo at zacarias.com.ar
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 1777
  --> https://bugs.busybox.net/attachment.cgi?id=1777
Forcibly disable PAM support in libcap

The libcap package fails to build because it tries to detect PAM presence via
shell file detection against the host includes.
Fix it by disabling PAM in Make.Rules since we don't have PAM support in
buildroot at the moment.

-- 
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:[~2010-05-28 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 17:43 bugzilla at busybox.net [this message]
2010-05-28 19:48 ` [Buildroot] [Bug 1843] Fix libcap build failure 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-1843-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