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 11991] New: [numpy] segfault when compiling for RPi3 64bits
Date: Wed, 26 Jun 2019 12:50:21 +0000	[thread overview]
Message-ID: <bug-11991-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 11991
           Summary: [numpy] segfault when compiling for RPi3 64bits
           Product: buildroot
           Version: 2019.05
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: xonqnoppp at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8126
  --> https://bugs.busybox.net/attachment.cgi?id=8126&action=edit
log of numpy compilation

When building for RaspberryPi 3 with 64bits from buildroot-2019.05 I get the
attached error. It did not happen with 32bits.

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

             reply	other threads:[~2019-06-26 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 12:50 bugzilla at busybox.net [this message]
2019-07-05 21:11 ` [Buildroot] [Bug 11991] [numpy] segfault when compiling for RPi3 64bits bugzilla at busybox.net
2019-07-08 11:36 ` bugzilla at busybox.net
2019-07-08 20:25 ` bugzilla at busybox.net
2019-07-10  6:30 ` bugzilla at busybox.net
2019-07-12 19:33 ` bugzilla at busybox.net
2019-07-15  5:38 ` 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-11991-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.