On Saturday 19 May 2007 08:44, Mike Frysinger wrote: > is that the only place that is causing warnings for your headers install ?
Yes. When using HOSTCC (which is wrong) the warnings (in fact they are cc1 errors) do no longer happen. > it'll be hard to make that step conditional (assuming we want to in the first Conditional on what? > place) ... we def dont want to go sending stderr to /dev/null as when there > is an error (like unable to locate asm/unistd.h), we want to see that ... Assuming this header is not needed, it shouldn't be generated during the headers step, but rather in the 'full' uClibc later on. In which case we _do_ want to see the error, you're right. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ | | --==< °_° >==-- °------------.-------: X AGAINST | /e\ There is no | | http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. | °------------------------------°-------°------------------°--------------------° _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
