From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] Building host-python-2.7.15 Failed
Date: Thu, 24 Jan 2019 10:18:13 -0200 (BRST) [thread overview]
Message-ID: <1878793170.3712761.1548332293148.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20190120141318.szbl7zs4bgazznov@vkochan-ThinkPad-T470p>
> From: "Vadim Kochan" <vadim4j@gmail.com>
> To: "Woody Wu" <narkewoody@gmail.com>
> Cc: "buildroot" <buildroot@busybox.net>
> Sent: Domingo, 20 de janeiro de 2019 12:13:18
> Subject: Re: [Buildroot] Building host-python-2.7.15 Failed
> Hi,
>
> On Sun, Jan 20, 2019 at 08:51:32PM +0800, Woody Wu wrote:
>> Hi,
>>
>> My savedefconfig:
>>
>> BR2_arm=y
>> BR2_cortex_a8=y
>> BR2_ARM_FPU_NEON=y
>> BR2_DL_DIR="$(TOPDIR)/../downloads"
>> BR2_TOOLCHAIN_EXTERNAL=y
>> BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
>> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="$(ARCH)-linux-gnueabihf"
>> BR2_TOOLCHAIN_EXTERNAL_GCC_7=y
>> BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_10=y
>> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
>> BR2_TOOLCHAIN_EXTERNAL_CXX=y
>> BR2_PACKAGE_IOSTAT=y
>> BR2_PACKAGE_NODEJS=y
>> BR2_PACKAGE_PYTHON=y
>>
>> BTW: My building system is ubuntu 18.10. The target is armv7
>>
>>
>> On Sun, Jan 20, 2019 at 12:24 AM Vadim Kochan <vadim4j@gmail.com> wrote:
>>
>> > Hi Woody,
>> >
>> > On Sun, Jan 20, 2019 at 12:15:36AM +0800, Woody Wu wrote:
>> > > Hi,
>> > >
>> > > This is buildroot-2018.11.1. I found I cannot build some packages with
>> > > buildroot, the problem seemed in the building of the host-python. Below
>> > is
>> > > the log:
>> > >
>> > > >>> host-python 2.7.15 Building
>> > >
>> > PATH="/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/bin:/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/sbin:/opt/linaro/gcc-linaro-7.3.1-2018.05-x86_64_arm-linux-gnueabihf/bin:/home/woody/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin"
>> > >
>> > PKG_CONFIG="/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/bin/pkg-config"
>> > > PKG_CONFIG_SYSROOT_DIR="/" PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1
>> > > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1
>> > >
>> > PKG_CONFIG_LIBDIR="/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/lib/pkgconfig:/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/share/pkgconfig"
>> > > /usr/bin/make -j1 -C
>> > >
>> > /home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/build/host-python-2.7.15/
>> > > running build
>> > > running build_ext
>> > > INFO: Can't locate Tcl/Tk libs and/or headers
>> > > building 'crypt' extension
>> > > /usr/bin/gcc -pthread -fPIC -fno-strict-aliasing -O2
>> > >
>> > -I/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/include
>> > > -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude
>> > -I./Include
>> > >
>> > -I/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/host/include
>> > > -I/usr/include/x86_64-linux-gnu -I/usr/local/include
>> > >
>> > -I/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/build/host-python-2.7.15/Include
>> > >
>> > -I/home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/build/host-python-2.7.15
>> > > -c
>> > >
>> > /home/woody/beacon-cross-build/buildroot/buildroot-2018.11.1/output/build/host-python-2.7.15/Modules/cryptmodule.c
>> > > -o
>> > >
>> > 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
>> > > /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
>> > > /usr/bin/ld: final link failed: bad value
>> > > collect2: error: ld returned 1 exit status
>> > >
>> > > Python build finished, but the necessary bits to build these modules were
>> > > not found:
>> > > _bsddb _sqlite3 _tkinter
>> > > bsddb185 bz2 dbm
>> > > dl gdbm imageop
>> > > readline sunaudiodev
>> > > To find the necessary bits, look in setup.py in detect_modules() for the
>> > > module's name.
>> > >
>> > > Failed to build these modules:
>> > > crypt
>> > > =============
>> > >
>> > > Can someone have a look at it and give me a hint?
>> > >
>> > > Thanks!
>> > >
>
> So, you are using custom toolchain, I used this defconfig:
>
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_FPU_NEON=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_PACKAGE_IOSTAT=y
> BR2_PACKAGE_NODEJS=y
> BR2_PACKAGE_PYTHON=y
>
> and it builds OK on master and 2018.11.1 tag.
It's a failure in the build of a host package so the toolchain, which
is used to build target packages, should not be relevant.
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
next prev parent reply other threads:[~2019-01-24 12:18 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 [this message]
2019-01-25 23:34 ` Arnout Vandecappelle
2019-01-26 14:10 ` Thomas Petazzoni
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=1878793170.3712761.1548332293148.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.