Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] BB update Was:  Build jobbing
Date: Sun, 29 Nov 2009 03:31:01 -0600	[thread overview]
Message-ID: <200911290331.03877.minimod@morethan.org> (raw)
In-Reply-To: <87my253d8o.fsf@macbook.be.48ers.dk>

On Sun November 29 2009, Peter Korsgaard wrote:
> >>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:
> 
> Hi,
> 
>  Michael> Well, then the text in the menu must be mis-leading. . .
>  Michael> it must be refering to generation/use of setjmp/longjmp
>  Michael> somewhere other than in the target applications compiled.
> 
> config BR2_GCC_USE_SJLJ_EXCEPTIONS
>         bool "Enable setjmp/longjmp exceptions?"
>         help
>           For some platforms, the 

            internal 

>           stack unwinding 

            that gcc generates for stack traces and debugging info

>           works perfectly, 
>           while other platforms must use setjmp/longjmp exceptions for
>           proper stack unwinding during exception handling.  

            This does not effect the use of setjmp/longjmp in applications
            compiled by gcc.

>           Most people can leave this set to n.
> 
> That's imho fairly clearly not about basic setjmp/longjmp support.
> 

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

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

>  Michael> The most recent build has the option enabled, will see if
>  Michael> it makes a difference.
> 
>  Michael> I did not test yesterday's build because of local work rules:
>  Michael> 1) No shift longer than 18 hours;
>  Michael> 2) A minimum of 4 hours off between shifts.
> 
> ;)
> 

Mike

  parent reply	other threads:[~2009-11-29  9:31 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 [this message]
2009-11-29 10:23       ` Peter Korsgaard
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=200911290331.03877.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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