From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] could not read symbols: Bad value error on musl based buildroot env on rpi2 config.
Date: Mon, 18 Jan 2016 09:59:02 +0100 [thread overview]
Message-ID: <569CA956.2050103@mind.be> (raw)
In-Reply-To: <569C84F2.1050309@scalemp.com>
[Please don't top-post, but reply in-line like I do below.]
On 18-01-16 07:23, Eial Czerwacki wrote:
> Greetings,
>
> the pastebin can be found at http://paste.ubuntu.com/14565509/
Hm, no reference to /usr/local/lib there...
First of all, can you confirm that this happened while building host-python? I
don't see what else it could be, but just to be sure.
Then, could you try to grep in the host-python build directory for the
occurence of /usr/local/lib? It must come from somewhere...
> what makes it a bit weirder is that on my 64 bit gentoo machine (this is
> a 32 bit ubuntu 12.04 machine) it compiles well.
I don't expect it has anything to do with that, it's just that your gentoo
machine has a python installed in /usr/local while your ubuntu machine doesn't.
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . 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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-01-18 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 15:42 [Buildroot] could not read symbols: Bad value error on musl based buildroot env on rpi2 config Eial Czerwacki
2016-01-17 20:35 ` Arnout Vandecappelle
2016-01-18 6:23 ` Eial Czerwacki
2016-01-18 8:59 ` Arnout Vandecappelle [this message]
2016-01-18 9:09 ` Eial Czerwacki
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=569CA956.2050103@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