From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: dev branch, bitbake of "mplayer" fails
Date: Wed, 13 Jan 2010 06:59:20 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001130657110.487@localhost> (raw)
i'm starting to think these build errors only ever happen to me.
:-( once again, on fedora 12, dev branch:
ERROR: function do_compile failed
ERROR: see log in
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/mplayer-0.0+1.0rc2+svnr30247-r15/temp/log.do_compile.26510
NOTE: Task failed:
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/mplayer-0.0+1.0rc2+svnr30247-r15/temp/log.do_compile.26510
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/home/rpjday/oe/openembedded/recipes/mplayer/mplayer_svn.bb do_compile
failed
log file:
NOTE: make
ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -Wundef -Wdisabled-optimization
-Wno-pointer-sign -Wdeclaration-after-statement -std=gnu99
-isystem/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include
-fexpensive-optimizations -ftree-vectorize -fomit-frame-pointer -O4
-ffast-math
-I/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/mplayer-0.0+1.0rc2+svnr30247-r15/trunk/libdvdread4
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I.
-isystem/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include
-D_REENTRANT
-I/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include/freetype2
-I/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include
-I/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include/schroedinger-1.0
-I/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include/liboil-0.3
-isystem/home/rpjday/oe/angstrom-dev/staging/armv7a-angstrom-linux-gnueabi/usr/include
-c -o libmpcodecs/vf_fspp.o libmpcodecs/vf_fspp.c
In file included from libmpcodecs/vf_fspp.c:50:
./libavutil/internal.h:266:6: warning: "HAVE_EXP2" is not defined
./libavutil/internal.h:273:6: warning: "HAVE_EXP2F" is not defined
./libavutil/internal.h:294:6: warning: "HAVE_LOG2F" is not defined
In file included from libmpcodecs/vf_fspp.c:51:
./libavutil/internal.h:267: error: static declaration of 'exp2'
follows non-static declaration
./libavutil/internal.h:274: error: static declaration of 'exp2f'
follows non-static declaration
./libavutil/internal.h:295: error: static declaration of 'log2f'
follows non-static declaration
make: *** [libmpcodecs/vf_fspp.o] Error 1
FATAL: oe_runmake failed
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2010-01-13 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 11:59 Robert P. J. Day [this message]
2010-01-13 13:20 ` dev branch, bitbake of "mplayer" fails Koen Kooi
2010-01-13 14:03 ` Koen Kooi
2010-01-13 14:16 ` Robert P. J. Day
2010-01-13 14:29 ` Koen Kooi
2010-01-13 14:35 ` Robert P. J. Day
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=alpine.LFD.2.00.1001130657110.487@localhost \
--to=rpjday@crashcourse.ca \
--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 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.