From: Mr Dash Four <mr.dash.four@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: "cannot find -lppl_c" link error
Date: Sat, 19 Nov 2011 21:07:17 +0000 [thread overview]
Message-ID: <4EC81A85.8050704@googlemail.com> (raw)
I am trying to build my kernel image with "bitbake virtual/kernel" using the following (rather short) local.conf:
DL_DIR = "${HOME}/oe/sources"
BBFILES = "${HOME}/oe/openembedded/recipes/*/*.bb"
MACHINE = "htcdream"
DISTRO = "shr"
BBMASK = "/(nonworking|obsolete|cacao)/"
As a side note - the reason I excluded "cacao" above as well is because there are some errors in the .bb recipe files. Unfortunately, my build fails with the following error:
| gcc -isystem/home/mr-4/oe/build/tmp/sysroots/x86_64-linux/usr/include -O2 -g -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -L/home/mr-4/oe/build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/home/mr-4/oe/build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/home/mr-4/oe/build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-O1 -o cc1-dummy c-lang.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o c-semantics.o c-ppoutput.o c-cppbuiltin.o c-objc-common.o c-dump.o c-pch.o c-parser.o arm-c.o c-gimplify.o tree-mudflap.o c-pretty-print.o c-omp.o \
| dummy-checksum.o main.o libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -lcloog -Wl,-Bstatic -lppl_c -lppl -lgmpxx -Wl,-Bdynamic -Wl,-Bstatic -lmpc -lmpfr -lgmp -Wl,-Bdynamic -rdynamic -ldl -L../zlib -lz -Wl,-Bstatic -lelf -Wl,-Bdynamic
| /usr/bin/ld: cannot find -lppl_c
| collect2: ld returned 1 exit status
| make[2]: *** [cc1-dummy] Error 1
| make[2]: Leaving directory `/home/mr-4/oe/build/tmp/work/armv6-novfp-oe-linux-gnueabi/gcc-cross-initial-4.5-r38.1+svnr170880/gcc-4_5-branch/build.x86_64-linux.arm-oe-linux-gnueabi/gcc'
| make[1]: *** [all-gcc] Error 2
| make[1]: Leaving directory `/home/mr-4/oe/build/tmp/work/armv6-novfp-oe-linux-gnueabi/gcc-cross-initial-4.5-r38.1+svnr170880/gcc-4_5-branch/build.x86_64-linux.arm-oe-linux-gnueabi'
| make: *** [all] Error 2
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1
NOTE: package gcc-cross-initial-4.5-r38.1+svnr170880: task do_compile: Failed
ERROR: Function 'do_compile' failed (see /home/mr-4/oe/build/tmp/work/armv6-novfp-oe-linux-gnueabi/gcc-cross-initial-4.5-r38.1+svnr170880/temp/log.do_compile.1190 for further information)
ERROR: Task 748 (/home/mr-4/oe/openembedded/recipes/gcc/gcc-cross-initial_4.5.bb, do_compile) failed with exit code '1'
ERROR: '/home/mr-4/oe/openembedded/recipes/gcc/gcc-cross-initial_4.5.bb' failed
It looks as though ld cannot find "ppl_c" (not ppl!). What is ppl_c? The build environment I use is x86_64 (quad core CPU), running heavily upgraded and updated FC13 (most of the components are based on FC14 & FC15). The target device is htcdream (ARMv6).
Any idea what is causing this?
I've followed the installation guide (http://www.openembedded.org/wiki/Getting_started) and the only difference is that I deployed bitbake 1.12.0 instead of 1.10.2. I keep the full logs so I can post them here if there is any interest. Many thanks in advance!
next reply other threads:[~2011-11-19 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 21:07 Mr Dash Four [this message]
2011-11-24 2:54 ` "cannot find -lppl_c" link error Khem Raj
2011-11-24 13:47 ` Mr Dash Four
2011-11-24 14:26 ` Mr Dash Four
2011-11-24 17:49 ` Khem Raj
2011-11-24 18:06 ` Mr Dash Four
2011-11-24 18:27 ` Khem Raj
2011-11-25 0:52 ` Mr Dash Four
2011-11-25 5:09 ` Khem Raj
2011-11-25 5:32 ` Mr Dash Four
2011-11-25 17:26 ` Khem Raj
2011-11-25 21:50 ` Mr Dash Four
2011-11-28 20:41 ` Mr Dash Four
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=4EC81A85.8050704@googlemail.com \
--to=mr.dash.four@googlemail.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