From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Fri, 30 Sep 2011 22:35:26 +0200 [thread overview]
Message-ID: <20110930223526.6aa05012@skate> (raw)
In-Reply-To: <20110930215915.3d7fad80@skate>
Le Fri, 30 Sep 2011 21:59:15 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> Maybe you should raise the issue on the uClibc mailing list?
A quick data point: I tested a build with gcc 4.6.1, uClibc 0.9.32,
NPTL, and both iperf and dbus-daemon start fine for me:
# iperf
Usage: iperf [-s|-c host] [options]
Try `iperf --help' for more information.
# dbus-daemon
No configuration file specified.
dbus-daemon [--version] [--session] [--system] [--config-file=FILE] [--print-address[=DESCRIPTOR]] [--print-pid[=DESCRIPTOR]] [--fork] [--nofork] [--introspect] [--address=ADDRESS] [--systemd-activation]
# uname -a
Linux buildroot 2.6.38.8 #1 Fri Sep 30 20:24:38 UTC 2011 armv5tejl
GNU/Linux
My target optimization options is:
BR2_GCC_TARGET_TUNE="arm926ej-s"
BR2_GCC_TARGET_ARCH="armv5te"
BR2_GCC_TARGET_ABI="aapcs-linux"
Therefore, I guess that the problem might be iwmmxt related. Can you
try with "lower" optimization options ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-30 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 8:04 [Buildroot] Segmentation faults after gcc update Sven Neumann
2011-09-27 21:35 ` Thomas Petazzoni
2011-09-28 8:57 ` Sven Neumann
2011-09-28 14:44 ` Sven Neumann
2011-09-30 9:06 ` Sven Neumann
2011-09-30 19:59 ` Thomas Petazzoni
2011-09-30 20:35 ` Thomas Petazzoni [this message]
2012-02-20 10:37 ` Sven Neumann
2012-02-20 16:55 ` Thomas Petazzoni
2011-10-04 9:20 ` Sven Neumann
2011-09-27 21:36 ` Thomas Petazzoni
2011-09-28 9:18 ` Sven Neumann
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=20110930223526.6aa05012@skate \
--to=thomas.petazzoni@free-electrons.com \
--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.