prevent -O0 for glibc builds?

prevent -O0 for glibc builds?

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

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.

Regards
Robert




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

Re: prevent -O0 for glibc builds?

[Phil Blundell]

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.

I think you'd be better off just setting SELECTED_OPTIMIZATION_glibc =
"-O -g" or some such.

p.

Re: prevent -O0 for glibc builds?

[Khem Raj]

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

bitbake man page typo

[Rich Pixley]

Index: bitbake.1
===================================================================
--- bitbake.1    (revision 48512)
+++ bitbake.1    (working copy)
@@ -64,7 +64,7 @@
 Specify task to execute. Note that this only executes the specified 
task for
 the providee and the packages it depends on, i.e. 'compile' does not 
implicitly
 call stage for the dependencies (IOW: use only if you know what you are 
doing).
-Depending on the base.bbclass a listtaks tasks is defined and will show
+Depending on the base.bbclass a listtasks tasks is defined and will show
 available tasks.
 .TP
 .B \-rFILE, \-\-read=FILE

Re: bitbake man page typo

[Khem Raj]

On Thu, 2008-07-10 at 17:22 -0700, Rich Pixley wrote:
> Index: bitbake.1
> ===================================================================
> --- bitbake.1    (revision 48512)
> +++ bitbake.1    (working copy)
> @@ -64,7 +64,7 @@
>  Specify task to execute. Note that this only executes the specified 
> task for
>  the providee and the packages it depends on, i.e. 'compile' does not 
> implicitly
>  call stage for the dependencies (IOW: use only if you know what you are 
> doing).
> -Depending on the base.bbclass a listtaks tasks is defined and will show
> +Depending on the base.bbclass a listtasks tasks is defined and will show
>  available tasks.
>  .TP
>  .B \-rFILE, \-\-read=FILE
> 

Still there is one more left. It should be 'listtasks task'  I think.

Khem

Compiling a custom kernel module

[Blaine Booher]

Hey guys,
  I am very new to Open Embedded so please bare with me if I make it too 
obvious :).  We are using a gumstix embedded system with open embedded (and 
the angstrom release that gumstix provides).  We would like to use the kernel 
module cp2101 with a usb device.  The default cp2101 module won't work, since 
we have to edit the USB Device ID in the source code.  I'm having a hard time 
figuring out:
1.  How do I 'enable' the cp2101 module in the kernel?
2.  How do I rebuild the kernel, once the source code is edited?
3.  How to I ensure that the module is part of the final build, so that I can 
do a 'modprove cp2101' on the gumstix and have it load successfully?

I have found a few references, including emails on this email list, but 
nothing that explains it in a clear and concise manner (yet, at least).

Thank you in advance,
Blaine

Re: Compiling a custom kernel module

[Cliff Brake]

On Fri, Jul 11, 2008 at 9:49 AM, Blaine Booher <blaine@cliftonlabs.com> wrote:
> Hey guys,
>  I am very new to Open Embedded so please bare with me if I make it too
> obvious :).

Welcome :-)

> We are using a gumstix embedded system with open embedded (and
> the angstrom release that gumstix provides).  We would like to use the kernel
> module cp2101 with a usb device.  The default cp2101 module won't work, since
> we have to edit the USB Device ID in the source code.  I'm having a hard time
> figuring out:
> 1.  How do I 'enable' the cp2101 module in the kernel?

Copy an updated defconfig to:
packages/linux/gumstix-kernel-2.6.21/gumstix-connex/defconfig

Note, figure out what kernel you are building first, the above is just a guess.

> 2.  How do I rebuild the kernel, once the source code is edited?

bitbake -c rebuild virtual/kernel (rebuilds the kernel)

For development, I usually keep a kernel tree separate from the OE
kernel, and then just copy the defconfig and patches to the OE build
when I get everything correct.

Alternatively, you can:

bitbake -c devshell virtual/kernel

and do your development there in a development shell.  Once you get
everything finished, create patch files/defconfig and copy to the OE
recipe.

> 3.  How to I ensure that the module is part of the final build, so that I can
> do a 'modprove cp2101' on the gumstix and have it load successfully?

look at the name of the *.ipk file generated by OE build system.  Then
create a custom image file and add the ipk file name to the
IMAGE_INSTALL variable.

The following article has some examples:

http://bec-systems.com/web/content/view/79/9/

Cliff


-- 
=======================
Cliff Brake
http://bec-systems.com