From: Javier Viguera <javier.viguera@digi.com>
To: buildroot@busybox.net
Subject: [Buildroot] gst-plugins-ugly fail to build
Date: Mon, 3 May 2010 12:06:08 +0200 [thread overview]
Message-ID: <4BDEA010.4010509@digi.com> (raw)
Hi all,
Seems that somehow a host library is leaking when cross-building
gst-plugins-ugly for ARM.
My current setup is latest buildroot (git sha1 0cd0d0647) with external
toolchain built with crosstool-NG (arm + eglibc toolchain).
The error reported is:
libtool: link:
/usr/local/DigiEL-5.5/x-tools/arm-unknown-linux-gnueabi/bin/arm-linux-gcc
-O3 -mcpu=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp
-ffast-math -fsingle-precision-constant -O3 -mabi=aapcs-linux
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
--sysroot /data/repo/buildroot.git/output/staging/ -shared
.libs/libgstmpegaudioparse_la-plugin.o
.libs/libgstmpegaudioparse_la-gstmpegaudioparse.o
.libs/libgstmpegaudioparse_la-gstxingmux.o -Wl,-rpath
-Wl,/data/repo/buildroot.git/output/host/usr/lib -Wl,-rpath
-Wl,/data/repo/buildroot.git/output/host/usr/lib -lgstbase-0.10
-L/data/repo/buildroot.git/output/host/lib
-L/data/repo/buildroot.git/output/host/usr/lib -lgstreamer-0.10
/data/repo/buildroot.git/output/host/usr/lib/libgobject-2.0.so
/data/repo/buildroot.git/output/host/usr/lib/libgmodule-2.0.so -ldl
/data/repo/buildroot.git/output/host/usr/lib/libgthread-2.0.so -lpthread
-lrt -lxml2 /data/repo/buildroot.git/output/host/usr/lib/libglib-2.0.so
-lintl -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mabi=aapcs-linux
-mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mabi=aapcs-linux -pthread
-pthread -pthread -Wl,-soname -Wl,libgstmpegaudioparse.so
-Wl,-version-script -Wl,.libs/libgstmpegaudioparse.ver -o
.libs/libgstmpegaudioparse.so
> /data/repo/buildroot.git/output/host/usr/lib/libgobject-2.0.so: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
So it seems that it's trying to link a library built for the host while
cross-compiling for the target and it fails.
Attached also the failing buildroot config file for anyone to reproduce.
I have also a complete build.log file but it is about 175KB compressed
so i guess the list won't accept such big files.
Does anyone have the same problem? Known bug?
--
Regards,
Javier Viguera
Software Engineer
Digi International Spain, S.A.
http://www.digi.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: br.config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100503/b3e05cb4/attachment-0001.diff>
next reply other threads:[~2010-05-03 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 10:06 Javier Viguera [this message]
2010-05-03 10:20 ` [Buildroot] gst-plugins-ugly fail to build Thomas Petazzoni
2010-05-03 10:22 ` Lionel Landwerlin
2010-05-03 12:23 ` Javier Viguera
2010-05-03 12:41 ` Thomas Petazzoni
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=4BDEA010.4010509@digi.com \
--to=javier.viguera@digi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox