From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool problem building mesa3d-demos
Date: Sat, 02 May 2015 00:14:37 +0200 [thread overview]
Message-ID: <5543FACD.4010307@mind.be> (raw)
In-Reply-To: <CAD7j7Q96pGF1qedawQw4-FHSyC15EyXH1DBu=MNkvFQg_Ys-dg@mail.gmail.com>
On 01/05/15 22:41, Carlos Soto wrote:
> Hi,
> I'm using buildroot to create a rootfs for iMX6-quad. I'm using an external
> toolchain created with crosstool-ng (arm-cortexa9_neon-linux-gnueabihf).
> When building mesa3d-demos, there is an error creating libutil.la
> <http://libutil.la>:
>
> libtool: error:
> '/home/starsl/iMX6/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/local/xtools/arm-cortexa9_neon-linux-gnueabihf/lib/gcc/arm-cortexa9_neon-linux-gnueabihf/4.9.1/../../../../arm-cortexa9_neon-linux-gnueabihf/lib/libstdc++.la'
> is not a valid libtool archive
>
> Of corse, this path is not right, it seems to be joining two different paths.
>
> I've tracked the source of the problem, and it seems to be related with the
> libtool used by buildroot. I've modified the resulting Makefiles to use the host
> libtool, and the problem disappears:
You have to use buildroot's libtool, otherwise you may get other problems with
cross-compilation.
>
> LIBTOOL = $(SHELL) $(top_builddir)/libtool to
> LIBTOOL = $(SHELL) /usr/bin/libtool
>
> Any thoughts about what it's going wrong?
Can you tell us which options are given to libtool, and perhaps run it with -v
to see what it does?
Regards,
Arnout
>
> Regards,
> Carlos
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-05-01 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 20:41 [Buildroot] Libtool problem building mesa3d-demos Carlos Soto
2015-05-01 22:14 ` Arnout Vandecappelle [this message]
2015-05-02 16:04 ` Carlos Soto
2015-05-02 19:19 ` Arnout Vandecappelle
2015-05-02 20:42 ` Carlos Soto
2015-05-02 20:45 ` Arnout Vandecappelle
2015-05-02 21:16 ` Carlos Soto
2015-05-02 21:26 ` Arnout Vandecappelle
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=5543FACD.4010307@mind.be \
--to=arnout@mind.be \
--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