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 7184] New: supervisord depends on libxml2 implicitly
Date: Tue, 10 Jun 2014 11:19:32 +0000 (UTC)	[thread overview]
Message-ID: <bug-7184-163@https.bugs.busybox.net/> (raw)

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

           Summary: supervisord depends on libxml2 implicitly
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: sebastian at himberger.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When using supervisord without libxml2 it complains because it can not use the
python xml module. apparently python needs libxml2 present to build the xml
module but happily builds without it and also works (as long as you dont use
the module). I would suggest either adding libxml2 to python or the supervisord
package as a dependency since supervisord fails to start without xml support.

-- 
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-10 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 11:19 bugzilla at busybox.net [this message]
2014-06-10 11:26 ` [Buildroot] [Bug 7184] supervisord depends on libxml2 implicitly bugzilla at busybox.net
2014-06-10 12:09 ` bugzilla at busybox.net
2014-06-10 12:18 ` bugzilla at busybox.net
2014-06-10 12:20 ` bugzilla at busybox.net
2014-06-10 12:21 ` bugzilla at busybox.net
2014-06-11  7:28 ` bugzilla at busybox.net
2014-06-11 19:18 ` bugzilla at busybox.net
2014-06-15 14:12 ` 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-7184-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