All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Barnett <ryan.barnett@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] Package python-pyxml missing?
Date: Thu, 29 Jan 2015 18:42:08 -0600	[thread overview]
Message-ID: <CAMQcK5K3Ye22haHyNcpOtdv1z4EqmKptC_84re527fhSW+xjnQ@mail.gmail.com> (raw)
In-Reply-To: <54CAC560.5060407@ecoventsystems.com>

Shawn,

On Thu, Jan 29, 2015 at 5:42 PM, Shawn Rose <sr@ecoventsystems.com> wrote:
> Hi,
>
> Is the python-pyxml package suppose to be included in the latest builds?
>  I just did a git clone git://git.busybox.net/buildroot and the package
> buildroot/package/python-pyxml is missing.  I also do not see it on
> http://git.buildroot.net/buildroot/ on the master branch.

That package has been submitted for inclusion into buildroot with the
following patch:

http://patchwork.ozlabs.org/patch/427112/

> Why I ask is my python-setuptools crashes on for me when I use any of
> its functionality with the error ImportError: No module named
> xml.dom.pulldom   I believe this is due to my python xml package being
> missing.

Please apply this patch to your clone of buildroot following these
instructions (section 21.3.1):

http://nightly.buildroot.org/manual.html#_reviewing_and_testing_patches

If this patch works for you, please add a "Tested by:" to the patch
following instructions in the section linked above.

Thanks,
-Ryan

-- 
Ryan Barnett / Sr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ryan.barnett at rockwellcollins.com
www.rockwellcollins.com

      reply	other threads:[~2015-01-30  0:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 23:42 [Buildroot] Package python-pyxml missing? Shawn Rose
2015-01-30  0:42 ` Ryan Barnett [this message]

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=CAMQcK5K3Ye22haHyNcpOtdv1z4EqmKptC_84re527fhSW+xjnQ@mail.gmail.com \
    --to=ryan.barnett@rockwellcollins.com \
    --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.