From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] bug report: c++ programs built by toolchain crash by seg fault
Date: Tue, 5 Feb 2013 08:45:02 +0100 [thread overview]
Message-ID: <20130205084502.6b370422@skate> (raw)
In-Reply-To: <CAJXWAwwHVddYF3StQByTW99aCDksiAwyOa_WdM7AbjGu3i6iJg@mail.gmail.com>
Dear hayate,
On Tue, 5 Feb 2013 14:24:55 +0800, hayate wrote:
> arm little endian; generic arm; OABI; gcc 4.6.3 with c++ support;
> uclibc 0.9.31.1
Can you test with EABI?
Really OABI is deprecated. It would not be surprising at all that there
are issues with OABI.
Do you have a compelling reason to stick with OABI if you are making a
new toolchain?
Best regards,
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:[~2013-02-05 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 6:24 [Buildroot] bug report: c++ programs built by toolchain crash by seg fault hayate
2013-02-05 7:45 ` Thomas Petazzoni [this message]
[not found] ` <CAJXWAwzg3iPu6qW+E560nw=fQZ6=UMhNAkTGhbaoCnFbcfQdzQ@mail.gmail.com>
2013-02-05 10:15 ` [Buildroot] Fwd: " hayate
2013-02-06 23:48 ` Arnout Vandecappelle
2013-02-08 4:57 ` hayate
2013-02-05 13:39 ` [Buildroot] " hayate
2013-02-06 22:15 ` Yann E. MORIN
2013-02-08 5:04 ` hayate
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=20130205084502.6b370422@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox