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 9916] qt5 does not build on arm-buildroot-linux-uclibcgnueabihf for ARMv8 cores
Date: Thu, 13 Jul 2017 18:42:10 +0000	[thread overview]
Message-ID: <bug-9916-163-vfY4UMaf0T@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9916-163@https.bugs.busybox.net/>

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

--- Comment #2 from Ivan <ivan.nazarenko@gmail.com> ---
Sorry if I did not get it. I am sort of a newbie.

Downloaded from git yesterday, selected the default raspberrypi3_defconfig,
QT5.8, GCC 6.4, musl, binutils 2.28. The built stopped in qt5base in the same
file above, for apparently the same reason:

tools/qhash.cpp:148:54: error: attribute(target("+crc")) is unknown
 static uint crc32(const Char *ptr, size_t len, uint h)

But the patch that you mentions "need to backport" seems already applied in the
sources in output/build/host-binutils-2.28! At least the files the patch is
supposed to change are already in the changed form.

So I did not get what is needed to solve this build issue.

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

  parent reply	other threads:[~2017-07-13 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 13:59 [Buildroot] [Bug 9916] New: qt5 does not build on arm-buildroot-linux-uclibcgnueabihf bugzilla at busybox.net
2017-05-30 14:58 ` [Buildroot] [Bug 9916] qt5 does not build on arm-buildroot-linux-uclibcgnueabihf for ARMv8 cores bugzilla at busybox.net
2017-05-30 15:00 ` bugzilla at busybox.net
2017-07-13 18:42 ` bugzilla at busybox.net [this message]
2017-07-13 20:33 ` bugzilla at busybox.net
2017-07-19 20:26 ` bugzilla at busybox.net

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-9916-163-vfY4UMaf0T@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.