All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Can't build glib-2.0
Date: Mon, 05 Dec 2011 10:23:28 -0700	[thread overview]
Message-ID: <4EDCFE10.4000208@mlbassoc.com> (raw)
In-Reply-To: <CAEsOVNfgTpENJvuQCjGd+BEytb7W4+MmPgJtrX4YqL9Q1-RXZw@mail.gmail.com>

On 2011-12-05 10:18, McClintock Matthew-B29882 wrote:
> On Mon, Dec 5, 2011 at 11:11 AM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> NOTE: package glib-2.0-1_2.30.1-r0: task do_install: Started
>> ERROR: Function 'do_install' failed (see
>> /home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/temp/log.do_install.8610
>> for further information)
>> ERROR: Logfile of failure stored in:
>> /home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/temp/log.do_install.8610
>> Log data follows:
>> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
>> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
>> | ERROR: Function 'do_install' failed (see
>> /home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/temp/log.do_install.8610
>> for further information)
>> |
>> /home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/temp/run.do_install.8610:
>> line 96: oe_runmake: command not found
>> NOTE: package glib-2.0-1_2.30.1-r0: task do_install: Failed
>
> What's on line 96?

The normal 'autotools_do_install' boilerplate:

autotools_do_install() {
         oe_runmake 'DESTDIR=/home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/image' install
         # Info dir listing isn't interesting at this point so remove it if it exists.
         if [ -e "/home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/image/usr/share/info/dir" ]; then
                 rm -f /home/local/p60_poky/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/glib-2.0-1_2.30.1-r0/image/usr/share/info/dir
         fi

}

What's missing is the functions which should be coming from base.bbclass.
I looked at an older build of glib-2.0 and these functions are missing:
==============================================================
oe_runmake() {
         if [ x"$MAKE" = x ]; then MAKE=make; fi
         bbnote make -j 4  "$@"
         make -j 4  "$@" || die "oe_runmake failed"

}

die() {
         bbfatal "$*"

}

bbnote() {
         echo "NOTE: $*"

}

bbfatal() {
         echo "ERROR: $*"
         exit 1

}
==============================================================

Why would they be missing from this run.do_install script?


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-12-05 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 17:11 Can't build glib-2.0 Gary Thomas
2011-12-05 17:18 ` McClintock Matthew-B29882
2011-12-05 17:23   ` Gary Thomas [this message]
2011-12-05 17:25     ` McClintock Matthew-B29882
2011-12-05 19:47 ` Tom Rini
2011-12-07 15:53   ` Gary Thomas

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=4EDCFE10.4000208@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=B29882@freescale.com \
    --cc=poky@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.