From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building host-python-2.7.15 Failed
Date: Sat, 26 Jan 2019 15:10:22 +0100 [thread overview]
Message-ID: <20190126151022.23c5a011@windsurf> (raw)
In-Reply-To: <8017d9a3-290f-f8de-8e13-55430ace2b77@mind.be>
Hello,
On Sat, 26 Jan 2019 00:34:31 +0100, Arnout Vandecappelle wrote:
> On 19/01/2019 17:15, Woody Wu wrote:
> > /usr/bin/gcc -pthread -shared
> > -L/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/lib
> > -Wl,-rpath,/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/lib
> > -Wl,--enable-new-dtags
> > build/temp.linux-x86_64-2.7/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/build/host-python-2.7.15/Modules/cryptmodule.o
> > -L/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/lib
> > -L/usr/lib/x86_64-linux-gnu -L/usr/local/lib -L. -lcrypt -lpython2.7 -o
> > build/lib.linux-x86_64-2.7/crypt.so
> > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libcrypt.a(crypt-entry.o): relocation
> > R_X86_64_PC32 against symbol `_ufc_foobar' can not be used when making a shared
> > object; recompile with -fPIC
>
> There is something wrong with your host compiler. There should be a
> /lib*/libcrypt.so that the compiler links against, instead of
> /usr/lib/libcrypt.a. On which distro do you work?
Woody said: "My building system is ubuntu 18.10"
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-26 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 16:15 [Buildroot] Building host-python-2.7.15 Failed Woody Wu
2019-01-19 16:33 ` Vadim Kochan
2019-01-20 12:51 ` Woody Wu
2019-01-20 14:13 ` Vadim Kochan
2019-01-20 16:08 ` Woody Wu
2019-01-23 4:06 ` Woody Wu
2019-01-24 12:18 ` Carlos Santos
2019-01-25 23:34 ` Arnout Vandecappelle
2019-01-26 14:10 ` Thomas Petazzoni [this message]
2019-01-26 16:27 ` Woody Wu
2019-01-27 17:06 ` Woody Wu
2019-01-27 19:55 ` Thomas Petazzoni
2019-01-30 5:29 ` Woody Wu
2019-01-26 14:09 ` 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=20190126151022.23c5a011@windsurf \
--to=thomas.petazzoni@bootlin.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