All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13356] New: libabseil-cpp: not building for raspberry pi
Date: Fri, 04 Dec 2020 09:32:26 +0000	[thread overview]
Message-ID: <bug-13356-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13356

            Bug ID: 13356
           Summary: libabseil-cpp: not building for raspberry pi
           Product: buildroot
           Version: 2020.11
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: buildroot at heine.tech
                CC: buildroot at uclibc.org
  Target Milestone: ---

I just stumbled across this but currently don't have the time to investigate
further.

libabseil-cpp fails to compile for raspberry pi targets with the following
error:

In file included from
/build/build/build/libabseil-cpp-20200923.2/absl/random/internal/randen_hwaes.cc:229:
/build/build/host/opt/ext-toolchain/lib/gcc/arm-none-linux-gnueabihf/9.2.1/include/arm_neon.h:
In function 'Vector128 {anonymous}::AesRound(const Vector128&, const
Vector128&)':
/build/build/host/opt/ext-toolchain/lib/gcc/arm-none-linux-gnueabihf/9.2.1/include/arm_neon.h:16925:1:
error: inlining failed in call to always_inline 'uint8x16_t
vaesmcq_u8(uint8x16_t)': target specific option mismatch
16925 | vaesmcq_u8 (uint8x16_t __data)
      | ^~~~~~~~~~
/build/build/build/libabseil-cpp-20200923.2/absl/random/internal/randen_hwaes.cc:255:20:
note: called from here
  255 |   return vaesmcq_u8(vaeseq_u8(state, uint8x16_t{})) ^ round_key;
      |          ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/build/build/build/libabseil-cpp-20200923.2/absl/random/internal/randen_hwaes.cc:229:
/build/build/host/opt/ext-toolchain/lib/gcc/arm-none-linux-gnueabihf/9.2.1/include/arm_neon.h:16911:1:
error: inlining failed in call to always_inline 'uint8x16_t
vaeseq_u8(uint8x16_t, uint8x16_t)': target specific option mismatch
16911 | vaeseq_u8 (uint8x16_t __data, uint8x16_t __key)
      | ^~~~~~~~~
/build/build/build/libabseil-cpp-20200923.2/absl/random/internal/randen_hwaes.cc:255:20:
note: called from here
  255 |   return vaesmcq_u8(vaeseq_u8(state, uint8x16_t{})) ^ round_key;
      |          ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: ***
[absl/random/CMakeFiles/random_internal_randen_hwaes_impl.dir/build.make:63:
absl/random/CMakeFiles/random_internal_randen_hwaes_impl.dir/internal/randen_hwaes.cc.o]
Error 1
make[3]: *** [CMakeFiles/Makefile2:2115:
absl/random/CMakeFiles/random_internal_randen_hwaes_impl.dir/all] Error 2
make[3]: *** Waiting for unfinished jobs....



It is already reported upstream at
https://github.com/abseil/abseil-cpp/issues/662 (on comment points out it is
also not compiling for arm/rpi3)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-12-04  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  9:32 bugzilla at busybox.net [this message]
2020-12-04 18:15 ` [Buildroot] [Bug 13356] libabseil-cpp: not building for raspberry pi bugzilla at busybox.net
2020-12-04 18:18 ` bugzilla at busybox.net
2022-07-27 18:34 ` bugzilla

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=bug-13356-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.