Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08
Date: Tue, 14 May 2019 22:36:08 +0200	[thread overview]
Message-ID: <20190514203608.GG2787@scaer> (raw)
In-Reply-To: <52f30b47-7416-e4d1-cb63-29ee8f6c7b88@micronovasrl.com>

Giulio, All,

On 2019-05-11 23:00 +0200, Giulio Benetti spake thusly:
> Hello Yann, All,
> 
> Il 09/05/2019 23:19, Giulio Benetti ha scritto:
> >>>       aarch64 |            python-numpy-1.16.3 | NOK | http://autobuild.buildroot.net/results/50f7f09a9f830cd7b94f8fc83c09fc3d39297d3d |
> >>
> >>/home/buildroot/autobuild/run/instance-2/output/host/bin/aarch64-linux-gnu-gcc /tmp/tmph865w02v/tmp/tmph865w02v/source.o -L/home/buildroot/autobuild/run/instance-2/output/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib -lcblas -o /tmp/tmph865w02v/a.out
> >>/home/buildroot/autobuild/run/instance-2/output/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/libcblas.so: undefined reference to `scnrm2_'
> >>/home/buildroot/autobuild/run/instance-2/output/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib/libcblas.so: undefined reference to `scasum_'
> >>collect2: error: ld returned 1 exit status
> >>/home/buildroot/autobuild/run/instance-2/output/host/bin/aarch64-linux-gnu-gcc /tmp/tmph865w02v/tmp/tmph865w02v/source.o -L/home/buildroot/autobuild/run/instance-2/output/host/aarch64-buildroot-linux-gnu/sysroot/usr/lib -lblas -o /tmp/tmph865w02v/a.out
> >>/tmp/tmph865w02v/tmp/tmph865w02v/source.o: In function `main':
> >>/tmp/tmph865w02v/source.c:6: undefined reference to `cblas_ddot'
> >>collect2: error: ld returned 1 exit status
> >>
> >>I'm not sure what's going on here. Sadly, Samuel who was maintaining
> >>python-numpy, is no longer active in Buildroot. Is there anyone else
> >>volunteering to have a look ?
> >
> >I can try to work this out.
> >
> 
> As spoken in IRC this builds correctly with every Docker in Adam Duskett:
> https://github.com/aduskett/buildroot-docker-devel
> 
> included Ubuntu 14.04(Trusty), the same as Yann's Autobuilder.
> 
> I'm waiting for Yann to report if it works for him too or not.

Here is a quick summary of Giulio's and my findings:

Usign the configuration from the failed autobuild job:

  - make clean; make python-numpy    --> builds OK

  - make clean; make   --> fails to build

The root cause is a hidden dependency on lapack. When lapack is build
before python-numpy (which is highly possible, because of alphabetical
ordering), then python-numpy detects it and fails to build properly in
this case.

So, I can see two solutions:

  - add an explicit, conditional dependency on lapack, and fix the
    build,

  - explicitly tell python-numpy to never use lapack.

Obviously, the first would be preferred, but it's probably non-trivial.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-05-14 20:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08 Thomas Petazzoni
2019-05-09 21:03 ` Thomas Petazzoni
2019-05-09 21:19   ` Giulio Benetti
2019-05-11 21:00     ` Giulio Benetti
2019-05-14 20:36       ` Yann E. MORIN [this message]
2019-05-14 21:47         ` Giulio Benetti
2019-05-09 21:41   ` LP C
2019-05-10  8:59   ` Vadym Kochan
2019-05-13 11:20   ` Julien Boibessot
2019-05-13 11:31     ` Thomas Petazzoni
2019-05-13 15:59       ` Julien Boibessot
2019-05-25 15:31         ` Arnout Vandecappelle
2019-05-26 14:08           ` LP C
2019-05-26 18:36             ` Thomas Petazzoni
2019-05-23  7:07   ` Nylon Chen

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=20190514203608.GG2787@scaer \
    --to=yann.morin.1998@free.fr \
    --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