Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Prasad Sankaran <prasad@cradlewise.com>
Cc: Archit Taneja <archit@cradlewise.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Not able to build python-numpy 1.23.5 on buildroot
Date: Sat, 21 Jan 2023 16:18:15 +0100	[thread overview]
Message-ID: <20230121151815.GD558596@scaer> (raw)
In-Reply-To: <CANtE+cKcemOj_DTSOZ_TzuThSrXBwah38WJYM-AVH1nGTJikDw@mail.gmail.com>

Prasad, All,

On 2023-01-21 20:12 +0530, Prasad Sankaran via buildroot spake thusly:
> The following errors are reported while generating numpy/core/_ [1]multiarray_umath.cpython-38-aarch64-linux-gnu.so using
> aarch64-buildroot-linux-gnu-gcc.
> Is there a way to avoid including AVX512 .s files from the compilation?
> 
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:19: Error: unknown mnemonic   pushq' -- pushq %rbp'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:21: Error: unknown mnemonic   movq' -- movq %rsp,%rbp'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:24: Error: unknown mnemonic   andq' -- andq $-64,%rsp'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:25: Error: unknown mnemonic   subq' -- subq $192,%rsp'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:26: Error: unknown mnemonic   vmovups' -- vmovups
> __svml_dacos_data_internal(%rip),%zmm7'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:27: Error: unknown mnemonic   vmovups' -- vmovups
> 64+__svml_dacos_data_internal(%rip),%zmm8'
> numpy/core/src/umath/svml/linux/avx512/svml_z0_acos_d_la.s:30: Error: unknown mnemonic   vmovups' -- vmovups
> 128+__svml_dacos_data_internal(%rip),%zmm11'

I was not able to reproduce such an error here, with the following
defconfig and master as of commit f090116066:

    BR2_aarch64=y
    BR2_TOOLCHAIN_EXTERNAL=y
    BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
    BR2_PER_PACKAGE_DIRECTORIES=y
    BR2_PACKAGE_PYTHON3=y
    BR2_PACKAGE_PYTHON_NUMPY=y

Can you share a _minimal_ defconfig that exhibits the issue?

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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-01-21 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 14:42 [Buildroot] Not able to build python-numpy 1.23.5 on buildroot Prasad Sankaran via buildroot
2023-01-21 15:18 ` Yann E. MORIN [this message]
2023-01-25 15:36   ` Prasad Sankaran via buildroot
2023-01-29 19:03     ` Yann E. MORIN

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=20230121151815.GD558596@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=archit@cradlewise.com \
    --cc=buildroot@buildroot.org \
    --cc=prasad@cradlewise.com \
    /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