On Saturday 02 June 2007 7:45 pm, Ken Moffat wrote: > On Sat, Jun 02, 2007 at 06:40:34PM -0400, Baho Utot wrote: > > I have the following error when building MesaLib-6.5 > > > > makedepend: warning: clientattrib.c (reading /usr/include/libio.h, line > > 53): cannot find include file "stdarg.h" > > not in ./stdarg.h > > not in ../../../include/stdarg.h > > not in ../../../include/GL/internal/stdarg.h > > not in ../../../src/mesa/main/stdarg.h > > not in ../../../src/mesa/glapi/stdarg.h > > not in ../../../src/mesa/drivers/dri/common/stdarg.h > > not in /usr/include/drm/stdarg.h > > not in /usr/include/stdarg.h > > not in /usr/include/stdarg.h > > > > It looks to me that it is missing an include > > -I/usr/include/linux > > as that is where those header files reside. > > > > Am I missing a path in gcc include path? > > If so how do I check it? > > The first time I tried to build modular X on an uncommon platform > (ppc64) it crapped out and at first I assumed the multitude of > messages like this showed something was wrong. In fact, _all_ of my > builds of Mesa produce these messages, so they don't indicate a > problem (although they might indicate that Mesa is royally screwed > up in what it is expecting to find ;-). > > But, these warnings don't halt the build. Did you get a later > error, or are you just worried after looking at your logs ? > > FWIW, On non-x86 I have to use one or a sed to stop it trying to > build for drivers that have no chance of being compiled.
It did build completly. I just saw the errors and did not know how it could build correctly with error like those. I am building on x86, AMD althon-xp. I wonder if I fix the include path so the error doesn't show up will it change anything in the resulting code? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
