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 7136] New: ecryptfs-utils needs gettext to run when glibc/eglibc is used
Date: Sun,  1 Jun 2014 17:13:42 +0000 (UTC)	[thread overview]
Message-ID: <bug-7136-163@https.bugs.busybox.net/> (raw)

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

           Summary: ecryptfs-utils needs gettext to run when glibc/eglibc
                    is used
           Product: buildroot
           Version: 2014.05
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: xxiao8 at fosiao.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


gettext package is disabled by default when glibc/eglibc is chosen, this should
be enabled at least for package such as ecryptfs, there might be other packages
that need gettext as well. gettext should not depend on BR2_NEEDS_GETTEXT which
is uClibc only.

-- 
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:[~2014-06-01 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 17:13 bugzilla at busybox.net [this message]
2014-06-01 17:31 ` [Buildroot] [Bug 7136] ecryptfs-utils needs gettext to run when glibc/eglibc is used bugzilla at busybox.net
2014-06-01 17:32 ` bugzilla at busybox.net
2014-06-01 20:24 ` bugzilla at busybox.net
2014-08-15 18:40 ` bugzilla at busybox.net
2014-08-18  9:13 ` 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-7136-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.