From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: prevent -O0 for glibc builds?
Date: Thu, 10 Jul 2008 08:21:24 -0700 [thread overview]
Message-ID: <1215703284.32070.6.camel@isis> (raw)
In-Reply-To: <48761569.4080304@gmx.net>
On Thu, 2008-07-10 at 15:58 +0200, Robert Schuster wrote:
> Hi,
> recently I set the (debug) optimization flags to "-g -O0" (= really
> no-optimization and full debug infos) and got an error from the glibc
> builds because glibc's configury told me that it cannot be compiled with
> no optimization.
>
> Would it be possible that the glibc recipes replace -O0 with something
> else and print a note about this instead of failing? The reason is that
> the current behavior prevents me from compiling a whole image without
> optimization.
>
> The reason I want -O0 in the first place is that while debugging an
> executable gdb told me that certain variables where optimized out.
glibc expects some optimizations like inlining for loader's early
startup code because it can not make function calls as the PLT has not
yet been relocated.
Thx
-Khem
>
> Regards
> Robert
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-07-10 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 13:58 prevent -O0 for glibc builds? Robert Schuster
2008-07-10 14:05 ` Phil Blundell
2008-07-10 15:21 ` Khem Raj [this message]
2008-07-11 0:22 ` bitbake man page typo Rich Pixley
2008-07-11 7:06 ` Khem Raj
2008-07-11 13:49 ` Compiling a custom kernel module Blaine Booher
2008-07-11 16:06 ` Cliff Brake
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=1215703284.32070.6.camel@isis \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.