Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] No rule to make target 'host-python !!
Date: Sun, 24 Jan 2021 17:39:40 +0100	[thread overview]
Message-ID: <20210124173940.29212b62@gmx.net> (raw)
In-Reply-To: <CAGshWo31-JML-C6D+T+Bbp8QrsWKZhE2r4-N8HaOAp6z4rkhtQ@mail.gmail.com>

Hello Emmanuel,

On Sun, 24 Jan 2021 17:08:21 +0100, manu f <e.fiancette@gmail.com> wrote:

> Thanks peter.
> What's mean Buildroot 2020.02.8-dirty?

This indicates normally a buildroot git repository at version
2020.02.8 (tag/branch) with local changes ('dirty')...

> 
> About python37, yes I add this custom package but like you see I didn't
> select it.

But the line '+# BR2_PACKAGE_PYTHON is not set' indicates that
there is no python package any longer with your build setup
(and so no host-python available needed by libevdev)...

Hard to judge without knowledge of your br-external but I would suspect
it contains a package/python directory with a python.mk file without
an '$(eval $(host-autotools-package))' line (or something like
that) and a Config.in file with BR2_PACKAGE_PYTHON_37 instead of
BR2_PACKAGE_PYTHON?

If so try to move .../br-exteranl/package/python to .../br-exteranl/package/python-37

Regards,
Peter

> this config is without livdevdev and it compile right. but if I select it I
> had th error I gave (do you think it could be a problem if I not set
> libdevdev, I realy not sure I need it, sorry I didn't completly setupp this
> buildroot jus modify some aspect and I am far to master all).
> 
> But its is strange that I have BR2_PACKAGE_PYTHON not set.
> I will look later (I am not on my linux computer), I think I even havent
> pithon item in menu-config...
> Is this mean I have a problem with python dependencies ? I will check the
> dependencies logic.
> 
> Peter, Its very strange that at your side you could compile with libdevdev
> set and not me. Do you have an idea wher I could search?
> 
> Many thanks for helping.
> 
> Regards.
> 
> Emmanuel
> 
> 
> 
> Le dim. 24 janv. 2021 ? 16:14, Peter Seiderer <ps.report@gmx.net> a ?crit :
> 
> > Hello,
> >
> > On Sun, 24 Jan 2021 12:40:31 +0100, manu f <e.fiancette@gmail.com> wrote:
> >  
> > > here my complete .config  
> >
> > Importing your .config into a plain buildroot-2020.02.8 gives
> > the following diff:
> >
> > @@ -1,9 +1,8 @@
> >  #
> >  # Automatically generated file; DO NOT EDIT.
> > -# Buildroot 2020.02.8-dirty Configuration
> > +# Buildroot 2020.02.8 Configuration
> >  #
> >  BR2_HAVE_DOT_CONFIG=y
> > -BR2_EXTERNAL_ATOS_PATH="/home/user/cleta_buildroot/br-external"
> >  BR2_HOST_GCC_AT_LEAST_4_9=y
> >  BR2_HOST_GCC_AT_LEAST_5=y
> >  BR2_HOST_GCC_AT_LEAST_6=y
> > @@ -1446,6 +1445,7 @@
> >  #
> >  # BR2_PACKAGE_PERL is not set
> >  # BR2_PACKAGE_PHP is not set
> > +# BR2_PACKAGE_PYTHON is not set
> >  BR2_PACKAGE_PYTHON3=y
> >  # BR2_PACKAGE_PYTHON3_PY_ONLY is not set
> >  BR2_PACKAGE_PYTHON3_PYC_ONLY=y
> > @@ -4174,6 +4174,7 @@
> >  # BR2_PACKAGE_HOST_PKGCONF is not set
> >  # BR2_PACKAGE_HOST_PRU_SOFTWARE_SUPPORT is not set
> >  # BR2_PACKAGE_HOST_PWGEN is not set
> > +# BR2_PACKAGE_HOST_PYTHON is not set
> >  # BR2_PACKAGE_HOST_PYTHON_CYTHON is not set
> >  # BR2_PACKAGE_HOST_PYTHON_LXML is not set
> >  # BR2_PACKAGE_HOST_PYTHON_SIX is not set
> > @@ -4876,17 +4877,3 @@
> >  # BR2_VFP_FLOAT is not set
> >  # BR2_PACKAGE_GCC_TARGET is not set
> >  # BR2_HAVE_DEVFILES is not set
> > -
> > -#
> > -# External options
> > -#
> > -
> > -#
> > -# br2-external tree for atos projects (in
> > /home/user/cleta_buildroot/br-external)
> > -#
> > -BR2_PACKAGE_BACKLIGHT_MONITORING=y
> > -BR2_PACKAGE_TEST_UART=y
> > -BR2_PACKAGE_APP_MOUNT=y
> > -BR2_PACKAGE_APP_UPDATER=y
> > -BR2_NODE_JS_14x=y
> > -# BR2_PYTHON_37 is not set
> >
> >
> > Note the lines with 'Buildroot 2020.02.8-dirty',
> > '-BR2_EXTERNAL_ATOS_PATH="/home/user/cleta_buildroot/br-external"',
> > '+# BR2_PACKAGE_PYTHON is not set' and '-# BR2_PYTHON_37 is not set',
> > so most likely something with your local change and/or br-external
> > changing the package python to python37?
> >
> > Otherwise the config compiles fine here (even with libevdev enabled)...
> >
> > Regards,
> > Peter
> >
> >  
> > >
> > > Le sam. 23 janv. 2021 ? 11:48, Thomas Petazzoni <  
> > > thomas.petazzoni at bootlin.com> a ?crit :  
> > >  
> > > > On Fri, 22 Jan 2021 23:53:30 +0100
> > > > manu f <e.fiancette@gmail.com> wrote:
> > > >  
> > > > > ok, I remove libevdev in Target package =>libraries=>Other and its  
> > copile  
> > > > > without error!
> > > > >
> > > > > (But I dont know if I realy need this lib... )
> > > > >
> > > > > Well why it no compile with libdevdev ?
> > > > > @ Thomas Petazzoni I saw you already got problem and make patch for
> > > > > host-python interpreter...is there something to see with ?  
> > > >
> > > > host-python is definitely part of Buildroot 2020.02, so I'm not sure
> > > > how you can get this error. We would need more details, such as the
> > > > complete .config that reproduces the issue.
> > > >
> > > > Thomas
> > > > --
> > > > Thomas Petazzoni, CTO, Bootlin
> > > > Embedded Linux and Kernel engineering
> > > > https://bootlin.com
> > > >  
> >
> >  

  reply	other threads:[~2021-01-24 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 22:21 [Buildroot] No rule to make target 'host-python !! manu f
2021-01-22 22:32 ` manu f
2021-01-22 22:53 ` manu f
2021-01-23 10:48   ` Thomas Petazzoni
2021-01-24 11:40     ` manu f
2021-01-24 15:14       ` Peter Seiderer
2021-01-24 16:08         ` manu f
2021-01-24 16:39           ` Peter Seiderer [this message]
2021-01-24 21:27             ` manu f
2021-01-24 21:53               ` Peter Seiderer
2021-01-25  9:55                 ` manu f
2021-01-25 12:40                   ` manu f
2021-01-25 14:05                     ` Thomas Petazzoni
2021-01-29 12:09                       ` [Buildroot] No rule to make target 'host-python !! [SOLVED] manu f

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=20210124173940.29212b62@gmx.net \
    --to=ps.report@gmx.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