Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] BB update Was:  Build jobbing
Date: Sun, 29 Nov 2009 11:23:28 +0100	[thread overview]
Message-ID: <87iqct39zz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200911290331.03877.minimod@morethan.org> (Michael S. Zick's message of "Sun\, 29 Nov 2009 03\:31\:01 -0600")

>>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:

 >> That's imho fairly clearly not about basic setjmp/longjmp support.

 Michael> Only when you are thinking about building a compiler, but if
 Michael> instead you happen to be an applications programmer, who
 Michael> doesn't know or care how the compiler works internally...

Then he probably shouldn't be changing stuff under toolchain options ;)

 Michael> I only now recognize why it seems clear to you - because I did live
 Michael> on the gcc list once upon a time - not all of the buildroot users
 Michael> have that background.

Actually I haven't done much gcc development. The
BR2_GCC_USE_SJLJ_EXCEPTIONS option got added back in 2004 by Erik really
in beginning of BR development. I don't know of anything needing it
today.

In general, we try to use sensible defaults - If you don't understand an
option, just leave it at default.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-11-29 10:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 21:22 [Buildroot] Build jobbing Michael S. Zick
2009-11-27 21:56 ` Peter Korsgaard
2009-11-27 22:10   ` Michael S. Zick
2009-11-27 22:16     ` Michael S. Zick
2009-11-27 22:33       ` Michael S. Zick
2009-11-27 22:45         ` Michael S. Zick
2009-11-27 22:59           ` Michael S. Zick
2009-11-28 10:40       ` Peter Korsgaard
2009-11-28 10:45     ` Peter Korsgaard
2009-11-28 11:10       ` Michael S. Zick
2009-11-28 11:38         ` Michael S. Zick
2009-11-28 18:58           ` Michael S. Zick
2009-11-28 14:07     ` Peter Korsgaard
2009-11-28 14:13       ` Michael S. Zick
2009-11-28 15:35         ` [Buildroot] BB update Was: " Michael S. Zick
2009-11-28 15:43           ` Michael S. Zick
2009-11-28 19:06             ` Peter Korsgaard
2009-11-28 19:15               ` Michael S. Zick
2009-11-28 19:20                 ` Peter Korsgaard
2009-11-28 19:06           ` Peter Korsgaard
2009-11-28 19:17             ` Michael S. Zick
2009-11-28 19:41               ` Michael S. Zick
2009-11-28 20:30                 ` Peter Korsgaard
2009-11-28 21:16                   ` Michael S. Zick
2009-11-28 22:44                     ` Peter Korsgaard
     [not found] ` <200911281650.44375.minimod@morethan.org>
     [not found]   ` <87r5rh3e8w.fsf@macbook.be.48ers.dk>
2009-11-29  9:16     ` Michael S. Zick
     [not found] ` <200911290302.13984.minimod@morethan.org>
     [not found]   ` <87my253d8o.fsf@macbook.be.48ers.dk>
2009-11-29  9:31     ` Michael S. Zick
2009-11-29 10:23       ` Peter Korsgaard [this message]
2009-11-29 10:53         ` Michael S. Zick
2009-11-29 11:23           ` Michael S. Zick
2009-11-29 12:54           ` Michael S. Zick
2009-11-29 16:50           ` Michael S. Zick
2009-11-29 18:11             ` Michael S. Zick

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=87iqct39zz.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --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