From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11991] [numpy] segfault when compiling for RPi3 64bits
Date: Mon, 08 Jul 2019 11:36:17 +0000 [thread overview]
Message-ID: <bug-11991-163-9UoYMib0Rj@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11991-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11991
--- Comment #2 from XonqNopp <xonqnoppp@gmail.com> ---
Created attachment 8136
--> https://bugs.busybox.net/attachment.cgi?id=8136&action=edit
Config used when encountering numpy segfault
Attached my .config (compressed because too large for bugzilla).
I started from configs/raspberry3_64_defconfig and added the stuff I need.
About GCC version I am not sure which one you want... So I have these:
$
/home/buildroot/buildroot201907numpySegFault/output/host/bin/aarch64-buildroot-linux-uclibc-gcc
--version
aarch64-buildroot-linux-uclibc-gcc.br_real (Buildroot 2019.05) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Let me know if you want to know about another one...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-08 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:50 [Buildroot] [Bug 11991] New: [numpy] segfault when compiling for RPi3 64bits bugzilla at busybox.net
2019-07-05 21:11 ` [Buildroot] [Bug 11991] " bugzilla at busybox.net
2019-07-08 11:36 ` bugzilla at busybox.net [this message]
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-9UoYMib0Rj@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.