From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] build of gcc 4.3.5 broken with BR2_GCC_USE_SJLJ_EXCEPTIONS
Date: Thu, 22 Jul 2010 23:59:25 +0200 [thread overview]
Message-ID: <4C48BF3D.4040301@gmx.net> (raw)
Hi mailinglist,
I don't need this particular option (BR2_GCC_USE_SJLJ_EXCEPTIONS) but
anyway my buildroot version (current git tree) wasn't able to build
4.3.5-final with BR2_GCC_USE_SJLJ_EXCEPTIONS=y. After deactivating it
everything was fine again.
Maybe someone is able to reproduce this behaviour and file a bug.
Regards,
Marcus
next reply other threads:[~2010-07-22 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 21:59 Ossy [this message]
2010-07-22 22:05 ` [Buildroot] build of gcc 4.3.5 broken with BR2_GCC_USE_SJLJ_EXCEPTIONS Yann E. MORIN
2010-07-27 18:30 ` Thomas Petazzoni
2010-08-01 22:23 ` Khem Raj
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=4C48BF3D.4040301@gmx.net \
--to=ossy1980@gmx.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.