Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Olof Johansson <olof.johansson@axis.com>
Cc: Peter Kjellerstedt <pkj@axis.com>, bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake: Disable pseudo in runfetchcmd()
Date: Thu, 20 Mar 2014 15:14:19 +0000	[thread overview]
Message-ID: <1395328459.3808.180.camel@ted> (raw)
In-Reply-To: <20140320150345.GB951@axis.com>

On Thu, 2014-03-20 at 16:03 +0100, Olof Johansson wrote:
>I work with Peter, and I'm seeing this issue as well. Sorry for
> the delay in response.
> 
> > I'm more than a little concerned about why pseudo is active during
> > do_patch. It shouldn't be. Are you doing anything different with pseudo
> > in your build?
> 
> No, not as far as I know. This is the output I'm seeing
> currently, where I temporarily replaced "git" with a small shell
> script that runs whoami and exits with failure (normally, it
> would just hang at this point) (somewhat trimmed for brevity):
> 
> 
> ....
> DEBUG: Starting bitbake-worker
> DEBUG: Using cache in '/oe/master/build/cache/bb_codeparser.dat'
> ERROR: Failure expanding variable do_patch: ExpansionError: Failure expanding variable do_patch, expression was         cd /oe/master/build/tmp/work/p3367-poky-linux/linux-porky/3.10+axis12-r4.1.1/linux
>         export KMETA=${KMETA}
> 
>         # if kernel tools are available in-tree, they are preferred
>         # and are placed on the path before any external tools. Unless
>         # the external tools flag is set, in that case we do nothing.
>         if [ -f "/oe/master/build/tmp/work/p3367-poky-linux/linux-porky/3.10+axis12-r4.1.1/linux/scripts/util/configme" ]; then
>                 if [ -z "${EXTERNAL_KERNEL_TOOLS}" ]; then
>                         PATH=/oe/master/build/tmp/work/p3367-poky-linux/linux-porky/3.10+axis12-r4.1.1/linux/scripts/util:/oe/master/scripts:/oe/master/build/tmp/sysroots/x86_64-linux/usr/bin/mipsel-nf-poky-linux:/oe/master/build/tmp/sysroots/p3367/usr/bin/crossscripts:/oe/master/build/tmp/sysroots/x86_64-linux/usr/sbin:/oe/master/build/tmp/sysroots/x86_64-linux/usr/bin:/oe/master/build/tmp/sysroots/x86_64-linux/sbin:/oe/master/build/tmp/sysroots/x86_64-linux/bin:/oe/master/scripts:/oe/master/bitbake/bin:/home/olofjn/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/var/cfengine/bin:/usr/local/mipsisa32r2el/r23/bin
>                 fi
>         fi
> 
>         machine_branch="${@ get_machine_branch(d, "master" )}"
> 
>         # ...
>         # trimmed down output
>         # ...
>  which triggered exception FetchError: Fetcher failure: Fetch command failed with exit code 1, output:
> + whoami
> + : whoami = root
> + id
> + : id = uid=0(root) gid=0(root) groups=0(root)
> + exit 1
> 
> ERROR: Task 100 (/oe/master/meta-porky/recipes-kernel/linux/linux-porky_3.10.bb, do_package_write_rpm) failed with exit code '1'
> 
> 
> Note that bitbake complains about do_patch, but the executed task
> is actually do_package_write_rpm. I'm not sure what this means.
> 
> Any ideas?

The log helps immensely since it shows its "Failure expanding variable
do_patch" so its not running do_patch, it is trying to expand the
variable for some reason when writing the rpm in do_package_write_rpm. 

Are you generating some kind of srpm differently from the normal
usecases?

Cheers,

Richard



  reply	other threads:[~2014-03-20 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 14:55 [PATCH 0/1] Avoid problem with Git fetcher hanging Peter Kjellerstedt
2014-02-20 14:55 ` [PATCH 1/1] bitbake: Disable pseudo in runfetchcmd() Peter Kjellerstedt
2014-02-20 15:42   ` Mark Hatle
2014-02-22 11:24   ` Richard Purdie
2014-03-20 15:03     ` Olof Johansson
2014-03-20 15:14       ` Richard Purdie [this message]
2014-03-21  8:27         ` Olof Johansson
2014-03-22 10:12           ` Richard Purdie
2014-03-24 12:45             ` Olof Johansson
  -- strict thread matches above, loose matches on Subject: below --
2014-02-21 10:10 Peter Kjellerstedt

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=1395328459.3808.180.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=olof.johansson@axis.com \
    --cc=pkj@axis.com \
    /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