All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Failed building DirectFB
Date: Wed, 24 Jul 2013 11:05:01 +0100	[thread overview]
Message-ID: <51EFA6CD.9090005@imgtec.com> (raw)
In-Reply-To: <20130724095703.GA391@zuhnb712.ap.bm.net>

Hi

>
> Understood. Now I enabled imlib2.  But, then I got other errors:
>
> mkdir .libs/libidirectfbimageprovider_mpeg2.a.tmp
> (cd .libs/libidirectfbimageprovider_mpeg2.a.tmp && /home/woody/src/buildroot-2013.05/output/host/usr/bin/arm-none-linux-gnueabi-ar x ../../.libs/libidirectfbimageprovider_mpeg2.a)
> /home/woody/src/buildroot-2013.05/output/host/usr/bin/arm-none-linux-gnueabi-ld -o libidirectfbimageprovider_mpeg2.o -r .libs/libidirectfbimageprovider_mpeg2.a.tmp/*.o
> rm -f .libs/libidirectfbimageprovider_mpeg2.a.tmp/*.o && rmdir .libs/libidirectfbimageprovider_mpeg2.a.tmp
>    CCLD   libidirectfbimageprovider_imlib2.la
> /home/woody/src/buildroot-2013.05/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: library search path "/usr/lib" is unsafe for cross-compilation
> /usr/lib/libImlib2.so: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[5]: *** [libidirectfbimageprovider_imlib2.la] Error 1

This is because it picks the imlib2-config on the host instead of the 
one in the staging directory. This has been fixed here

http://git.buildroot.net/buildroot/commit/package/directfb/directfb.mk?id=88378877273829c387f48a6c96959712b892856f

but it's not in the release you are using.

  reply	other threads:[~2013-07-24 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  9:10 [Buildroot] Failed building DirectFB Woody Wu
2013-07-24  9:30 ` Thomas De Schampheleire
2013-07-24  9:57   ` Woody Wu
2013-07-24 10:05     ` Markos Chandras [this message]
2013-07-24 13:34       ` Woody Wu
2013-07-24 13:37         ` Thomas De Schampheleire
2013-07-24 13:40           ` Woody Wu
2013-07-25  0:53           ` Woody Wu
2013-07-24 13:48         ` Markos Chandras

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=51EFA6CD.9090005@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=buildroot@busybox.net \
    /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.