From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/11 v4] package/python-lxml: new package
Date: Sun, 18 Jan 2015 20:26:34 +0100 [thread overview]
Message-ID: <20150118192634.GD16593@free.fr> (raw)
In-Reply-To: <CAGm1_ksWvJcap__h4Xte0osgJo7TKotYxbWthj3=mmynKyVpOw@mail.gmail.com>
Yegor, All,
On 2015-01-18 20:14 +0100, Yegor Yefremov spake thusly:
> On Sun, Jan 18, 2015 at 7:03 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Yegor, All,
> >
> > On 2015-01-18 18:27 +0100, Yegor Yefremov spake thusly:
> >> On Sun, Jan 18, 2015 at 1:11 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> > The lxml XML toolkit is a Pythonic binding for the C libraries libxml2
> >> > and libxslt.
> >> Trying to build lxml as normal package and get following error:
> >
> > You mean, as a target package?
> >
> > It can not work as-is, because I only declared the host variant.
> > You'd have to add the target variant if you want the target package.
>
> I've created needed files like Config.in etc.
OK, I guessed you did, but was trying the obvious... ;-)
[--SNIP--]
> >> compilation terminated.
> >
> > Well, I just tried, and it builds fine, even when I remove the libxml2
> > development files from my host:
[--SNIP--]
> >
> > I don't know what would break for the target package. Maybe it includes
> > unsafe paths (-I and/or -L) ?
>
> Have you also installed libxslt-dev on your PC?
No, I do not have libxslt development files installed on the host.
> After I've done this,
> I could cross-compile lxml, but it is not very "legal" approach :-)
Smells like unclean include paths to me. I'll investigate further on the
target-side package
Adding the target variant can come in a later patch, no? And that should
not impact the host variant from being comitted as-is, would it?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-01-18 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 12:11 [Buildroot] [PATCH 0/11 v4] NVidia GPU binary blobs for x86 and ARM (branch yem/gfx-2) Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 01/11 v4] package/python-lxml: new package Yann E. MORIN
2015-01-18 17:27 ` Yegor Yefremov
2015-01-18 17:51 ` Yann E. MORIN
2015-01-18 18:03 ` Yann E. MORIN
2015-01-18 19:14 ` Yegor Yefremov
2015-01-18 19:26 ` Yann E. MORIN [this message]
2015-01-18 19:57 ` Yegor Yefremov
2015-01-18 12:11 ` [Buildroot] [PATCH 02/11 v4] package/khrplatform-registry: " Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 03/11 v4] package/openkode-registry: " Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 04/11 v4] package/opengl-registry: " Yann E. MORIN
2015-01-18 22:24 ` Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 05/11 v4] package/openmax-registry: " Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 06/11 v4] package/nvidia-driver: add NVidia's OpenGL binary blob Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 07/11 v4] package/nvidia-driver: build the kernel module Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 08/11 v4] package/nvidia-tegra23-binaries: new package Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 09/11 v4] package.nvidia-tegra23-binaries: add gstreamer plugins Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 10/11 v4] package/nvidia-tegra23-binaries: provides JPEG Yann E. MORIN
2015-01-18 12:11 ` [Buildroot] [PATCH 11/11 v4] package/nvidia-tegra23-codecs: new package Yann E. MORIN
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=20150118192634.GD16593@free.fr \
--to=yann.morin.1998@free.fr \
--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.