Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: angstrom-2010.x : gnome-power-manager-2.30.0-r0: libtool: Command not found
Date: Sun, 26 Dec 2010 09:54:32 +0100	[thread overview]
Message-ID: <4D1702C8.6050300@eukrea.com> (raw)

Hi,

MACHINE=beagleboard
DISTRO=angstrom-2010.x

error log :
NOTE: make
make  all-recursive
make[1]: Entering directory 
`/home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/work/armv7a-angs
trom-linux-gnueabi/gnome-power-manager-2.30.0-r0/gnome-power-manager-2.30.0'
Making all in src
make[2]: Entering directory 
`/home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/work/armv7a-angs
trom-linux-gnueabi/gnome-power-manager-2.30.0-r0/gnome-power-manager-2.30.0/src'
libtool --mode=execute dbus-binding-tool	\
		--prefix=gpm_manager			\
		--mode=glib-server			\
		--output=org.gnome.PowerManager.h	\
		./org.gnome.PowerManager.xml
make[2]: libtool: Command not found
make[2]: *** [org.gnome.PowerManager.h] Error 127
make[2]: Leaving directory 
`/home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/work/armv7a-angst
rom-linux-gnueabi/gnome-power-manager-2.30.0-r0/gnome-power-manager-2.30.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/work/armv7a-angst
rom-linux-gnueabi/gnome-power-manager-2.30.0-r0/gnome-power-manager-2.30.0'
make: *** [all] Error 2
FATAL: oe_runmake failed
ebenard@eukrea-desktop:~/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/gnome-power-manager-2.30.0-r0/temp$ 
more log.do_compile.*


Eric



                 reply	other threads:[~2010-12-26  8:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D1702C8.6050300@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox