All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: yocto@yoctoproject.org
Subject: Re: [zeus] icu-native-64.2-r0 do_configure: configure failed
Date: Wed, 30 Oct 2019 10:30:24 +0000	[thread overview]
Message-ID: <6166e80d-ce25-14cf-1f16-02ae9d36aa14@intel.com> (raw)
In-Reply-To: <trinity-8eddf10e-7c97-465a-a389-4a6462d8fdf7-1572416709913@3c-app-gmx-bs26>

On 30/10/2019 06:25, star@gmx.li wrote:
> Build of image failed, I got strange and long error messages like:
> 
> | from distutils.sysconfig import parse_makefile
> | ModuleNotFoundError: No module named 'distutils.sysconfig'
> | configure: error: Python failed to run; see above error.

> a) What goes wrong here and how can this be avoid?

distutils.sysconfig is part of the standard Python library.  What 
distribution are you using?  It's possible that you've only got a 
'minimal' Python installed instead of the full thing.

> b) How do I found which module is responsible. There is nothing about strace/valgrind mentioned in the log. I just had to build all my additional packets of my image manually to find the triggers for this icu-native.

The recipe responsible is icu-native.  Something in your build depends 
on this, such as boost-native maybe.

Ross


  reply	other threads:[~2019-10-30 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  6:25 [zeus] icu-native-64.2-r0 do_configure: configure failed star
2019-10-30 10:30 ` Ross Burton [this message]
2019-10-30 12:11 ` Arno Steffens
2019-10-30 17:30   ` Ross Burton
2019-10-31  9:20 Arno Steffens

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=6166e80d-ce25-14cf-1f16-02ae9d36aa14@intel.com \
    --to=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    /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.