From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool problem building mesa3d-demos
Date: Sat, 02 May 2015 22:45:04 +0200 [thread overview]
Message-ID: <55453750.9080302@mind.be> (raw)
In-Reply-To: <CAD7j7Q9-bJDVNo7yfOowfuiD6X=KTPjTwvGtznoenG8c2Hzqxg@mail.gmail.com>
On 02/05/15 22:42, Carlos Soto wrote:
>
> Since this xtools thing is not passed on the command line, it must be in your
> environment. Can you do 'env | grep xtools'?
>
> Regards,
> Arnout
>
> No, it's not in my environment. As far as I can tell, libtool seems to be
> joining together my toolchain path
> (usr/local/xtools//arm-cortexa9_neon-linux-gnueabihf) and the buildroot staging
> sysroot path (
> /home/starsl/iMX6/buildroot/output/host/usr/lib)
OK, so then there must be some .la file which has something funny. Can you grep
for xtools in all the .la files in output/ ?
Regards,
Arnout
--
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-02 20:45 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
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 [this message]
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=55453750.9080302@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