Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] python-cffi: add host variant
Date: Fri, 25 Dec 2015 22:44:36 +0100	[thread overview]
Message-ID: <20151225214436.GB3878@free.fr> (raw)
In-Reply-To: <CAGm1_kvTT4GX63oEHPoD7e2P5SQaoMqU8pAjR0Cqaf0erFnHtA@mail.gmail.com>

Yegor, All,

On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:
> On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
> >> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
> >> > Target variant doesn't need pycparser. cffi's setup.py seems to
> >> > distinguish, if we install real package or cross-compiled one:
> >> >
> >> >         install_requires=[
> >> >             'pycparser',
> >> >         ] if cpython else [],
> >>
> >> I don't understand how this "if cpython" is relevant to make the
> >> different between the native (host) variant or the cross-compiled
> >> (target) variant. cpython is defined as is:
> >>
> >>     cpython = ('_cffi_backend' not in sys.builtin_module_names)
> >>
> >> Can you give some more details?
> >
> > Yegor and I briefly discussed this on IRC yesterday, but I'm not really
> > convinced by this reply either. I forgot to reply yesterday...
> >
> > What I understand, however, is that they want to differentiate between
> > cpython (the 'ofiicial' native Python interpreter), and PyPy (the Python
> > interpreter written in Python).
> >
> > Of course, I don't see how this all works. It seems in
> > cross-compilation. there differentiation criterai beliveves it is
> > running under PyPy amd thus they do not need pycparser.
> >
> > But thtat's just incorrect, because we may have a host-python with
> > cffi_backend at one point, and thus the check above will eventually
> > differentiate toward cpython, and we'd nreak again.
> >
> > So, two things:
> >   - their check is wrong,
> >   - we probably need host-pycparser
> >
> > At least, that's what I understood...
> 
> We have host-pycparser: http://patchwork.ozlabs.org/patch/560970/

Well, I meant that we should need host-pycparser as a dependency of
python-cffi.

But anyway, there is more to this: we really need to understand what is
going on...

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-12-25 21:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 21:30 [Buildroot] [PATCH 1/5] python-ipaddress: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 2/5] python-pycparser: " Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 3/5] python-cffi: add host variant Yegor Yefremov
2015-12-24 21:46   ` Yann E. MORIN
2015-12-24 22:12     ` Yegor Yefremov
2015-12-25 19:00       ` Thomas Petazzoni
2015-12-25 19:12         ` Yann E. MORIN
2015-12-25 19:58           ` Yegor Yefremov
2015-12-25 21:44             ` Yann E. MORIN [this message]
2015-12-26 22:54               ` Yegor Yefremov
2015-12-31  7:20                 ` Oli Vogt
2015-12-31  8:55                   ` Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 4/5] python-cryptography: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 5/5] python-pyopenssl: " Yegor Yefremov

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=20151225214436.GB3878@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox