All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] host-python link fails due to missing readline
Date: Mon, 1 Feb 2016 00:15:47 +0100	[thread overview]
Message-ID: <56AE95A3.8070701@mind.be> (raw)
In-Reply-To: <CAHb0ztk2fbycwTbct4gESVMVHuM==GaJsCVe1uVQiHVL5U84tA@mail.gmail.com>

On 29-01-16 01:08, Jeff Gray wrote:
> Host machine : Ubuntu 12.04.2 x86_64
> Buildroot : 2015.11.1
> Target : arm920t
> Build fail : host-python-2.7.10
> 
> Build stopped with an error during host-python:
> Failed to build these modules:
> readline
> 
> I can see that readline-6.3 has been built for target, but not host. In the log
> file, I see these references to not finding readline as expected in the
> host-python configuration stage:
> checking how to link readline libs... none
> checking for rl_callback_handler_install in -lreadline... no
> checking for rl_pre_input_hook in -lreadline... no
> checking for rl_completion_display_matches_hook in -lreadline... no
> checking for rl_completion_matches in -lreadline... no 
> 
> And then later in the build process, because readline is not there:
> running build_ext
> /usr/lib/libreadline.so: not an ELF file.

 That is just weird... For two reasons:
- it shouldn't try to link with readline to begin with;
- since this is host compilation, /usr/lib/readline.so should be OK.

 What is also weird is that configure can't find readline, but the compilation
doesn't complain about missing header files.

 Can you check from which package /usr/lib/readline.so is coming?
dpkg -S /usr/lib/readline.so

 Does your gcc somehow generate 32bit code? Are you running inside some kind of
container that could affect things?

 It may also be useful to look at the config.log of python.


> 
> Then when trying to build the readline Python extension (shortened for readability):
> building 'readline' extension
> /usr/bin/gcc ... -c /output/build/host-python-2.7.10/Modules/readline.c ...
> (some warnings but nothing serious)
> /usr/bin/gcc -pthread -shared readline.o ... -lreadline -lncurses -lpython2.7 -o
> readline.so
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libreadline.so when searching
> for -lreadline
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libreadline.so when searching
> for -lreadline
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../libreadline.so when searching for
> -lreadline
> /usr/bin/ld: skipping incompatible /usr/lib/libreadline.so when searching for
> -lreadline
> /usr/bin/ld: cannot find -lreadline
> collect2: ld returned 1 exit status 
> 
> There is no /output/host/usr/lib/gcc/x86_64/ directory. Should there be one?

 Why do you mention this directory?


 Regards,
 Arnout


> 
> I'm experienced with embedded development, but new to buildroot, so forgive me
> an obvious error. I have searched through the list archives for similar issues,
> but can't find anything since a similar problem that was reported fixed by a
> Python update (the patch which is no longer part of buildroot).
> http://lists.busybox.net/pipermail/buildroot/2014-April/094460.html
> 
> I'm not sure what area to look at for this issue. Should readline be built for
> host before the host-python build? Or is it a config error in host-python
> looking for something that isn't there?
> 
> My .config file is on Google Drive here: https://goo.gl/gLj4rM
> My full build log file (16MB) is here: https://goo.gl/NLDCOj
> 
> 
> _______________________________________________
> 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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-01-31 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  0:08 [Buildroot] host-python link fails due to missing readline Jeff Gray
2016-01-31 23:15 ` Arnout Vandecappelle [this message]
2016-02-01  0:02   ` Jeff Gray

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=56AE95A3.8070701@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 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.