From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2143] New: buildroot compiler generates segfaulting statically linked executables
Date: Mon, 28 Jun 2010 22:13:56 +0000 (UTC) [thread overview]
Message-ID: <bug-2143-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2143
Summary: buildroot compiler generates segfaulting statically
linked executables
Product: buildroot
Version: 2010.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: sander.ashwin at live.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hello,
I'm using buildroot 2010.05 (also tried latest git version). The target is
i586.
All buildroot's settings are default (except for the architecture).
All statically linked executables generated by the buildroot's gcc compiler
immediately segfault when they start.
I tried to compile Busybox, udev and sysvinit, but they all segfault.
When compiling dynamically linked, they all run fine.
My host OS is Fedora 13 x64 with all the latest updates installed.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-06-28 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 22:13 bugzilla at busybox.net [this message]
2010-07-06 12:23 ` [Buildroot] [Bug 2143] buildroot compiler generates segfaulting statically linked executables bugzilla at busybox.net
2010-07-08 8:04 ` 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-2143-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox