What I found looks to be a difference between libc6-dev packages on the lucid version of ubunutu and libc6-dev on the oneiric version of ubuntu. Is there specific c library I should be using for the host compile? Or should I go to an older version of gcc? It is 4.4 on lucid and 4.6 on oneiric.<div>
<br></div>
<div><br></div><div>Respectfully,</div><div>Paul<br><br><div class="gmail_quote">On Wed, Jun 6, 2012 at 11:23 AM, Paul Wilhelm <span dir="ltr">&lt;<a href="mailto:bearcat.pilot@gmail.com" target="_blank">bearcat.pilot@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On the machine that does compile, the following file is used:<div>/usr/include/bits/sigcontext.h</div><div>This file has a copyright of 2002 from FSF.</div>

<div>This file does not try to use __u32, etc, and does not include other files that do.</div>
<div><br></div><div>On the machine that fails to compile, the following file is used:</div><div>/usr/include/i386-linux-gnu/bits/sigcontext.h</div><div>This file has a copyright of 1998 from FSF. This includes asm/sigcontext.h which in turn includes linux/types.h before using __u32, etc. linux/types.h includes asm/types.h (which in other other circumstance would include other files that include the definition for __u32, etc.). With the asm/types.h in target/include, things get broken.</div>


<div><br></div><div>I did some googling to find out how the /usr/include/bits directory gets filled, what package might set that up, but, I did not find anything useful.</div><div><br></div><div>Any suggestions?</div><div>

<div><div><br></div></div></div></blockquote></div></div>