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 9571] New: buildroot fails while building opencv for arm64 platform
Date: Fri, 06 Jan 2017 09:54:53 +0000	[thread overview]
Message-ID: <bug-9571-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9571
           Summary: buildroot fails while building opencv for arm64
                    platform
           Product: buildroot
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: saik.iitk at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

i am getting the following error while building opencv. During opencv_core
building, it is linking the following 


sw/tools/linaro/gcc-aarch64-linux-gnu-4.9-2014.09/bin/../lib/gcc/aarch64-linux-gnu/4.9.2/../../../../aarch64-linux-gnu/bin/ld:
/local_disk/sai/wpu_aug23/wpu-sw/src/common/utils/buildroot/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib/aarch64-linux-gnu/libm.a(k_standard.o)(.text+0x318):
unresolvable R_AARCH64_ADR_PREL_PG_HI21 relocation against symbol
`stderr@@GLIBC_2.17'


and sinc libm.a is not built with option "-fPIC", The error can come and libm.a
is default generated part of buildroot and i cannot build here. 


Please have a look

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

             reply	other threads:[~2017-01-06  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  9:54 bugzilla at busybox.net [this message]
2017-01-06 21:43 ` [Buildroot] [Bug 9571] buildroot fails while building opencv for arm64 platform bugzilla at busybox.net
2017-01-10  5:35 ` 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-9571-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.